March 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-2955) Client handler chain configured by annotation does not work

by Jim Ma (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2955?page=com.atlassian.jira.plug... ] Jim Ma updated JBWS-2955: ------------------------- Description: The handler chain configured in client side does not work : @WebServiceClient(name = "EndpointService") @HandlerChain(file = "client-handlers.xml") public class EndpointService extends Service { } . was: The handler chain configured in client side does not work : @WebServiceClient(name = "EndpointService") @HandlerChain(file = "client-handlers.xml") public class EndpointService extends Service { } Tck test com/sun/ts/tests/jaxws/ee/w2j/rpc/literal/handlertest/Client_ClientLogicalHandlerTest_from_standalone is failed for this . > Client handler chain configured by annotation does not work > ----------------------------------------------------------- > > Key: JBWS-2955 > URL: https://jira.jboss.org/jira/browse/JBWS-2955 > 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 > > > The handler chain configured in client side does not work : > @WebServiceClient(name = "EndpointService") > @HandlerChain(file = "client-handlers.xml") > public class EndpointService extends Service { > } > . -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2968) Remove compilation warnings where possible

by Richard Opalka (JIRA)

Remove compilation warnings where possible ------------------------------------------ Key: JBWS-2968 URL: https://jira.jboss.org/jira/browse/JBWS-2968 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.3.0.CR1, jbossws-metro-3.3.0.CR1, jbossws-native-3.3.0.CR1 -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2965) Allow nullable root element when building SchemaBinding

by Alessio Soldano (JIRA)

Allow nullable root element when building SchemaBinding ------------------------------------------------------- Key: JBWS-2965 URL: https://jira.jboss.org/jira/browse/JBWS-2965 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.3.0.CR1 .. required when moving to JBossXB 2.0.2.Beta5 or greater -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2774) Cleaned up dependency in cxf client module

by Jim Ma (JIRA)

Cleaned up dependency in cxf client module ------------------------------------------ Key: JBWS-2774 URL: https://jira.jboss.org/jira/browse/JBWS-2774 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.2.1 There is no aegis related jar files in client library, look at if we need to add other jar files to enable ws-*, aegis etc. Look at if we also can remove the geronimo-*.jar shipped in cxf and use Sun equivalent. -- 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

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2951) StringIndexOutOfBoundsException in JavaUtils#getPackageName()

by Ondrej Žižka (JIRA)

StringIndexOutOfBoundsException in JavaUtils#getPackageName() ------------------------------------------------------------- Key: JBWS-2951 URL: https://jira.jboss.org/jira/browse/JBWS-2951 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: EAP5 Implementation-Title: JBoss Web Services - Common Implementation-Version: 1.1.0.SP2 Reporter: Ondrej Žižka Attachments: HelloWS.war Deploying a class with no package causes String index out of range: -1 because of: String fullName = clazz.getName(); return fullName.substring(0, fullName.lastIndexOf(".")); BTW, why do we have a project-specific JavaUtils... these functionalities must have been coded milion times and with such cases handled. http://commons.apache.org/lang/api-release/org/apache/commons/lang/ClassU... --------------------------------------------------------------------------- Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1937) at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:533) at org.jboss.ws.metadata.wsdl.WSDLUtils.getTypeNamespace(WSDLUtils.java:700) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processWebService(JAXWSWebServiceMetaDataBuilder.java:306) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:104) 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 -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] Updated: (JBWS-2955) Client handler chain configured by annotation does not work

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2955?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2955: ---------------------------------- Security: Public (was: JBoss Internal) > Client handler chain configured by annotation does not work > ----------------------------------------------------------- > > Key: JBWS-2955 > URL: https://jira.jboss.org/jira/browse/JBWS-2955 > 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.Beta5 > > > The handler chain configured in client side does not work : > @WebServiceClient(name = "EndpointService") > @HandlerChain(file = "client-handlers.xml") > public class EndpointService extends Service { > } > Tck test com/sun/ts/tests/jaxws/ee/w2j/rpc/literal/handlertest/Client_ClientLogicalHandlerTest_from_standalone is failed for this . -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-2949) JBossWS native does not ignore handler chains containing illegal namespace prefix in handler chains configuration file

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2949?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2949: ---------------------------------- Summary: JBossWS native does not ignore handler chains containing illegal namespace prefix in handler chains configuration file (was: JBossWS native does not ignore the handler chain which contains illegal namespace prefix in handle chains configuration file) Security: Public (was: JBoss Internal) > 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.Beta5 > > > 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> -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-2927) WSAaddressingClientHandler and WSAaddressingServerHandler don't honor the required value in @Addressing annotation

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2927?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2927: ---------------------------------- Summary: WSAaddressingClientHandler and WSAaddressingServerHandler don't honor the required value in @Addressing annotation (was: WSAaddressingClientHandler and WSAaddressingServerHandler does not honor the required value in Addressing annotation) Security: Public (was: JBoss Internal) > WSAaddressingClientHandler and WSAaddressingServerHandler don't honor the required value in @Addressing annotation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-2927 > URL: https://jira.jboss.org/jira/browse/JBWS-2927 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.2.2 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-native-3.3.0.Beta5 > > > WSAaddressingClientHandler and WSAaddressingServerHandler still checks the wsa header when @Addressing(required=false). It should check the required value first , then decide if needs to read the wsa headers. -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...

by Chris Laprun (JIRA)

JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine... --------------------------------------------------------------------------------------------------------- Key: JBWS-2884 URL: https://jira.jboss.org/jira/browse/JBWS-2884 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Chris Laprun Priority: Blocker I get: Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:570) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:369) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231) when attempting to connect to a remote webservice with JBoss WS but I can access it just fine using SOAPUI. The remote service is defined by: http://portalstandards.oracle.com/portletapp/portlets?WSDL I'm trying to access the getServiceDescription method. SOAP body as generated by JBoss WS is: <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription> Requesting: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:oasis:names:tc:wsrp:v1:types"> <soapenv:Header/> <soapenv:Body> <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription> </soapenv:Body> </soapenv:Envelope> in SOAP UI results in the expected result: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="urn:oasis:names:tc:wsrp:v1:types"> <env:Body> <ns0:getServiceDescriptionResponse> <ns0:requiresRegistration>true</ns0:requiresRegistration> <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:edit_defaults"> <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:edit_defaults"> <ns0:value>This mode signifies that the portlet should render a screen to set the default values for the modifiable preferences that are typically changed in the EDIT screen. Calling this mode requires that the user must have administrator rights.</ns0:value> </ns0:description> </ns0:customModeDescriptions> <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:about"> <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:about"> <ns0:value>This mode should be used by the portlet to display information on the portlet's purpose, origin, version, etc.</ns0:value> </ns0:description> </ns0:customModeDescriptions> </ns0:getServiceDescriptionResponse> </env:Body> </env:Envelope> JBoss WS fails on with the above error. -- 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

14 years, 1 month

5
17
0 / 0

[JBoss JIRA] Created: (JBWS-2963) JavaDoc inconsistency in WSConsume.java

by Rostislav Svoboda (JIRA)

JavaDoc inconsistency in WSConsume.java --------------------------------------- Key: JBWS-2963 URL: https://jira.jboss.org/jira/browse/JBWS-2963 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Rostislav Svoboda Assignee: Jason T. Greene Priority: Minor Inconsistency in WSConsume.java between class JavaDoc and printHelp() method. Please add this to JavaDoc: * <tr><td>-n, --nocompile </td><td>Do not compile generated sources</td></tr> http://anonsvn.jboss.org/repos/jbossws/spi/trunk/src/main/java/org/jboss/... -- 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

14 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2010