May 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1657) Error resolving swaref schema

by Heiko Braun (JIRA)

Error resolving swaref schema ----------------------------- Key: JBWS-1657 URL: http://jira.jboss.com/jira/browse/JBWS-1657 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun 17:24:15,851 ERROR [JBossXSErrorHandler] JBossWS_swaref.samples.jaxws.ws.test.jboss.org_64364.xsd[domain:http://ww...: Error resolving component 'ns1:swaRef'. It was detected that 'ns1:swaRef' is in namespace 'http://ws-i.org/profiles/basic/1.1/xsd', but components from this namespace are not referenceable from schema document 'file:/home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/tmp/jbossws/JBossWS_swaref.samples.jaxws.ws.test.jboss.org_64364.xsd'. If this is the incorrect namespace, perhaps the prefix of 'ns1:swaRef' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/tmp/jbossws/JBossWS_swaref.samples.jaxws.ws.test.jboss.org_64364.xsd'. 17:24:16,308 INFO [TomcatDeployment] deploy, ctxPath=/DocLitEndpointImplService, vfsUrl= -- 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

16 years, 11 months

1
5
0 / 0

[JBoss JIRA] Commented: (JBWS-1283) Soap attachments were dropped on server responses. Attachment is added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message.

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1283?page=comments#action_12363058 ] Heiko Braun commented on JBWS-1283: ----------------------------------- George, i'll need a test case that reproduces the error in order to verify the patches. > Soap attachments were dropped on server responses. Attachment is added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-1283 > URL: http://jira.jboss.com/jira/browse/JBWS-1283 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.0.2 > Environment: windows, linux, jdk1.5 > Reporter: George Gan > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > Attachments: ServiceEndpointInvoker.java, ServiceEndpointInvokerEJB21.java > > > Soap attachments were dropped on server responses. Attachment can be added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message. > The problem was in the ServiceEndpointInvoker. It overwrote the SOAPMessage in the MessageContext. In this class, the method invokeServiceEndpoint was overwritten by ServiceEndpointInvokerEJB21, which invokes the EJB via the ServiceEndpointInterceptor. This ServiceEndpointInterceptor invokes the EJB and also the handlers; it creates the correct SOAPMessage and sets it in the ContextContext. Unfortunately, it was overwritten later by the ServiceEndpointInvoker. > Fixes are attached. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1460) @XmlMimeType on SEI parameter declarations

by Heiko Braun (JIRA)

@XmlMimeType on SEI parameter declarations ------------------------------------------ Key: JBWS-1460 URL: http://jira.jboss.com/jira/browse/JBWS-1460 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: binding Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.0 -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-1660) Resolve swaref schema through entity resolver

by Heiko Braun (JIRA)

Resolve swaref schema through entity resolver --------------------------------------------- Key: JBWS-1660 URL: http://jira.jboss.com/jira/browse/JBWS-1660 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.0 -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1564) Support swaRef with JAX-WS

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1564?page=comments#action_12362963 ] Heiko Braun commented on JBWS-1564: ----------------------------------- [hbraun@localhost jbossws-tests]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.swaref.SWARefTestCase one-test Buildfile: build.xml one-test: [junit] Running org.jboss.test.ws.jaxws.samples.swaref.SWARefTestCase [junit] FIXME [JBWS-1460]: @XmlMimeType and @XmlAttachmentRef on SEI parameter declarations [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.09 sec > Support swaRef with JAX-WS > --------------------------- > > Key: JBWS-1564 > URL: http://jira.jboss.com/jira/browse/JBWS-1564 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.2.0 > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > WS-I Attachment Profile 1.0 defines mechanism to reference MIME attachment parts using swaRef. In this mechanism the content of XML element of type wsi:swaRef is sent as MIME attachment and the element inside SOAP Body holds the reference to this attachment in the CID URI scheme as defined by RFC 2111. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1659) @XmlAttachmentRef ignored on method level

by Heiko Braun (JIRA)

@XmlAttachmentRef ignored on method level ----------------------------------------- Key: JBWS-1659 URL: http://jira.jboss.com/jira/browse/JBWS-1659 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.0 If you set the @XmlAttachmentRef on getter methods the AttachmentRef scanner fails to identify these properties -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1564) Support swaRef with JAX-WS

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1564?page=all ] Heiko Braun updated JBWS-1564: ------------------------------ Summary: Support swaRef with JAX-WS (was: Add support for swaRef) > Support swaRef with JAX-WS > --------------------------- > > Key: JBWS-1564 > URL: http://jira.jboss.com/jira/browse/JBWS-1564 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.2.0 > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > WS-I Attachment Profile 1.0 defines mechanism to reference MIME attachment parts using swaRef. In this mechanism the content of XML element of type wsi:swaRef is sent as MIME attachment and the element inside SOAP Body holds the reference to this attachment in the CID URI scheme as defined by RFC 2111. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1564) Support swaRef with JAX-WS

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1564?page=all ] Heiko Braun updated JBWS-1564: ------------------------------ Fix Version/s: jbossws-2.0.0 (was: jbossws-2.0.1) > Support swaRef with JAX-WS > --------------------------- > > Key: JBWS-1564 > URL: http://jira.jboss.com/jira/browse/JBWS-1564 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.2.0 > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > WS-I Attachment Profile 1.0 defines mechanism to reference MIME attachment parts using swaRef. In this mechanism the content of XML element of type wsi:swaRef is sent as MIME attachment and the element inside SOAP Body holds the reference to this attachment in the CID URI scheme as defined by RFC 2111. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1658) SwaRef fails with doclit/wrapped endpoints

by Heiko Braun (JIRA)

SwaRef fails with doclit/wrapped endpoints ------------------------------------------ Key: JBWS-1658 URL: http://jira.jboss.com/jira/browse/JBWS-1658 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.0 The ReflectiveAttachmentRefScanner doesnt correctly scan generated wrapper beans. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1622) Multiple context root not supported

by Rick Reumann (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1622?page=comments#action_12362893 ] Rick Reumann commented on JBWS-1622: ------------------------------------ Yes, Heiko's explanation was very good. And I was incorrect above in my statement concerning the user of @WebContext. Actually using the @WebContext annotation does work for me. (I apologize for stating that it didn't - not sure really what went originally wrong there.) I'd still consider this issue something that should be addressed though, since I don't believe you should 'have' to use @WebContext in order to get the desired behavior of multiple webservices deployed in an ear. > Multiple context root not supported > ----------------------------------- > > Key: JBWS-1622 > URL: http://jira.jboss.com/jira/browse/JBWS-1622 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-1.2.1 > Environment: JBoss 4.0.5 + EJB3 + JBossWS 1.2.1.GA > Reporter: Stephan Heffner > Assigned To: Darran Lofthouse > > Switching JBossWS from 1.2.0.SP1 to 1.2.1.GA I got this error message starting my EAR based application including four Services: > 09:36:13,998 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: joe.ear/joe.jar > 09:36:14,001 ERROR [MainDeployer] Could not create deployment: file:/home/heffner/Java/jboss-4.0.5.GA/server/default/deploy/joe.ear/joe.jar/ > org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: Multiple context root not supported) > at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83) > at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) > at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy29.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy8.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) > at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:417) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy5.deploy(Unknown Source) > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) > at org.jboss.Main.boot(Main.java:200) > at org.jboss.Main$1.run(Main.java:490) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.ws.WSException: Multiple context root not supported > at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.createJBossWebAppDescriptor(ServiceEndpointGeneratorEJB.java:258) > at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.generatWebDeployment(ServiceEndpointGeneratorEJB.java:71) > at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB3.generateWebDeployment(DeployerInterceptorEJB3.java:127) > at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:49) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) > ... 75 more > Switching back to 1.2.0.SP1 works. > I'm using onyl Annotations to configure the provided services. Example of one test service: > @Local > @WebService > public interface DatabaseService > { > @WebMethod > public String dbmsAlert(@WebParam(name = "alert") String alert, @WebParam(name = "message") String message); > } > @Stateless > @WebService(endpointInterface = "de.spiegel.joe.service.DatabaseService") > public class DatabaseServiceImpl implements DatabaseService > { > private static final Logger log = Logger.getLogger(DatabaseServiceImpl.class); > @PersistenceContext > EntityManager entityManager; > > public String dbmsAlert(String alert, String message) > { > log.debug("Received alert '"+alert+"' with message '"+message+"'."); > return "OK"; > } > } > What can I do to solve this issue? -- 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2007