6:59 p.m.
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ppc
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:16 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=93151 (was:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=93151&am...)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ppc
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
7:16 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: EJB 3.0 RC10 - FD
Priority: Critical (was: Major)
Missing functionality.
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ppc
Priority: Critical
Fix For: EJB 3.0 RC10 - FD
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
9:52 p.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf reassigned EJBTHREE-757:
--------------------------------------
Assignee: Carlo de Wolf
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: EJB 3.0 RC10 - FD
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:07 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: AS 4.2.0 CR2
(was: AS 4.2.0 CR1)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.0 CR2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:27 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=comments#action_12354692 ]
Carlo de Wolf commented on EJBTHREE-757:
----------------------------------------
AS 4.2 now says: "IllegalStateException: No message context found"
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.0 CR2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:27 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Affects Version/s: AS 4.2.0 CR1
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.0 CR2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:27 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Environment: Unit test: jaxws
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.0 CR2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
10:01 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: AS 4.2.0 GA
(was: AS 4.2.0 CR2)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.0 GA
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
6:52 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: Branch_4_2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
9:49 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.1)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: Branch_4_2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
4:58 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=comments#action_12380355 ]
Thomas Diesler commented on EJBTHREE-757:
-----------------------------------------
AFAIK
EJB3 only supports JAX-WS
EJB21 only supports JAX-RPC
IMHO it is illegal for an EJB3 endpoint to obtain a JAX-RPC MessageContext via the
SessionContext.
The way to obtain a JAX-WS MessageContext is via injection.
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: Branch_4_2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
5:10 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: AS 4.2.2.GA
(was: Branch_4_2)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.2.GA
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
5:30 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf resolved EJBTHREE-757.
------------------------------------
Resolution: Rejected
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.2.GA
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
6:20 p.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf reopened EJBTHREE-757:
------------------------------------
Cheered too soon.
EJB 3 3.5.2 defines the use of JAX-RPC clients.
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: AS 4.2.2.GA
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
5:24 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.2.GA)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: Branch_4_2
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
11:06 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext Not Implemented
[ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]
Carlo de Wolf updated EJBTHREE-757:
-----------------------------------
Fix Version/s: (was: Branch_4_2)
Assignee: (was: Carlo de Wolf)
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Priority: Critical
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
3:19 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-757) getMessageContext Not Implemented
[
https://jira.jboss.org/jira/browse/EJBTHREE-757?page=com.atlassian.jira.p...
]
Carlo de Wolf resolved EJBTHREE-757.
------------------------------------
Resolution: Out of Date
See JBWS-1443 for details
getMessageContext Not Implemented
---------------------------------
Key: EJBTHREE-757
URL: https://jira.jboss.org/jira/browse/EJBTHREE-757
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
Environment: Unit test: jaxws
Reporter: ppc
Priority: Critical
jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the
SessionContext he method getMessageContext is called.
Form this version with the new JbossWS stack as far i know i not anymore possible to
retreive a SOAP attachement .
With the old ws4ee was possible calling the
org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now
all the axis stuff has been removed :(
--
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
5482
days inactive
6406
days old
17 comments
4 participants
participants (4)
-
Carlo de Wolf (JIRA) -
Carlo de Wolf (JIRA) -
ppc (JIRA)
-
Thomas Diesler (JIRA)