June 2007 - jbossws-issues - Jboss List Archives

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1622?page=all ] Thomas Diesler updated JBWS-1622: --------------------------------- Component/s: jbossws-jaxws > 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) > Components: jbossws-jaxws > 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1628) Resurect Eventing tests for new deployer architecture

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1628?page=all ] Thomas Diesler updated JBWS-1628: --------------------------------- Component/s: jbossws-jaxws Fix Version/s: jbossws-2.0.0 (was: jbossws-2.1.0) > Resurect Eventing tests for new deployer architecture > ----------------------------------------------------- > > Key: JBWS-1628 > URL: http://jira.jboss.com/jira/browse/JBWS-1628 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1626) Resurect dynamic server handlers

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1626?page=all ] Thomas Diesler updated JBWS-1626: --------------------------------- Component/s: jbossws-jaxws Fix Version/s: jbossws-2.0.0 (was: jbossws-2.x) > Resurect dynamic server handlers > -------------------------------- > > Key: JBWS-1626 > URL: http://jira.jboss.com/jira/browse/JBWS-1626 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1281) Marshalling exception with xsi:nil='1' but without xsi:type

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1281?page=all ] Thomas Diesler updated JBWS-1281: --------------------------------- Summary: Marshalling exception with xsi:nil='1' but without xsi:type (was: When an element is nil, weblogic (8.1 sp3) sends an element with xsi:nil='1', however, it does not send type information with xsi:type=xxxx. It causes exception in org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.java.) > Marshalling exception with xsi:nil='1' but without xsi:type > ----------------------------------------------------------- > > Key: JBWS-1281 > URL: http://jira.jboss.com/jira/browse/JBWS-1281 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Affects Versions: jbossws-1.0.2 > Environment: windows xp, linux, jdk1.5 > Reporter: George Gan > Fix For: jbossws-2.0.0 > > Attachments: SundayContentHandler.java > > > When an element is nil, weblogic (8.1 sp3) sends an element with xsi:nil='1', however, it does not send type information with xsi:type=xxxx. It causes exception in org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.java. I hacked to code to only compare the localpart: > public void endElement(String namespaceURI, String localName, String qName) > { > ElementBinding elementBinding = null; > QName endName = localName.length() == 0 ? new QName(qName) : new QName(namespaceURI, localName); > StackItem item; > while(true) > { > item = stack.peek(); > if(item.cursor == null) > { > if(item.ended) > { > pop(); > if(item.particle.isRepeatable()) > { > endRepeatableParticle(item.particle); > } > } > else > { > elementBinding = (ElementBinding)item.particle.getTerm(); > item.ended = true; > break; > } > } > else > { > if(!item.ended) // could be ended if it's a choice > { > endParticle(item, endName, 1); > } > ParticleBinding currentParticle = item.cursor.getCurrentParticle(); > TermBinding term = currentParticle.getTerm(); > if(term.isWildcard() && currentParticle.isRepeatable()) > { > endRepeatableParticle(currentParticle); > } > pop(); > if(item.particle.isRepeatable()) > { > endRepeatableParticle(item.particle); > } > } > } > if(elementBinding == null) > { > throw new JBossXBRuntimeException("Failed to endElement " + qName + ": binding not found"); > } > //if(!elementBinding.getQName().equals(endName)) <--------------------------------------- hack starts here > // GG hack only compare the local parts. In the case of the an element is nil, > // there is no type prefix > if(!endName.getLocalPart().equals( elementBinding.getQName().getLocalPart())) > { > throw new JBossXBRuntimeException("Failed to end element " + > new QName(namespaceURI, localName) + > ": element on the stack is " + elementBinding.getQName() > ); > } > endElement(); > } -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1242) ComplexDataTypesRpcList_Service - null array elements incorrectly created as empty elements

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1242?page=all ] Thomas Diesler updated JBWS-1242: --------------------------------- Fix Version/s: jbossws-interop-1.0 (was: jbossws-2.0.0) > ComplexDataTypesRpcList_Service - null array elements incorrectly created as empty elements > ------------------------------------------------------------------------------------------- > > Key: JBWS-1242 > URL: http://jira.jboss.com/jira/browse/JBWS-1242 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-interop-1.0 > > > For schema type: > <xs:complexType name="ArrayOfstring"> > <xs:sequence> > <xs:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="xs:string"/> > </xs:sequence> > </xs:complexType> > <xs:element name="ArrayOfstring" nillable="true" type="tns:ArrayOfstring"/> > The following request > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> </s:Header> <s:Body> <RetArrayString1D xmlns="http://tempuri.org/"> <inArrayString1D xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns=""> <d4p1:string i:nil="true" /> <d4p1:string>string Array Data 1</d4p1:string> <d4p1:string i:nil="true" /> <d4p1:string>string Array Data 3</d4p1:string> <d4p1:string i:nil="true" /> <d4p1:string>string Array Data 5</d4p1:string> <d4p1:string i:nil="true" /> <d4p1:string>string Array Data 7</d4p1:string> <d4p1:string i:nil="true" /> <d4p1:string>string Array Data 9</d4p1:string> </inArrayString1D> </RetArrayString1D> </s:Body> </s:Envelope> > incorrectly returns: > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <ns1:RetArrayString1DResponse xmlns:ns1="http://tempuri.org/"> <RetArrayString1DResult xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> </ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays">string Array Data 1</ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> </ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays">string Array Data 3</ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> </ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays">string Array Data 5</ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> </ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays">string Array Data 7</ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> </ns_string:string> <ns_string:string xmlns:ns_string="http://schemas.microsoft.com/2003/10/Serialization/Arrays">string Array Data 9</ns_string:string> </RetArrayString1DResult> </ns1:RetArrayString1DResponse> </env:Body> </env:Envelope -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1243) ComplexDataTypesRpcList_Service - null structures result in members with null values

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1243?page=all ] Thomas Diesler updated JBWS-1243: --------------------------------- Fix Version/s: jbossws-interop-1.0 (was: jbossws-2.0.0) > ComplexDataTypesRpcList_Service - null structures result in members with null values > ------------------------------------------------------------------------------------ > > Key: JBWS-1243 > URL: http://jira.jboss.com/jira/browse/JBWS-1243 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-interop-1.0 > > > A null structure, like the following:: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> </s:Header> <s:Body> <RetStructS1 xmlns="http://tempuri.org/"> <inStructS1 xmlns:d4p1="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="" /> </RetStructS1> </s:Body> </s:Envelope> > results in a member being set to null instead of the structure itself: > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <ns1:RetStructS1Response xmlns:ns1="http://tempuri.org/"> <RetStructS1Result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ns_name:name xmlns:ns_name="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." xsi:nil="1"> </ns_name:name> </RetStructS1Result> </ns1:RetStructS1Response> </env:Body> </env:Envelope> -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1241) BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1241?page=all ] Thomas Diesler updated JBWS-1241: --------------------------------- Fix Version/s: jbossws-interop-1.0 (was: jbossws-2.0.0) > BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling > --------------------------------------------------------------- > > Key: JBWS-1241 > URL: http://jira.jboss.com/jira/browse/JBWS-1241 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-interop-1.0 > > > CR Fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">HelloWorld</inString></RetString></s:Body></s:Envelope> > CRLF fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">Hello > World</inString></RetString></s:Body></s:Envelope> > The returned value for both is LF only, which is incorrect. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1240) BaseDataTypesRpcLit_Service - RetQName - QName escape character parsing issues

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1240?page=all ] Thomas Diesler updated JBWS-1240: --------------------------------- Fix Version/s: jbossws-interop-1.0 (was: jbossws-2.0.0) > BaseDataTypesRpcLit_Service - RetQName - QName escape character parsing issues > ------------------------------------------------------------------------------ > > Key: JBWS-1240 > URL: http://jira.jboss.com/jira/browse/JBWS-1240 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-interop-1.0 > > > A namespace with escape characters fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetQName xmlns="http://tempuri.org/"><inQName xmlns="" xmlns:a=">:Can We do it<:">a:localname</inQName></RetQName></s:Body></s:Envelope> > A value with escape characters fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetQName xmlns="http://tempuri.org/"><inQName xmlns="" xmlns:a="namespace">a:<::Yes We Can ::></inQName></RetQName></s:Body></s:Envelope> -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1263) Addressing does not disable the mustUnderstand attribute, which causes HandlerchainBaseImple.checkMustUnderstand to fail

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1263?page=comments#action_12365208 ] Heiko Braun commented on JBWS-1263: ----------------------------------- Per default it's sending of mustUnderstand is disabled > Addressing does not disable the mustUnderstand attribute, which causes HandlerchainBaseImple.checkMustUnderstand to fail > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-1263 > URL: http://jira.jboss.com/jira/browse/JBWS-1263 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-addressing > Reporter: Jason T. Greene > 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1692) SAAJ:importNode needs to work

by Anil Saldhana (JIRA)

SAAJ:importNode needs to work ----------------------------- Key: JBWS-1692 URL: http://jira.jboss.com/jira/browse/JBWS-1692 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws Reporter: Anil Saldhana If I have a SOAPMessage constructed using the MessageFactory interface, I should be able to import a node from a different document and append to the first child of soap body. This does not work correctly. I have tested this against the SAAJ RI and it works fine there. Here is sample code: MessageFactory factory = MessageFactory.newInstance(); File soapreqfile = new File("soap-request-template.xml"); SOAPMessage msg = factory.createMessage(null, new FileInputStream(soapreqfile)); //Get the node that needs to be imported Node someNode = getNode("import-node.xml"); //Import the node Node importedNode = msg.getSOAPPart().getOwnerDocument().importNode(someNode, true); //Append the node to the first child msg.getSOAPBody.getFirstChild().appendChild(importedNode); -- 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

17 years, 6 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007