Upgrade EJB3 to 1.1.4
---------------------
Key: JBAS-6775
URL: https://jira.jboss.org/jira/browse/JBAS-6775
Project: JBoss Application Server
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Reporter: Carlo de Wolf
Assignee: jaikiran pai
Fix For: JBossAS-6.0.0.Alpha1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Remove the old deployer api
---------------------------
Key: JBAS-6503
URL: https://jira.jboss.org/jira/browse/JBAS-6503
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Deployers
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBossAS-6.0.0.Alpha1
There's still a lot of legacy deployer code lying around in JBossAS.
This should be removed since it no longer works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JBoss Serailization 1.0.3 does not work. Make sure a new Serializtion jar gets sent out with this fix with remoting.
---------------------------------------------------------------------------------------------------------------------
Key: JBREM-998
URL: http://jira.jboss.com/jira/browse/JBREM-998
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: serialization
Affects Versions: 2.2.2.SP7
Reporter: Jay Howell
Priority: Critical
Jboss serialization is broken. We need to make sure that we fix http://jira.jboss.org/jira/browse/JBSER-108 and it gets out with future versions of remoting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Upgrade jboss-ejb3-api to a working version
-------------------------------------------
Key: JBMETA-227
URL: https://jira.jboss.org/jira/browse/JBMETA-227
Project: JBoss Metadata
Issue Type: Task
Security Level: Public (Everyone can see)
Components: EJB
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Currently on 3.1.0-SNAPSHOT, this artifact has disappeared from the snapshot repository. Use 3.1.0 for the time being.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Patch commons-logging so that Jasper doesn't use a deployment's logj4.jar when compiling a JSP in that deployment
-----------------------------------------------------------------------------------------------------------------
Key: JBAS-7120
URL: https://jira.jboss.org/jira/browse/JBAS-7120
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA
Reporter: Jimmy Wilson
Assignee: David Lloyd
If a deployment (e.g. a WAR) packages its own log4j.jar then Jasper will use that log4j.jar when compiling the deployment's JSPs. This can cause unexpected behavior. Jasper should use JBoss' log4j.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/JBRULES-95?page=com.atlassian.jira.plu... ]
Mark Proctor closed JBRULES-95.
-------------------------------
> scan ObjectTypeNodes for is assignable when adding new ObjectTypeNodes
> ----------------------------------------------------------------------
>
> Key: JBRULES-95
> URL: https://jira.jboss.org/jira/browse/JBRULES-95
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: drools-core (expert)
> Reporter: Mark Proctor
> Assignee: Edson Tirelli
> Fix For: 3.0-beta3
>
>
> when a new Rule is added that adds new ObjectTypeNodes we need to scan all other ObjectTypdeNodes to see if their contenst are "assignablefrom". This ensures that we propagate facts from List and ArrayList. One key part to this is to make sure we remove redundance, we don't want to propagate a fact twice because it matches both List and ArrayList.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support ShrinkWrap archives in the embedded configuration
---------------------------------------------------------
Key: JBJCA-229
URL: https://jira.jboss.org/jira/browse/JBJCA-229
Project: JBoss JCA
Issue Type: Task
Components: Embedded
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.0.Alpha7
The embedded configuration of container should allow deployment of ShrinkWrap archives.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira