February 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2529) Missing type in generated WSDL part definition

by Alessio Soldano (JIRA)

Missing type in generated WSDL part definition ---------------------------------------------- Key: JBWS-2529 URL: https://jira.jboss.org/jira/browse/JBWS-2529 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 Running CXF java2wsdl tool on a service implementation like this @WebService @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding.ParameterStyle.BARE) public class webParamWebService { ... @WebMethod(operationName="helloString8", action="urn:HelloString8") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding .ParameterStyle.WRAPPED) public String hello8(@WebParam (name="string8") String name, Address address) { return "hello8 : " + address.getCity() + " to Web Service"; } } seems to cause a wrong wsdl being generated: ... <wsdl:message name="helloString8"> <wsdl:part name="parameters"> </wsdl:part> </wsdl:message> <wsdl:message name="helloString8Response"> <wsdl:part name="parameters"> </wsdl:part> </wsdl:message> ... The wsdl:part only have name parameter. This is currently preventing the webparam1 reverse test configuration in jws tck5 module, as the obtained wsdl cannot then be consumed by wsdl2java (because it's broken) We should reproduce this and see if this is actually a cxf issue or an integration one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1941) Fault handler chain is not called when user application exceptions are thrown

by Alessio Soldano (JIRA)

Fault handler chain is not called when user application exceptions are thrown ----------------------------------------------------------------------------- Key: JBWS-1941 URL: http://jira.jboss.com/jira/browse/JBWS-1941 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.2 Reporter: Alessio Soldano Assigned To: Alessio Soldano The fault handler chain not called when user application exception are thrown (while runtime and common soap exception cause the right handler chain to be processed). This can can be reproduced adding an handler to the exception sample test case. -- 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

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2333) Refactor ArchiveDeployerHook.getWebservicesMetaData() to Separate Deployer

by Richard Opalka (JIRA)

Refactor ArchiveDeployerHook.getWebservicesMetaData() to Separate Deployer -------------------------------------------------------------------------- Key: JBWS-2333 URL: https://jira.jboss.org/jira/browse/JBWS-2333 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.3, jbossws-metro-3.0.3, jbossws-native-3.0.3 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 We do the following in <b>org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.getWebservicesMetaData(DeploymentUnit unit)</b> <pre> /** Unmrashall the webservices.xml if there is one */ protected WebservicesMetaData getWebservicesMetaData(DeploymentUnit unit) { WebservicesMetaData wsMetaData = unit.getAttachment(WebservicesMetaData.class); UnifiedVirtualFile vfWebservices = getWebservicesFile(unit); if (wsMetaData == null && vfWebservices != null) { try { URL wsURL = vfWebservices.toURL(); Element root = DOMUtils.parse(wsURL.openStream()); String namespaceURI = root.getNamespaceURI(); if (namespaceURI.equals("http://java.sun.com/xml/ns/j2ee")) { Unmarshaller unmarshaller = UnmarshallerFactory.newInstance().newUnmarshaller(); ObjectModelFactory factory = new WebservicesFactory(wsURL); wsMetaData = (WebservicesMetaData)unmarshaller.unmarshal(wsURL.openStream(), factory, null); unit.addAttachment(WebservicesMetaData.class, wsMetaData); } } catch (Exception ex) { throw new WSFDeploymentException(ex); } } return wsMetaData; } </pre> It integrates with deployers improperly. This method should be refactored to separate deployer that does this translation job from webservices.xml -> WebservicesMetaData class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2522) IncompleteDeploymentException caused by NPE

by Juergen Zimmermann (JIRA)

