November 2006 - jbossws-issues - Jboss List Archives

[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

17 years

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, 3 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, 5 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-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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1304) Automatically detect Connector ports when deployed to Tomcat

by Darran Lofthouse (JIRA)

Automatically detect Connector ports when deployed to Tomcat ------------------------------------------------------------ Key: JBWS-1304 URL: http://jira.jboss.com/jira/browse/JBWS-1304 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Environment: Tomcat Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.0.5 Automatically detect Connector ports when deployed to Tomcat. JBWS-1115 adds functionality to automatically detect the connector ports when deploying to JBoss, the same should be implemented when deploying to Tomcat. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1339) @Security domain vs. <security-domain>

by Thomas Diesler (JIRA)

@Security domain vs. <security-domain> -------------------------------------- Key: JBWS-1339 URL: http://jira.jboss.com/jira/browse/JBWS-1339 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-1.0.5 I have a test where my ejb3 SLSB, jsr181 endpoint works only if I use the @SecurityDomain annotation. If I try to define the security-domain in the deployment descriptor I get a 401 http response code. -- 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, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-1384) Cannot obtain java/xml type mapping for attachmet part

by Thomas Diesler (JIRA)

Cannot obtain java/xml type mapping for attachmet part ------------------------------------------------------- Key: JBWS-1384 URL: http://jira.jboss.com/jira/browse/JBWS-1384 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 22:11:09,354 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string 22:11:09,354 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.4.GA/server/defaul t/deploy/alhamd.war org.jboss.ws.WSException: Cannot obtain java/xml type mapping for: {http://www.w3.org/2001/XMLSchema }string at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBui lder.java:513) at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuild er.java:200) at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBui lder.java:223) at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:78) at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80) at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java: -- 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1328) Client security configuration not loaded when client deployed with issolated classloader.

by Thomas Diesler (JIRA)

Client security configuration not loaded when client deployed with issolated classloader. ----------------------------------------------------------------------------------------- Key: JBWS-1328 URL: http://jira.jboss.com/jira/browse/JBWS-1328 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-1.0.2 Reporter: Thomas Diesler Assigned To: Darran Lofthouse Fix For: jbossws-1.0.3 When a client is deployed using an issolated classloader the security configuration of the client is not loaded as the wrong classloader is used to load the resource. This results in a warning being logged and the client sending messages that are not signed / encrypted. -- 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, 11 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2006