[JBoss JIRA] Created: (JBWS-2972) WSProvide tool throws WSExcepton for WebServiceProvider annotated endpoints
by Richard Opalka (JIRA)
WSProvide tool throws WSExcepton for WebServiceProvider annotated endpoints
---------------------------------------------------------------------------
Key: JBWS-2972
URL: https://jira.jboss.org/jira/browse/JBWS-2972
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.3.0.CR1
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-3.3.0
org.jboss.ws.WSException: Cannot obtain @WebService annotation from: com.sun.ts.tests.jaxws.ee.j2w.document.literal.restful.server.TokensImpl
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processWebService(JAXWSWebServiceMetaDataBuilder.java:290)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:105)
at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:108)
at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:124)
at org.jboss.wsf.spi.tools.cmd.WSProvide.generate(WSProvide.java:183)
at org.jboss.wsf.spi.tools.cmd.WSProvide.main(WSProvide.java:76)
--
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, 6 months
[JBoss JIRA] Created: (JBWS-2971) Write published wsdl to file on deploy
by Alessio Soldano (JIRA)
Write published wsdl to file on deploy
--------------------------------------
Key: JBWS-2971
URL: https://jira.jboss.org/jira/browse/JBWS-2971
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-3.3.0
JBossWS-CXF currently does not write file(s) to disk with the deployed wsdl(s) and referenced schemas for a given endpoint. This can probably be done building the bus corresponding to the endpoint at deploy time (need to figure out if this can happen before the webapp is actually created or needs to happen later), invoking the CXF ServiceWSDLBuilder and then pushing the obtained wsdl definition to a modified version of the Native WSDLFilePublisher for writing the files.
--
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, 6 months
[JBoss JIRA] Updated: (JBWS-2964) SOAPMessageImpl.saveChanges() changed the referenced mimeHeaders
by Jim Ma (JIRA)
[ https://jira.jboss.org/jira/browse/JBWS-2964?page=com.atlassian.jira.plug... ]
Jim Ma updated JBWS-2964:
-------------------------
Description:
When the mimeHeaders value is from another soap message's mimeHeaders , the mimeHeader modification will probably change the referenced mimeHeaders.
was:
There is code in TCK to create a tmp soapmessage used to dump the outbound soap message:
1 baos = new ByteArrayOutputStream();
2 msg.writeTo(baos);
3 MessageFactory mf = MessageFactory.newInstance();
4 SOAPMessage tmpMsg = mf.createMessage(msg.getMimeHeaders(),
5 new ByteArrayInputStream(baos.toString().getBytes()));
6 tmpMsg.removeAllAttachments();
7 tmpMsg.saveChanges();
Line7 will change the msg's mimeHeaders value . This is not expected.
This issue is the cause of two tck failures : com.sun.ts.tests.jaxws.api.javax_xml_ws_handler.LogicalMessageContext.Client.java#ContextPropertiesTest_from_standalone()
com.sun.ts.tests.jaxws.api.javax_xml_ws_handler_soap.SOAPMessageContext.Client.java#ContextPropertiesTest_from_standalone()
Security: Public (was: JBoss Internal)
> SOAPMessageImpl.saveChanges() changed the referenced mimeHeaders
> ----------------------------------------------------------------
>
> Key: JBWS-2964
> URL: https://jira.jboss.org/jira/browse/JBWS-2964
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Affects Versions: jbossws-native-3.3.0.Beta4
> Reporter: Jim Ma
> Assignee: Jim Ma
> Fix For: jbossws-native-3.3.0.CR1
>
>
> When the mimeHeaders value is from another soap message's mimeHeaders , the mimeHeader modification will probably change the referenced mimeHeaders.
--
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, 6 months
[JBoss JIRA] Updated: (JBWS-2949) JBossWS native does not ignore handler chains containing illegal namespace prefix in handler chains configuration file
by Jim Ma (JIRA)
[ https://jira.jboss.org/jira/browse/JBWS-2949?page=com.atlassian.jira.plug... ]
Jim Ma updated JBWS-2949:
-------------------------
Description: When there is illegal namespace prefix in one handler chain, it will cause the whole deployment failed. It should ignore this error handler chain configuration and give some warning message. (was: When there is illegal namespace prefix in one handler chain, it will cause the whole deployment failed. It should ignore this error handler chain configuration and give some warning message.
-------------Stack trace-----------
WSRLHandlerService_web.war/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/x1/code/EAP-TCK/tck_home/work/jboss-5.1.0.GA/server/default/deploy/WSRLHandlerService_web.war/
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.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
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:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
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: org.jboss.ws.WSException: Cannot process handler chain: GetTrackerData_handler.xml
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:269)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processHandlerChain(JAXWSMetaDataBuilder.java:174)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:178)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:61)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:64)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129)
at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:76)
at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
... 24 more
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Cannot obtain namespace URI for prefix: foo
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:255)
... 34 more
Caused by: java.lang.IllegalStateException: Cannot obtain namespace URI for prefix: foo
at org.jboss.xb.binding.ObjectModelBuilder.resolveQName(ObjectModelBuilder.java:196)
at org.jboss.wsf.spi.metadata.j2ee.serviceref.HandlerChainsObjectFactory.setValue(HandlerChainsObjectFactory.java:127)
at sun.reflect.GeneratedMethodAccessor329.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.xb.binding.ObjectModelBuilder.invokeFactory(ObjectModelBuilder.java:465)
at org.jboss.xb.binding.DelegatingObjectModelFactory.setValue(DelegatingObjectModelFactory.java:177)
at org.jboss.xb.binding.ObjectModelBuilder.endElement(ObjectModelBuilder.java:401)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:373)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.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:199)
... 37 more
18:57:29,039 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/x1/code/EAP-TCK/tck_home/work/jboss-5.1.0.GA/server/default/deploy/WSRLHandlerService_web.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/x1/code/EAP-TCK/tck_home/work/jboss-5.1.0.GA/server/default/deploy/WSRLHandlerService_web.war/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/x1/code/EAP-TCK/tck_home/work/jboss-5.1.0.GA/server/default/deploy/WSRLHandlerService_web.war/" is in error due to the following reason(s): java.lang.IllegalStateException: Cannot obtain namespace URI for prefix: foo
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
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)
------------handler chains configuration file-------------
<handler-chain>
<port-name-pattern xmlns:ns1="http://dlhandlerservice.org/wsdl">foo:Hello2Port</port-name-pattern>
<handler>
<handler-name>ServerLogicalHandler4</handler-name>
<handler-class>com.sun.ts.tests.jaxws.sharedwebservices.dlhandlerservice.ServerLogicalHandler4</handler-class>
</handler>
</handler-chain>
)
> JBossWS native does not ignore handler chains containing illegal namespace prefix in handler chains configuration file
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBWS-2949
> URL: https://jira.jboss.org/jira/browse/JBWS-2949
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Affects Versions: jbossws-native-3.3.0.Beta4
> Reporter: Jim Ma
> Assignee: Jim Ma
> Fix For: jbossws-native-3.3.0.CR1
>
>
> When there is illegal namespace prefix in one handler chain, it will cause the whole deployment failed. It should ignore this error handler chain configuration and give some warning message.
--
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, 6 months