December 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1395) Add a Standard All Client Configuration to standard-jbossws-client-config.xml

by John Gilbert (JIRA)

Add a Standard All Client Configuration to standard-jbossws-client-config.xml ----------------------------------------------------------------------------- Key: JBWS-1395 URL: http://jira.jboss.com/jira/browse/JBWS-1395 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: John Gilbert Priority: Trivial It would be nice to have this in addition to Standard Client, Standard Secure Client, and Standard Addressing Client, so that all clients don't have to create their config file. <client-config> <config-name>Standard All Client</config-name> <post-handler-chain> <handler-chain-name>PostHandlerChain</handler-chain-name> <handler> <j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.wsse.WSSecurityHandlerOutbound</j2ee:handler-class> </handler> <handler> <j2ee:handler-name>SOAPClientHandler</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.addressing.soap.SOAPClientHandler</j2ee:handler-class> </handler> </post-handler-chain> </client-config> -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1412) WS-Eventing clustering capabilities

by Heiko Braun (JIRA)

WS-Eventing clustering capabilities ----------------------------------- Key: JBWS-1412 URL: http://jira.jboss.com/jira/browse/JBWS-1412 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-eventing Reporter: Heiko Braun -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1314) Precursor to streaming optimizations, elimination of xmlFragment

by Thomas Diesler (JIRA)

Precursor to streaming optimizations, elimination of xmlFragment ---------------------------------------------------------------- Key: JBWS-1314 URL: http://jira.jboss.com/jira/browse/JBWS-1314 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Thomas Diesler Fix For: jbossws-2.0.1 At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design. Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using javax.xml.transform.Source, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see [JBWS-1240] for an example). -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1324) JMS Endpoint - Message delivery starts before endpoint is ready.

by Darran Lofthouse (JIRA)

JMS Endpoint - Message delivery starts before endpoint is ready. ---------------------------------------------------------------- Key: JBWS-1324 URL: http://jira.jboss.com/jira/browse/JBWS-1324 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Fix For: jbossws-1.0.6 For most endpoints we need the EJB to be initialised before we initialise the web service, this way we know the session bean will be ready to process requests before the first request from a client is received. For message driven beans we need the web service to be initialised before the first message is processed by the MDB, however the same logic is used as is used for session beans so it is possible that the first message will be received while the web service is still being initialised. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-1330) Fix jaxrpc wsse tests for jbossws-5.0

by Thomas Diesler (JIRA)

Fix jaxrpc wsse tests for jbossws-5.0 ------------------------------------- Key: JBWS-1330 URL: http://jira.jboss.com/jira/browse/JBWS-1330 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0.CR2 [tdiesler@tdvaio test]$ ant -Dtest=jaxrpc/wsse test tests-main: [junit] Running org.jboss.test.ws.jaxrpc.wsse.MicrosoftInteropTestCase [junit] FIXME: [JBWS-1130] Consolidate namespace declarations [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.863 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.536 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.RoundTripTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.289 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.RpcTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.722 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.RpcTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 7.19 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 5.947 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 6.581 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.452 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SunInteropTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.382 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 0.431 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.WebClientTestCase [junit] [JBAS-3824] Fix ENC for EJB2.1 and Servlets [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.524 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 4.64 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase FAILED -- 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, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1307) JAXWS user guide and sampes

by Thomas Diesler (JIRA)

JAXWS user guide and sampes --------------------------- Key: JBWS-1307 URL: http://jira.jboss.com/jira/browse/JBWS-1307 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Fix For: jbossws-2.0.0 The user guide should cover all aspects of the JAXWS specification. Every chapter should be associated with code samples. It should be possible to take the userguide + samples and have instant working code as a easy entry point to JAXWS -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1335) Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA

by Igor Stuyver (JIRA)

Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA ------------------------------------------------------ Key: JBWS-1335 URL: http://jira.jboss.com/jira/browse/JBWS-1335 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxb Affects Versions: jbossws-1.0.0 Environment: JBoss 4.0.4.GA/jbossws-1.0.0.GA/wscompile Reporter: Igor Stuyver This bug report is a follow up for http://jira.jboss.com/jira/browse/JBWS-761 We are experiencing simular problems but on JBoss 4.0.4.GA. The only difference is that we have an interface (created by XmlBeans) with the same package/classname JBossWS is looking for for mapping its simpleType. We have following simple type declared: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" targetNamespace="http://my.project/schema/common" elementFormDefault="qualified"> <xs:simpleType name="LanguageCode"> <xs:restriction base="xs:string"> <xs:minLength value="2"/> <xs:maxLength value="2"/> </xs:restriction> </xs:simpleType> </xs:schema> This simple type is used in the WSDL file and in a seperate XSD file. Of this seperate XSD file, XMLBeans (http://xmlbeans.apache.org/) are created for easy use of XML in our application. We use an ejb-service-ref to call the webservice from an enterprise bean. In the response an element of type LanguageCode is present, in the generated POJO's (sun's wscompile) the element is declared as a String. During unmarshalling of the xml, following error occurs: Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Neither fromValue(java.lang.String p) nor fromValue(java.lang.String p1, javax.xml.namespace.NamespaceContext p2) were found in interface project.my.schema.common.LanguageCode at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtUtil.invokeUnmarshalMethod(RtUtil.java:522) at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:104) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:592) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:130) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:271) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:137) For me it seems that during unmarchalling, a class is searched to map the SimpleType to. Not a class but an interface is found and used from the created XMLBeans. The above exceptions is the result. Following the SUN forum (http://forum.java.sun.com/thread.jspa?threadID=716435) the simple type should be mapped to the Java type the base type of the SimpleType is mapped to, String is this example. During unmarshalling JBossWS is still looking for a class to map the SimpleType to instead of mapping it to String directly. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-1403) NumberFormatException When Using StubExt.PROPERTY_CLIENT_TIMEOUT

by Kevin Urciolo (JIRA)

NumberFormatException When Using StubExt.PROPERTY_CLIENT_TIMEOUT ---------------------------------------------------------------- Key: JBWS-1403 URL: http://jira.jboss.com/jira/browse/JBWS-1403 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Kevin Urciolo Priority: Minor If you attempt to to do this: stub._setProperty(StubExt.PROPERTY_CLIENT_TIMEOUT,timeout); You get the exception below. I believe the InvokerLocator JBoss code parses out the port by taking the string from a certain point to the end of the string. It appears the client timeout property is added to the string after after the port. So the timout gets picked up and causes the exception. 20:51:37,052 ERROR [STDERR] Caused by: java.lang.NumberFormatException: For input string: "8999?timeout=999999999" 20:51:37,053 ERROR [STDERR] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) 20:51:37,053 ERROR [STDERR] at java.lang.Integer.parseInt(Integer.java:456) 20:51:37,053 ERROR [STDERR] at java.lang.Integer.parseInt(Integer.java:497) 20:51:37,053 ERROR [STDERR] at org.jboss.remoting.InvokerLocator.(InvokerLocator.java:159) 20:51:37,054 ERROR [STDERR] at org.jboss.ws.soap.SOAPConnectionImpl.createRemotingClient(SOAPConnectionImpl.java:203) -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-1422) NPE if more than one upper-case character in @WebParam.name

by Ortwin Glück (JIRA)

NPE if more than one upper-case character in @WebParam.name ----------------------------------------------------------- Key: JBWS-1422 URL: http://jira.jboss.com/jira/browse/JBWS-1422 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.3.SP1 Reporter: Ortwin Glück If @WebParam.name is a string with more than one upper-case character a NPE is thrown on deployment. @WebService( name="test", serviceName="Websvc" ) @SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED) @Remote public interface IWebsvc { Response cancel( @WebParam(name="myFooBar") String myfoobar); } java.lang.NullPointerException [exec] at java.lang.Class.searchFields(Class.java:2571) [exec] at java.lang.Class.getField0(Class.java:2590) [exec] at java.lang.Class.getField(Class.java:1505) [exec] at org.jboss.ws.metadata.wsdl.WSDLUtils.doesPublicFieldExist(WSDLUtils.java:428) [exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.addVariableMappings(SchemaTypeCreator.java:493) [exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.registerJavaTypeMapping(SchemaTypeCreator.java:463) [exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:344) [exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:273) [exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132) [exec] at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD.java:109) [exec] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:556) [exec] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:141) [exec] at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:235) [exec] at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:168) [exec] at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318) [exec] at org.jboss.ws.deployment.JSR181MetaDataBuilder.processOrGenerateWSDL(JSR181MetaDataBuilder.java:289) [exec] at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:231) [exec] at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75) [exec] at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106) -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1308) JAXWS training material and labs

by Thomas Diesler (JIRA)

JAXWS training material and labs -------------------------------- Key: JBWS-1308 URL: http://jira.jboss.com/jira/browse/JBWS-1308 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Fix For: jbossws-2.0.0 The user guide should cover all aspects of the JAXWS specification. Every chapter should be associated with code samples. It should be possible to take the userguide + samples and have instant working code as a easy entry point to JAXWS -- 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, 10 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2006