March 2007 - jbossws-issues - Jboss List Archives

[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, 9 months

2
2
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, 9 months

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, 9 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, 9 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1502) wsdl-java in wstools-config.xml: location should be relative to config file

by David Robison (JIRA)

wsdl-java in wstools-config.xml: location should be relative to config file --------------------------------------------------------------------------- Key: JBWS-1502 URL: http://jira.jboss.com/jira/browse/JBWS-1502 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: David Robison Priority: Minor The wsdl location specified in the wstools-config.xml file should be relative to that file. This helps when building with ant. If I build with ant from the subproject, it builds well. If I build from the parent directory, it cannot find the location. I use "dir/file.wsdl" but that relative path does not work from the parent directory -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1381) Disable HTTP chunking for J2ME client s

by Thomas Diesler (JIRA)

Disable HTTP chunking for J2ME client s --------------------------------------- Key: JBWS-1381 URL: http://jira.jboss.com/jira/browse/JBWS-1381 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.5 How do I disable HTTP chunking for my EJB3 webservices? I am using @WebMethod etc. I need to disable HTTP chunking because my J2ME client (the wireless toolkit) can't handle chunking yet. -- 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1395) Add a Standard All Client Configuration to standard-jbossws-client-config.xml

by John Gilbert (JIRA)

Add a Standard All Client Configuration to standard-jbossws-client-config.xml ----------------------------------------------------------------------------- Key: JBWS-1395 URL: http://jira.jboss.com/jira/browse/JBWS-1395 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: John Gilbert Priority: Trivial It would be nice to have this in addition to Standard Client, Standard Secure Client, and Standard Addressing Client, so that all clients don't have to create their config file. <client-config> <config-name>Standard All Client</config-name> <post-handler-chain> <handler-chain-name>PostHandlerChain</handler-chain-name> <handler> <j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.wsse.WSSecurityHandlerOutbound</j2ee:handler-class> </handler> <handler> <j2ee:handler-name>SOAPClientHandler</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.addressing.soap.SOAPClientHandler</j2ee:handler-class> </handler> </post-handler-chain> </client-config> -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1471) Remove unwated tomcat excludes

by Thomas Diesler (JIRA)

Remove unwated tomcat excludes ------------------------------ Key: JBWS-1471 URL: http://jira.jboss.com/jira/browse/JBWS-1471 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0 # TODO: Why are these excluded org/jboss/test/ws/jaxws/samples/wseventing/** org/jboss/test/ws/jaxrpc/samples/wssecurity/StorePassEncryptTestCase.* -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1461) Migrate our addressing impl to JAXB

by Heiko Braun (JIRA)

Migrate our addressing impl to JAXB ----------------------------------- Key: JBWS-1461 URL: http://jira.jboss.com/jira/browse/JBWS-1461 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: jbossws-2.0.0 When the addressing custom types (epr, etc) will be marshalled by JAXB, they could be easily be reused to represent addressing elements inside the soap body. -- 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, 10 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 March 2007