May 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1462) JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request.

by Darran Lofthouse (JIRA)

JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request. -------------------------------------------------------------------------------------------------------------- Key: JBWS-1462 URL: http://jira.jboss.com/jira/browse/JBWS-1462 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 If an incomming request has the JMSCorrelationID set it should be set on the outgoing response message as this is a mechanism that can be used to track which responses correspond to which requests. -- 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

16 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1652) ServiceEndpoint requirements for JBossESB

by Tom Fennelly (JIRA)

ServiceEndpoint requirements for JBossESB ----------------------------------------- Key: JBWS-1652 URL: http://jira.jboss.com/jira/browse/JBWS-1652 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Fennelly JBossESB implements what it calls a "JBossWSAdapter" (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). This class allows the ESB to expose JBossWS endpoints through the ESB i.e. over all transport protocols supported by the ESB. In order to do this, JBossWSAdapter currently relies on a number of non-public JBossWS classes (tested against jbossws-1.0.3.SP1 only). After talking with Thomas (at JavaOne), we established that JBossWS will have a public API that will fit our requirements. This JIRA is just to track the ESB requirements in this area. So the ESB needs the following: 1. The ability to "lookup" a JBossWS ServiceEndpoint (or its equivalent in the new API). We currently use the ServiceEndpointManagerFactory to do this. 2. The ability to invoke the ServiceEndpoint to process a SOAP payload (ala the "ServiceEndpoint.handleRequest" method in jbossws-1.0.3.SP1). 3. The ability to register/deploy endpoint implementations. Thomas showed me how this can be done, but I forget the exact code now without having the code in front of me :-) 4. The ability to get the endpoint WSDL from the ServiceEndpoint instance (ala the ServiceEndpoint.handleWSDLRequest method in jbossws-1.0.3.SP1). -- 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

16 years

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1498) Hudson build fails under Windows

by Alejandro Guizar (JIRA)

Hudson build fails under Windows -------------------------------- Key: JBWS-1498 URL: http://jira.jboss.com/jira/browse/JBWS-1498 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-1.2.0, jbossws-2.0.0 Environment: Windows XP Pro Reporter: Alejandro Guizar In target hudson-setup: <exec executable="basename" outputproperty="svn.basename"> <arg value="${svn.url}"/> </exec> <exec executable="dirname" outputproperty="svn.basedir.local"> <arg value="${basedir}"/> </exec> Neither basename nor dirname are standard Windows commands. Targets hudson-start and hudson-stop invoke script catalina.sh to start/stop the web server. This is non portable as well. -- 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

16 years

4
10
0 / 0

[JBoss JIRA] Created: (JBWS-1325) Add support for virtual-hosts for EJB2.1 endpoints

by Darran Lofthouse (JIRA)

Add support for virtual-hosts for EJB2.1 endpoints -------------------------------------------------- Key: JBWS-1325 URL: http://jira.jboss.com/jira/browse/JBWS-1325 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.0.5 This will require a change to the jboss.xml deployment descriptor to allow this to be specified. -- 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

16 years

5
8
0 / 0

[JBoss JIRA] Created: (JBWS-1449) Generate extra XML schema file for SOAP message in document style web service

by qi liu (JIRA)

Generate extra XML schema file for SOAP message in document style web service ----------------------------------------------------------------------------- Key: JBWS-1449 URL: http://jira.jboss.com/jira/browse/JBWS-1449 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: qi liu The schema is currently inlined in the wsdl. An extra schema file is needed. -- 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

16 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1431) Merge ws-security config with jaxrpc/jaxws config

by Thomas Diesler (JIRA)

Merge ws-security config with jaxrpc/jaxws config ------------------------------------------------- Key: JBWS-1431 URL: http://jira.jboss.com/jira/browse/JBWS-1431 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc, jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 The config data should be in standard jbossws client/server side config files. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1382) Provide access to servlet init params

by Thomas Diesler (JIRA)

Provide access to servlet init params ------------------------------------- Key: JBWS-1382 URL: http://jira.jboss.com/jira/browse/JBWS-1382 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.6 -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1402) Ejb3 JMSTransportSupport

by John Gilbert (JIRA)

