[JBoss JIRA] Created: (JBWS-1393) Problem interpreting messages with attachment when confronted with no <start> header
by Romeu Figueira (JIRA)
Problem interpreting messages with attachment when confronted with no <start> header
------------------------------------------------------------------------------------
Key: JBWS-1393
URL: http://jira.jboss.com/jira/browse/JBWS-1393
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: JBoss AS 4.0.5, JBossWS 1.0.4, JDK 1.5.0.8, Windows XP SP2 and HP-UX
Reporter: Romeu Figueira
The current JBoss WS stack fails to properly interpret the MIME boundary when a message is put through without a <start> part in the MIME Headers. It skips the rootpart and gives an error of "multipart/related type specified a root type other than the one that was found." when finding the attachment part.
Using TCPMon confirms that a correct message was put out.
A fix is available in the forum thread.
--
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
19 years
[JBoss JIRA] Created: (JBWS-1410) NumberFormatException From StubExt.PROPERTY_CLIENT_TIMEOUT
by Thomas Diesler (JIRA)
NumberFormatException From StubExt.PROPERTY_CLIENT_TIMEOUT
----------------------------------------------------------
Key: JBWS-1410
URL: http://jira.jboss.com/jira/browse/JBWS-1410
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-1.2.0
I am trying to set the client timeout for a jbossws. I get the exception show below. The number before the '?' is the port I set. How do I fix this?
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
19 years
[JBoss JIRA] Updated: (JBWS-723) Protect access to wsdl
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-723?page=all ]
Thomas Diesler updated JBWS-723:
--------------------------------
Fix Version/s: (was: jbossws-1.0.5)
> Protect access to wsdl
> ----------------------
>
> Key: JBWS-723
> URL: http://jira.jboss.com/jira/browse/JBWS-723
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jaxrpc
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-1.2.0
>
>
> Hello,
> the reason for protecting the wsdl file, is that the wsdl file can give
> valuable information for starting a Web Service related attack,
> according to the bibliography (see for example: Hacking Exposed, Web Applications, Scambray J., Shema M., McGraw Hill; Hacking Exposed,
> J2EE & Java, Taylor B., Buege R., Layman A., McGraw Hill).
> Spyros Halkidis
--
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
19 years
[JBoss JIRA] Updated: (JBWS-1260) WSDL To Java - Parameter unwrapping fails for a lot of scenarios.
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1260?page=all ]
Thomas Diesler updated JBWS-1260:
---------------------------------
Fix Version/s: (was: jbossws-1.0.5)
> WSDL To Java - Parameter unwrapping fails for a lot of scenarios.
> -----------------------------------------------------------------
>
> Key: JBWS-1260
> URL: http://jira.jboss.com/jira/browse/JBWS-1260
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wstools
> Affects Versions: jbossws-1.0.4
> Reporter: Ole Matzura
> Assigned To: Darran Lofthouse
> Fix For: jbossws-1.2.0
>
>
> Testing parameter unwrapping when using wsdl to java with the following scenarios: -
> A - Element contains anonymous complex type which contains a single element.
> B - Element contains anonymous complex type which contains two elements.
> C - Element references complex type which contains a single element.
> D - Element references complex type which contains two elements.
> E - Element references complex type which contains an anonymous type which contains a single element.
> F - Element references complex type which contains an anonymous type which contains two elements.
> G - Element contains anonymous complex type which contains a single element which is an array. (1)
> H - Element references complex type which contains a single element which is an array. (3)
> I - Element references complex type which contains an anonymous type which contains a single element which is an array. (5)
> J - Element contains anonymout complex type which contains an empty sequence.
> K - Element references complex type which contains an empty sequence.
> L - Element references complex type which contains an anonymous type which contains an empty sequence.
> Scenarios A, B, and G are failing with the following error: -
> org.jboss.ws.WSException: String passed is null
> at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:455)
> at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:137)
> at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113)
> Scenario D
> The parameter is being unwrapped even though it contains two elements, one of the elements is being lost.
> Scenarios E, F, I, and L are failing with the following error: -
> java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
> at javax.xml.namespace.QName.<init>(Unknown Source)
> at javax.xml.namespace.QName.<init>(Unknown Source)
> at org.jboss.ws.tools.WSDLToJava.unwrapResponseParticles(WSDLToJava.java:316)
> Scenarios J, and K are failing with the following error: -
> org.jboss.ws.WSException: Attempt to unwrap a response type with no particles
> at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:285)
> at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:540)
--
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
19 years
[JBoss JIRA] Created: (JBWS-1336) JAXWSDeployerJSE throws NPE
by Anil Saldhana (JIRA)
JAXWSDeployerJSE throws NPE
---------------------------
Key: JBWS-1336
URL: http://jira.jboss.com/jira/browse/JBWS-1336
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Anil Saldhana
Priority: Critical
Attachments: xacml-requestattrib.war
JAXWSDeployerJSE is throwing a NPE for the attached war.
==============================================================
14:22:14,656 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta (build: CVSTa
g=HEAD date=200611071417)] Started in 27s:188ms
14:22:20,156 INFO [MainDeployer] deploy, url=file:/C:/cygwin/home/asaldhana/jbo
ss-5.0/jboss-head/testsuite/output/lib/xacml-requestattrib.war
14:22:20,187 ERROR [JAXWSDeployerJSE] Cannot process web deployment
java.lang.NullPointerException
at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:194)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:394)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ws.integration.jboss50.JAXWSDeployerJSE.isWebServiceDeployment(JAXWSDeployerJSE.java:79)
at org.jboss.ws.integration.jboss50.AbstractDeployer.deploy(AbstractDeployer.java:55)
at org.jboss.ws.integration.jboss50.AbstractJSEDeployer.deploy(AbstractJSEDeployer.java:85)
================================================================
I think the deploer is trying to load a bean that does not exist.
--
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
19 years