[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
[JBoss JIRA] Updated: (JBWS-1577) javax.jws.WebService in jbossws14-client.jar breaks Class#isAnnotationPresent()
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1577?page=all ]
Thomas Diesler updated JBWS-1577:
---------------------------------
Assignee: Thomas Diesler
> javax.jws.WebService in jbossws14-client.jar breaks Class#isAnnotationPresent()
> -------------------------------------------------------------------------------
>
> Key: JBWS-1577
> URL: http://jira.jboss.com/jira/browse/JBWS-1577
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws
> Environment: n/a
> Reporter: Brice Ruth
> Assigned To: Thomas Diesler
>
> The javax.jws.WebService in jbossws14-client.jar breaks Class#isAnnotationPresent().
> Because the javax.jws.WebService annotation is defined to extend org.jboss.lang.Annotation, instead of java.lang.annotation.Annotation, the Java language method Class#isAnnotationPresent() throws a ClassCastException when it tries to cast JBoss' javax.jws.WebService to a java.lang.annotation.Annotation in sun.reflect.annotation.AnnotationParser#annotationForMap().
> To replicate:
> Create a class, MyService:
> package test;
> import javax.jws.WebService;
> @WebService
> public class MyService {
> public void execute() {
>
> }
> }
> Create a class, TestAnnotation:
> package test;
> import javax.jws.WebService;
> public class TestAnnotation {
> public static void main(String[] args) {
> Class clazz = MyService.class;
> boolean hasAnnotation = clazz.isAnnotationPresent(WebService.class);
> System.out.print("Has annotation? " + hasAnnotation);
> }
> }
> Run TestAnnotation against the jbossws14-client.jar (and its dependencies). The following exception will be thrown:
> Exception in thread "main" java.lang.ClassCastException: $Proxy0
> at sun.reflect.annotation.AnnotationParser.annotationForMap(Unknown Source)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation(Unknown Source)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(Unknown Source)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(Unknown Source)
> at java.lang.Class.initAnnotationsIfNecessary(Unknown Source)
> at java.lang.Class.getAnnotation(Unknown Source)
> at java.lang.Class.isAnnotationPresent(Unknown Source)
> at test.TestAnnotation.main(TestAnnotation.java:8)
> The JSR-181 APIs provided by jbossws14-client.jar should not extend JBoss custom classes, I don't think. Especially not something as fundamental as Annotation.
> Respectfully,
> Brice Ruth
--
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
[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
[JBoss JIRA] Updated: (JBWS-1520) No server response on invalid soap request
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1520?page=all ]
Thomas Diesler updated JBWS-1520:
---------------------------------
Assignee: Thomas Diesler
> No server response on invalid soap request
> ------------------------------------------
>
> Key: JBWS-1520
> URL: http://jira.jboss.com/jira/browse/JBWS-1520
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-2.0.0
>
>
> My service replies correctly when the correct input is given, but when a bad SOAP message is sent, such as a typo in an opening tag but not a closing, the client gets no reply and the server logs an exception a la:
> 15:21:29,103 ERROR [STDERR] [Fatal Error] :4:60: The end-tag for element type "CustomerID" must end with a '>' delimiter.
> 15:21:29,104 ERROR [SOAPFaultExceptionHelper] SOAP request exception
> java.io.IOException: org.xml.sax.SAXParseException: The end-tag for element type "CustomerID" must end with a '>' delimiter.
> at org.jboss.util.xml.DOMUtils.parse(DOMUtils.java:110)
> at org.jboss.ws.soap.MessageFactoryImpl.createSOAPEnvelope(MessageFactoryImpl.java:238)
--
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