November 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Can I point a wsconsume-generated client to a local WSDL

by Brad Marshall

Brilliant. That works. Thanks Richard. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102256#4102256 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102256

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: service-name-pattern

by richard.opalka＠jboss.com

There's no source code that would read service-name-pattern element content at all. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102253#4102253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102253

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: service-name-pattern

by Sefai

I added this handler-chain in standard-jaxws-endpoint-config.xml,and it didn't work,then I added it in standard-jaxws-client-config.xml,I looked into the DEBUG output,and didn't see any anything regarding this config during deployment.So I posted here. Then I worked on it more, and discovered that this client-config is loaded after you call it,not during deployment,and if you put service-name-pattern in endpoint-config you get an exception,but you dont get any exceptions if you put this in client-config. Also the web-service-call I want to make with secure works smooth, and other web-services-call I make continue to work without any security constraint,meaning this pattern provides us using different authentication mechanisms. When I logged in this forum to post the resolution I saw your reply and I am confused. I changed the service-name-pattern definiton to point to an unsecured web-service-client,to test if it worked before by chance. But it didn't,it throw exception as excepted. And I am now confused more. You say it is not supported,but it works as expected. Can you enlighten me please? best regards... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102216#4102216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102216

16 years, 7 months

1
0
0 / 0

[JBossWS] - Design question - initializing and cleaning up resources

by dode

I am developing a POJO SEI deployed as WAR to JBoss 4.0.5, JBossWS 2.0.1.GA. I am unsure how I would initialize resources such as JMS connections on deployment and how to clean them up on undeployment. I looked at ServiceLifecycle, but since the init() and destroy() methods are called for each webservice call, it does not seem to be a good idea to perform expensive operations in them. Would it make more sense to implement the webservice as EJB3 SLSB? Can someone give me some advice? Torsten View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102205#4102205 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102205

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: How to do cleanup when undeploying webservice

by dode

To anyone having the same question: Have your SEI implement javax.xml.rpc.server.ServiceLifecycle. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102201#4102201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102201

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: JBoss Transaction Integration Status

by adinn

Hi Ted, Before answering your question I'll just note that the current XTS package in JBossTS already allows JaxWS clients and servers to participate in transactions using the 1.0 WSCOOR protocols. All that is need is to configure the client and server with the SOAP handlers supplied in the package. However, this WSCOOR implementation is based on a 'home-grown' soap stack embedded in the XTS implementation. I am currently extending XTS to provide a wscoor 1.1 conformant implementation of web service transactions based on JaxWS. The WSCOOR, WSAT and WSBA 1.1 services are exposed as JaxWS endpoints. Client code will normally only access these services via a suitably configured UserTransaction or TransactionManager class but it should be possible to go 'under the hood' to configure the JaxWS layer e.g. with logging interceptors, etc. This new XTS will rely upon on the JaxWS implementation provided by JBossWS. in App Server 5.0. However, it is not tied to the JBoss implementation, for two reasons. In AS 5.0 JBossWS is being split into a generic API layer and an implementation layer (called JBossWS-Native). This will allow alternative WS implementaions to be dropped into the AS in place of JBossWS-Native. Furthermore, the XTS implementation only relies on generic JaxWS features so it should be able to run directly over any fully compliant JaxWS 2.1 implementation, e.g. by dropping the TS and XTS implementation into a different app server. WSCOOR 1.0 support should still be available alongside this new implementation by retaining the 'home-grown' soap stack currently embedded in the XTS package. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102168#4102168 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102168

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: service-name-pattern

by richard.opalka＠jboss.com

Hi, unfortunately javaee:service-name-pattern element isn't supported by jbossws post-handler-chains configuration. However, you're doing your job right. Create new JAX-WS client config, define there your post-handler-chains configurations but use config-name instead of service-name-pattern subelement. The last step you should do is to refer to this config by annotating the SEI interface, you're using on your client side. Here's the example. @EndpointConfig(configName = "Config Name Sample", configFile = "META-INF/custom-jaxws-client-config.xml") | public interface SEI { ... } | Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102115#4102115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102115

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Using custom exception inheritance

by richard.opalka＠jboss.com

"dode" wrote : | What am I missing? | Torsten You have to use javax.xml.bind.annotation.* annotations. Take a look to Java Types To XML chapter of JAXB 2.1 specification. I suggest you to write your wsdl first with exceptions inheritance inside and use wsprovide to generate the java artifacts for you. Then you can study them to get familiar how to do it. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102113#4102113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102113

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Can I point a wsconsume-generated client to a local WSDL

by richard.opalka＠jboss.com

"Brad Marshall" wrote : Can I easily override the Service class?s retrieval of the WSDL from the Web service and point it instead at a local copy of the WSDL file? In out environment, every caller of the Web service also implements their own Web service with the identical interface, so we can enforce a rule that they have a copy local of the valid WSDL file. | URL wsdlURL = new File("resources/YourService.wsdl").toURL(); | QName serviceName = new QName("yourWsdlNs", "ServiceQName"); | Service service = Service.create(wsdlURL, serviceName); | Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102105#4102105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102105

16 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Problem deploying WebServices

by richard.opalka＠jboss.com

Hi, your eclipse workspace has Axis webservices jars in the classpath. If you want to enforce it to use JBoss native webservices, you must ensure that JBoss native webservices jars are before Axis jars in the classpath. Another approach to activate JBossWS native webservices is to set up the following properties in your eclipse workspace environment: -Djavax.xml.soap.MessageFactory=org.jboss.ws.core.soap.MessageFactoryImpl | -Djavax.xml.soap.MetaFactory=org.jboss.ws.core.soap.SAAJMetaFactoryImpl | -Djavax.xml.soap.SOAPFactory=org.jboss.ws.core.soap.SOAPFactoryImpl | Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102097#4102097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102097

16 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users November 2007