Ejb3 JMSTransportSupport ------------------------ Key: JBWS-1402 URL: http://jira.jboss.com/jira/browse/JBWS-1402 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Environment: I made these changes to work with JBossWS 1.0.3 and JBoss AS 4.0.4. Reporter: John Gilbert Allow the use of Ejb3 MDBs to support soap over jms. Note: This is a different solution then outlined in the referenced forum discussion. Here is a sample Ejb3 MDB which is also annotated with JWS annotations: @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/AuthorizationCallbackQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable") }) @WebService(name = "AuthorizationCallbackService", serviceName = "AuthorizationCallbackService") @SOAPBinding(style = Style.RPC, use = Use.LITERAL, parameterStyle = ParameterStyle.BARE) @SOAPMessageHandlers( { @SOAPMessageHandler(className = "org.jboss.ws.wsse.WSSecurityHandlerInbound") }) @SecurityDomain("portal") public class AuthorizationCallbackMDB extends JMSTransportSupport implements MessageListener { @WebMethod @Oneway public void authorizationResponse(@WebParam(name = "paymentId") long paymentId, @WebParam(name = "status") boolean status) throws java.rmi.RemoteException { ... } } The following changes where made to get this to work: jbossws-core.jar -> org.jboss.ws.server.ServiceEndpointInfo constructor } else if (udi.type == UnifiedDeploymentInfo.Type.JSR181_EJB3) { String ejbName = sepMetaData.getLinkName(); UnifiedApplicationMetaData applMetaData = (UnifiedApplicationMetaData) udi.metaData; UnifiedBeanMetaData beanMetaData = (UnifiedBeanMetaData) applMetaData .getBeanByEjbName(ejbName); if (beanMetaData instanceof UnifiedMessageDrivenMetaData) { this.type = Type.MDB21; } else { this.type = Type.SLSB30; } } jbossws-jboss-integration.jar -> org.jboss.ws.integration.jboss.DeployerInterceptorEJB3 protected UnifiedDeploymentInfo createUnifiedDeploymentInfo(DeploymentInfo di) throws Exception { ... for (Object container : ejb3Module.getContainers().values()) { if (container instanceof StatelessContainer) { StatelessContainer slc = (StatelessContainer) container; UnifiedBeanMetaData uslc = new UnifiedBeanMetaData(); uslc.setEjbName(slc.getEjbName()); uslc.setEjbClass(slc.getBeanClassName()); beans.add(uslc); } if (container instanceof MDB) { MDB mdc = (MDB) container; if (mdc.resolveAnnotation(WebService.class) != null) { UnifiedBeanMetaData umdc = new UnifiedMessageDrivenMetaData(); umdc.setEjbName(mdc.getEjbName()); umdc.setEjbClass(mdc.getBeanClassName()); ActivationConfigPropertyMetaData p = (ActivationConfigPropertyMetaData) mdc .getActivationConfigProperties().get("destination"); ((UnifiedMessageDrivenMetaData) umdc) .setDestinationJndiName(p.getValue()); beans.add(umdc); } } } ... } protected boolean isWebserviceDeployment(DeploymentInfo di) { ... for (Object manager : ejb3Module.getContainers().values()) { if (manager instanceof StatelessContainer) { StatelessContainer container = (StatelessContainer) manager; if (container.resolveAnnotation(WebService.class) != null) { isWebserviceDeployment = true; break; } } if (manager instanceof MDB) { MDB container = (MDB) manager; if (container.resolveAnnotation(WebService.class) != null) { isWebserviceDeployment = true; break; } } } ... } The only thing I couldn't fix was the generated endpoint address in the wsdl. It still comes out like this <soap:address location='http://localhost:8080/payment-authorizer-0/AuthorizationCallbackMDB'/> instead of something like this <soap:address location='jms://localhost/queue/AuthorizationCallbackQueue'/> On a similar note I have created a straight forward jboss remoting JmsClientInvoker. It only works with Oneway messages, which is reasonable. -- 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

16 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1432) WSDL to Java - If parameters can not be unwrapped fall back to bare and log a warning.

by Darran Lofthouse (JIRA)

WSDL to Java - If parameters can not be unwrapped fall back to bare and log a warning. --------------------------------------------------------------------------------------- Key: JBWS-1432 URL: http://jira.jboss.com/jira/browse/JBWS-1432 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: wstools Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.0.CR1 WSDL to Java - If parameters can not be unwrapped fall back to bare and log a warning. At the moment unless the parameters for all operations can be unwrapped we throw an exception and stop processing the WSDL. If instead we unwrap what we can it will make it a lot easier to configure WSDL to Java and users will not need to worry about setting the parameter-style unless they want to force bare style. -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1459) Java to WSDL - Incorrect handling of arrays with bare parameter style

by Darran Lofthouse (JIRA)

Java to WSDL - Incorrect handling of arrays with bare parameter style --------------------------------------------------------------------- Key: JBWS-1459 URL: http://jira.jboss.com/jira/browse/JBWS-1459 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.2.0.CR2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 Java to WSDL - Incorrect handling of arrays with bare parameter style The following method on a SEI: - public String[] lookup(final String[] person) throws RemoteException; The following type is generated in the WSDL: - <complexType name='String.Array'> <sequence> <element maxOccurs='unbounded' minOccurs='0' name='value' nillable='true' type='string'/> </sequence> </complexType> This type is not mapped in the generated JAX-RPC mapping so the following error is reported on deployment: - Caused by: org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://www.jboss.org/support/phonebook/types}String.Array at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processDocElement(JAXRPCMetaDataBuilder.java:613) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:865) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:214) at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:219) at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:81) at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:127) at org.jboss.ws.integration.jboss42.DeployerInterceptorJSE.createServiceEndpoint(DeployerInterceptorJSE.java:130) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) -- 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

16 years, 2 months

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 May 2007