December 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1309) Support xml overrides for @PortComponent

by Jason T. Greene (JIRA)

Support xml overrides for @PortComponent ---------------------------------------- Key: JBWS-1309 URL: http://jira.jboss.com/jira/browse/JBWS-1309 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Jason T. Greene Fix For: jbossws-2.0.0 Similar to EJB3 annotations, we need to support an xml override for the PortComponent annotation. The information will then need to be pulled from the JBoss metadata. -- 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

14 years, 10 months

7
22
0 / 0

[JBoss JIRA] Created: (JBWS-1397) Fix <wsdl-publish-location> for jboss-5.0.x

by Thomas Diesler (JIRA)

Fix <wsdl-publish-location> for jboss-5.0.x ------------------------------------------- Key: JBWS-1397 URL: http://jira.jboss.com/jira/browse/JBWS-1397 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 [tdiesler@localhost test]$ ant -Dtest=org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0.971 sec [junit] Test org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase FAILED -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1312) Fix JMS transport in trunk

by Jason T. Greene (JIRA)

Fix JMS transport in trunk -------------------------- Key: JBWS-1312 URL: http://jira.jboss.com/jira/browse/JBWS-1312 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Fix For: jbossws-2.0.0 -- 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 months

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-1316) Add support for a configurable time tolerance value that handles clock skew

by Jason T. Greene (JIRA)

Add support for a configurable time tolerance value that handles clock skew --------------------------------------------------------------------------- Key: JBWS-1316 URL: http://jira.jboss.com/jira/browse/JBWS-1316 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Reporter: Jason T. Greene Fix For: jbossws-1.0.5 -- 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, 8 months

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

5
8
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, 10 months

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

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

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2006