IncompleteDeploymentException caused by NPE ------------------------------------------- Key: JBWS-2522 URL: https://jira.jboss.org/jira/browse/JBWS-2522 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.5 Environment: JBossAS 5.0.0.GA updated with JBossWS-Native 3.0.5, JDK 1.6.0_11 Reporter: Juergen Zimmermann I'll attach a testcase: 1 EAR containing 1 EJB module with JBossWS. During deployment I get this stacktrace: 17:42:06,267 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/ state=ClassLoader mode=Manual requiredState=PostClassLoader org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/hskaWS.jar/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.metadata.process.processor.ejb.jboss.SetDefaultLocalBusinessInterfaceProcessor.process(SetDefaultLocalBusinessInterfaceProcessor.java:114) at org.jboss.metadata.process.chain.ejb.jboss.JBossMetaDataProcessorChain.process(JBossMetaDataProcessorChain.java:115) at org.jboss.ejb3.deployers.Ejb3MetadataProcessingDeployer.deploy(Ejb3MetadataProcessingDeployer.java:128) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 24 more 17:42:06,289 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS IN ERROR: Name -> Error vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/ -> java.lang.NullPointerException at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2563) Useless Warning Message

by Fernando Ribeiro (JIRA)

Useless Warning Message ----------------------- Key: JBWS-2563 URL: https://jira.jboss.org/jira/browse/JBWS-2563 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Fernando Ribeiro The "Ignore child type" message in org.jboss.ws.core.soap.EnvelopeBuilderDOM looks so to me, the priority can be lowered without any compromises. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2327) Create test that tests wsrunclient shell script

by Richard Opalka (JIRA)

Create test that tests wsrunclient shell script ----------------------------------------------- Key: JBWS-2327 URL: https://jira.jboss.org/jira/browse/JBWS-2327 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.3, jbossws-metro-3.0.3, jbossws-native-3.0.3 Reporter: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 Test have to be cross platform and it will test wsrunclient of metro and cxf integrations too in the future (thus should reside in framework code base) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2537) Simplify Hudson Jobs

by Richard Opalka (JIRA)

Simplify Hudson Jobs -------------------- Key: JBWS-2537 URL: https://jira.jboss.org/jira/browse/JBWS-2537 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.1.1, jbossws-metro-3.1.1, jbossws-cxf-3.1.1 There are many copy/pastes in jobs/config.xml files that are identical. This should be part of shell script that should be included in each config.xml file and its functions should be called. This will help us don't touch config.xml files, simple update of framework code will be sufficient to apply changes, thus no hudson updates, restarts, job modifications will be necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2531) Check testsuite & hudson integration

by Alessio Soldano (JIRA)

Check testsuite & hudson integration ------------------------------------ Key: JBWS-2531 URL: https://jira.jboss.org/jira/browse/JBWS-2531 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Priority: Critical Fix For: jbossws-cxf-3.1.0 This is definitely not good: http://jbossws.jboss.org:8180/hudson/job/CXF-Core-AS-4.2.2/68/console , ie. a compilation failure does not cause the main build to fail, thus a blue dot is generated by hudson. This might shadow issues. Moreover, I'm seeing something weird locally, ie. running something like mvn -Ptestsuite,jboss500 -Dtest=wsse/**/*TestCase test cause the build to fail because not test is found in the jbossws-cxf server module. A workaround is to specify -DfailIfNoTests=false on the command line, but that was not required previously. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2564) Use Server MBean instead of ServerConfig to get JBoss version

by Alessio Soldano (JIRA)

Use Server MBean instead of ServerConfig to get JBoss version ------------------------------------------------------------- Key: JBWS-2564 URL: https://jira.jboss.org/jira/browse/JBWS-2564 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.1.1, jbossws-metro-3.1.1, jbossws-cxf-3.1.1 The VersionNumber attribute from Server MBean is the right source for the integration target version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2559) Review EndpointMetaData and ConfigObservable

by Darran Lofthouse (JIRA)

Review EndpointMetaData and ConfigObservable -------------------------------------------- Key: JBWS-2559 URL: https://jira.jboss.org/jira/browse/JBWS-2559 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Reporter: Darran Lofthouse Fix For: jbossws-native-3.1.1 The implementation currently has: - private List<WeakReference<Observer>> observer = new ArrayList<WeakReference<Observer>>(); However there is nothing to remove the WeakReference as it looses it's reference. Secondly notifyOberservers has: - for (WeakReference<Observer> w : observer) { Observer tmp = w.get(); tmp.update(this, arg); } As w is a WeakReference the value from get should be checked to ensure it is not null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2009