4:51 a.m.
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.5
--
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
5:57 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints
[
https://jira.jboss.org/jira/browse/JBWS-2368?page=com.atlassian.jira.plug...
]
Darran Lofthouse updated JBWS-2368:
-----------------------------------
Description:
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.5
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
--
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
5:57 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints
[
https://jira.jboss.org/jira/browse/JBWS-2368?page=com.atlassian.jira.plug...
]
Darran Lofthouse updated JBWS-2368:
-----------------------------------
Workaround Description: Annotate all web methods with @WebMethod, this stops JBossWS
from processing all of the methods on the class.
Workaround: [Workaround Exists]
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.5
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
--
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
10 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints
[
https://jira.jboss.org/jira/browse/JBWS-2368?page=com.atlassian.jira.plug...
]
Darran Lofthouse updated JBWS-2368:
-----------------------------------
Fix Version/s: jbossws-native-3.0.6
(was: jbossws-native-3.0.5)
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.6
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
--
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
10 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints
[
https://jira.jboss.org/jira/browse/JBWS-2368?page=com.atlassian.jira.plug...
]
Darran Lofthouse commented on JBWS-2368:
----------------------------------------
There is still one method not being marked as synthetic, I have raised JBAOP-680 for this
to be investigated. Due to the dependency I am going to defer the commit to JBossWS
Native 3.0.6.GA.
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.6
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
--
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
10:24 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints
[
https://jira.jboss.org/jira/browse/JBWS-2368?page=com.atlassian.jira.plug...
]
Darran Lofthouse updated JBWS-2368:
-----------------------------------
Attachment: JAXWSAop.aop
JAXWSAop.jar
Uploading two deployments to test this with JBoss 5.
JAX-WS Deployments Fail For AOP Instrumented Endpoints
------------------------------------------------------
Key: JBWS-2368
URL: https://jira.jboss.org/jira/browse/JBWS-2368
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.6
Attachments: JAXWSAop.aop, JAXWSAop.jar
A message similar to the following is logged as JBossWS attempts to process the methods
added by JBoss AOP: -
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of
IllegalAnnotationExceptions
org.jboss.aop.InstanceAdvisor is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.InstanceAdvisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.InstanceAdvisor
at private org.jboss.aop.InstanceAdvisor
org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getInstanceAdvisorResponse
org.jboss.aop.Advisor does not have a no-arg default constructor.
this problem is related to the following location:
at org.jboss.aop.Advisor
at private org.jboss.aop.Advisor
org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse._return
at org.jboss.test.support.ws.phonebook.jaxws._getAdvisorResponse
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 82 more
--
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
5656
days inactive
5691
days old
jbossws-issues@lists.jboss.org
5 comments
1 participants
participants (1)
-
Darran Lofthouse (JIRA)