[JBoss JIRA] (DROOLS-683) ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
by Abel Marrero Santos (JIRA)
Abel Marrero Santos created DROOLS-683:
------------------------------------------
Summary: ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
Key: DROOLS-683
URL: https://issues.jboss.org/browse/DROOLS-683
Project: Drools
Issue Type: Bug
Affects Versions: 6.2.0.CR4
Environment: Ubuntu Linux x64 & Tomcat 7
Reporter: Abel Marrero Santos
Assignee: Mark Proctor
An exception is raised when the REST method to create a new organizational unit is invoked.
To reproduce the issue you only have to POST to /rest/organizationalunits a JSON like:
{
"name":"testorg",
"description":"",
"owner":"test",
"repositories":[]
}
and then check the job result or check the server logs.
It works fine in version 6.2.0.CR3
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-3502) Handle session attribute serialization incompatiblities
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-3502?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-3502:
-------------------------------
Summary: Handle session attribute serialization incompatiblities (was: Create configurable strategy for dealing with serialization incompatiblities)
> Handle session attribute serialization incompatiblities
> -------------------------------------------------------
>
> Key: WFLY-3502
> URL: https://issues.jboss.org/browse/WFLY-3502
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> When a new release of a web application is deployed to an existing cluster, any changes to the object placed in the web session can cause serialization incompatibilities. To handle this cleanly, we typically recommend that users leverage isolated cluster and mod_cluster load balancing groups (or mod_jk domains) to transition users to the new version of an application.
> For simple applications, this might be overkill. It might be acceptable/preferable to create a new session in the event of a serialization incompatibility, rather than failing the request. We should allow developers to configure this behavior per-application.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Rafael Benevides commented on WFLY-4171:
----------------------------------------
Thanks for reporting it. I'll reopen DESIGN-659 for html5 QS
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFCORE-501) ServerGroupAddHandler should add a separate step to validate profile and socket-binding-group refs
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-501:
----------------------------------------
Summary: ServerGroupAddHandler should add a separate step to validate profile and socket-binding-group refs
Key: WFCORE-501
URL: https://issues.jboss.org/browse/WFCORE-501
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha15
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Validating references directly will imply specific ordering, in this case profile and socket-binding-group will have to be added before this handler executes. Postponing the validation to the next step will remove such a requirement.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months