[ http://jira.jboss.com/jira/browse/BPEL-86?page=all ]
Alejandro Guizar updated BPEL-86:
---------------------------------
Summary: Release jBPM BPEL 1.1 (was: Release jBPM BPEL 1.0)
Description: Renamed this version to BPEL 1.1 on Pierre's request.
> Release jBPM BPEL 1.1
> ---------------------
>
> Key: BPEL-86
> URL: http://jira.jboss.com/jira/browse/BPEL-86
> Project: JBoss jBPM BPEL
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Engine
> Reporter: Alejandro Guizar
> Assigned To: Alejandro Guizar
> Fix For: jBPM BPEL 1.1
>
>
> Renamed this version to BPEL 1.1 on Pierre's request.
--
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
[ http://jira.jboss.com/jira/browse/JBAS-3330?page=all ]
Anil Saldhana closed JBAS-3330.
-------------------------------
Resolution: Out of Date
Need to wait for JBossWEB with Apr integration
> Tomcat6 Integration Issues With HEAD
> ------------------------------------
>
> Key: JBAS-3330
> URL: http://jira.jboss.com/jira/browse/JBAS-3330
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-5.0.0.Beta
> Reporter: Anil Saldhana
> Assigned To: Anil Saldhana
> Fix For: JBossAS-5.0.0.Beta
>
>
> This is the container task for all the issues that relate to the Tomcat6 integration in HEAD.
> Individual JIRA issues can be linked to this issue for audit.
> Note to Bill:-
> This issue is assigned to you initially until you can get HEAD building clean with JDK4 and JDK5.
--
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 ehcache version to 1.2.2
--------------------------------
Key: JBPORTAL-967
URL: http://jira.jboss.com/jira/browse/JBPORTAL-967
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.2 Branch, 2.4 Final
Reporter: Julien Viet
Assigned To: Rali Genova
Fix For: 2.4 Final, 2.2.2 Final
--
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
[ http://jira.jboss.com/jira/browse/EJBTHREE-436?page=all ]
Brian Stansberry closed EJBTHREE-436.
-------------------------------------
Resolution: Rejected
See http://jira.jboss.com/jira/browse/EJBTHREE-424 which will give you the same control over the partition name that you get with EJB 2.0.
> partition name should not be part of the @clustered annotation
> --------------------------------------------------------------
>
> Key: EJBTHREE-436
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-436
> Project: EJB 3.0
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: EJB 3.0 RC4 - PFD
> Reporter: Martin Welss
> Assigned To: Bill Burke
> Priority: Critical
> Fix For: EJB 3.0 RC9 - FD
>
>
> Why is the partition name part of the ejb-clustering annotation?
> Suppose there are three clusters: one for integration, one for test, one for production and each has a distinct partition name. It would not be possible to 'move' an application from integration to test without changing the code!
> And because of the attributes default value, there is no way to say to the bean 'never mind the partition name, just run everywhere'
--
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
[ http://jira.jboss.com/jira/browse/EJBTHREE-424?page=all ]
Brian Stansberry reassigned EJBTHREE-424:
-----------------------------------------
Assignee: Brian Stansberry
> Add check of the jboss.partition.name to the @Clustered annotation
> ------------------------------------------------------------------
>
> Key: EJBTHREE-424
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-424
> Project: EJB 3.0
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
>
> The @Clustered annotation defaults to "DefaultPartition" rather than the value of system property jboss.partition.name.
--
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
[ http://jira.jboss.com/jira/browse/JBXB-68?page=all ]
Heiko Braun closed JBXB-68.
---------------------------
> Release jbossxb-1.0.0.CR6 binary
> --------------------------------
>
> Key: JBXB-68
> URL: http://jira.jboss.com/jira/browse/JBXB-68
> Project: JBoss XML Binding (JBossXB)
> Issue Type: Task
> Reporter: Thomas Diesler
> Assigned To: Heiko Braun
> Fix For: JBossXB-1.0.0.CR6
>
>
> This release is a dependency off jbossws-1.0.2. It should work as a binary drop-in replacement in jboss-4.0.4.GA
--
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
[ http://jira.jboss.com/jira/browse/JBXB-68?page=all ]
Heiko Braun reassigned JBXB-68:
-------------------------------
Assignee: Heiko Braun (was: Alexey Loubyansky)
> Release jbossxb-1.0.0.CR6 binary
> --------------------------------
>
> Key: JBXB-68
> URL: http://jira.jboss.com/jira/browse/JBXB-68
> Project: JBoss XML Binding (JBossXB)
> Issue Type: Task
> Reporter: Thomas Diesler
> Assigned To: Heiko Braun
> Fix For: JBossXB-1.0.0.CR6
>
>
> This release is a dependency off jbossws-1.0.2. It should work as a binary drop-in replacement in jboss-4.0.4.GA
--
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
[ http://jira.jboss.com/jira/browse/JBXB-68?page=all ]
Heiko Braun updated JBXB-68:
----------------------------
Comment: was deleted
> Release jbossxb-1.0.0.CR6 binary
> --------------------------------
>
> Key: JBXB-68
> URL: http://jira.jboss.com/jira/browse/JBXB-68
> Project: JBoss XML Binding (JBossXB)
> Issue Type: Task
> Reporter: Thomas Diesler
> Assigned To: Heiko Braun
> Fix For: JBossXB-1.0.0.CR6
>
>
> This release is a dependency off jbossws-1.0.2. It should work as a binary drop-in replacement in jboss-4.0.4.GA
--
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
[ http://jira.jboss.com/jira/browse/JBXB-68?page=all ]
Heiko Braun resolved JBXB-68.
-----------------------------
Fix Version/s: JBossXB-1.0.0.CR6
Resolution: Done
> Release jbossxb-1.0.0.CR6 binary
> --------------------------------
>
> Key: JBXB-68
> URL: http://jira.jboss.com/jira/browse/JBXB-68
> Project: JBoss XML Binding (JBossXB)
> Issue Type: Task
> Reporter: Thomas Diesler
> Assigned To: Heiko Braun
> Fix For: JBossXB-1.0.0.CR6
>
>
> This release is a dependency off jbossws-1.0.2. It should work as a binary drop-in replacement in jboss-4.0.4.GA
--
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