December 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1429) Cleanup PortComponent annotation

by Heiko Braun (JIRA)

Cleanup PortComponent annotation -------------------------------- Key: JBWS-1429 URL: http://jira.jboss.com/jira/browse/JBWS-1429 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0.CR2 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.0.CR3 Break up into several, more specific annotations -- 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
1
0 / 0

[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

17 years, 11 months

1
2
0 / 0

[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

17 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1396) Now jbossws-beans is exploded jbossws.sar must be exploded

by Darran Lofthouse (JIRA)

Now jbossws-beans is exploded jbossws.sar must be exploded ---------------------------------------------------------- Key: JBWS-1396 URL: http://jira.jboss.com/jira/browse/JBWS-1396 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Darran Lofthouse Fix For: jbossws-1.0.5 The archive jboss.beans has now been converted as an exploded deployment within jbossws.sar, It is not possible to have an exploded archive within a non-exploded archive so now jbossws.sar must be exploded before deployment. To avoid confusion the jbossws.sar in the distribution should also be exploded. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBWS-1343) Synchronize code bases in branch & trunk

by Thomas Diesler (JIRA)

Synchronize code bases in branch & trunk ---------------------------------------- Key: JBWS-1343 URL: http://jira.jboss.com/jira/browse/JBWS-1343 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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
3
0 / 0

[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

17 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1406) WS-Eventing: event notification failure

by Alessio Soldano (JIRA)

WS-Eventing: event notification failure --------------------------------------- Key: JBWS-1406 URL: http://jira.jboss.com/jira/browse/JBWS-1406 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-eventing Affects Versions: jbossws-1.0.4 Environment: JBoss 4.0.4.GA, JBossWS 1.0.4.GA Reporter: Alessio Soldano Attachments: dsvn.txt We noticed that event notification failures are completely lost. If an event notification fail (for example because the event sink is down) the current jbossws engine just logs the error and does nothing else. Of course it could be useful at least to keep track of failed notification in order to analyze the problem, send them again later or simply to warn the sink's owner. -- 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

[JBoss JIRA] Created: (JBWS-1426) Release jbossws-1.2.0.CR1

by Thomas Diesler (JIRA)

Release jbossws-1.2.0.CR1 ------------------------- Key: JBWS-1426 URL: http://jira.jboss.com/jira/browse/JBWS-1426 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 The release criteria for jbossws-1.1.0.GA are: * pass all internal jbossws tests * pass all portable j2ee-1.4 tests from the jboss testsuite * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite * generate all test artifacts with wstools -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-1409) WsdlGenerator crashes on void-methods

by Thomas Diesler (JIRA)

WsdlGenerator crashes on void-methods ------------------------------------- Key: JBWS-1409 URL: http://jira.jboss.com/jira/browse/JBWS-1409 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Thomas Diesler The automatic generation of a wsdl to deploy time crashes, if there is a method which returns void. Changing the return parameter to everything else besides void (i.e. String, boolean, ..) fixes the problem. Using JBoss 4.04 with JBossWS 1.0.4 + jboss-xml-binding.jar 1.0.0.CR7. Seems this bug http://jira.jboss.org/jira/browse/JBWS-647 is back in 1.0.4 again. Quote: 2006-11-22 16:16:35,181 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/jzx/zxdev_jboss/server/default/tmp/deploy/tmp19079zxapp_webservices.ear-contents/zxapp_webservices_logic.jar java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:559) at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:146) at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:249) at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:170) at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:321) at org.jboss.ws.deployment.AnnotationsMetaDataBuilder.processOrGenerateWSDL(AnnotationsMetaDataBuilder.java:93) at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:177) at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75) at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106) at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80) at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44) -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-1399) JBWS-1178 implementation trouble

by Stefano Maestri (JIRA)

JBWS-1178 implementation trouble -------------------------------- Key: JBWS-1399 URL: http://jira.jboss.com/jira/browse/JBWS-1399 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Stefano Maestri I got jbossws-1.0.4 and I installed it in my environment (for the description of the environment refer to my original blog post about multiple virtual host: http://www.javalinux.it/blogs/index.php?title=multiple_virtual_host_and_s... ). There are some problems * If I follow instruction in jboss-beans.xml leaving webservicehost as a null string I get this Exception during deploy of jbossws: Code: 09:11:02,349 ERROR [AbstractKernelController] Error installing to Configured: name=ServiceEndpointMa nager state=Instantiated mode=Manual requiredState=Create java.lang.IllegalArgumentException: Null value metadata at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java :487) at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java :434) at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.jav a:398) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(Ab [...] *** DEPLOYMENTS IN ERROR: ServiceEndpointManager -> java.lang.IllegalArgumentException: Null value metadata If I comment the webServiceHost tag the deploy works correctly. I think here the explaination in the commented part of jboss-beans.xml have to be changed . * The current implementation only replaces the host name, but not the port used to call the webservice. I think the port replacing is also very important in an environment of complete virtual hosting like our one. Using Linux Virtual Server is normal to virtualize ports. For example we use ports > 1024 on real servers and standard 80/443 ports on virtual servers * You didn't apply the patch on showServiceEndpointTable method in ServiceEndPointManager. This method is called from context servlets and IMHO have to replace host and ports accordingly to wsdl's replacing. Otherwise you get an horrible list of wsdl pointing to "http://jbossws.undefined.host/..." and of course links do not work -- 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
4
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