October 2009 - jbossws-dev - Jboss List Archives

[JBoss Web Services Development] - How is it determined what web service artifacts are publishe

by RonnieSpike

I'm deploying a group of web services to JBoss. I used NetBeans to generate the java code from wsdl. The following annotation is in the impl class: wsdlLocation = "WEB-INF/wsdl/BrokeredNotification/brw-2Wrapper.wsdl" When the server is started and JBoss logs INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: /server//data/wsdl/.war/BrokeredNotification/brw-2Wrapper.wsdl not all .xsd artifacts are being placed in said directory. They DO exist in the .war file under WEB-INF/wsdl/BrokeredNotification. I first tried deploying with the artifacts in a directory hierarchy, then with a flattened directory. This causes an exception when a client calls the web service because the artifacts can't be found. Don't have that exception before me, but if it's needed to answer my question, I can provide. Thanks! Ronnie View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263076#4263076 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263076

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : | is accessible via httpit's a bug if it isn't. I mean you're able to invoke endpoint operations via HTTP(S) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262885#4262885 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262885

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"jim.ma" wrote : So this correct jms address deployer should be ordered after TomcatDeployer(the war actually started). | | What do you think about this ? | We shouldn't rely on Tomcat deployer :( The fact you'll place your new deployer after tomcat deployer doesn't mean war is deployed and ready to service after tomcat deployer finishes its job. For example if there's a war with many dependencies on other archives, this war won't be started until dependencies are satisfied. IOW your prediction ordered after TomcatDeployer(the war actually started) is wrong. BTW we had many troubles in the past with such expectations and it took us months to fix that. Now all the JBossWS deployers are executed before tomcat deployer by purpose. "jim.ma" wrote : | BTW, I also tried the native jms transport sample . I see there is only jms endpoint registered . The http endpoint is not been list in the services list page . Is it intended ? | I don't know the details of that native sample, but if endpoint in JMS sample is accessible via http, it should be registered with endpoints registry and it's a bug if it isn't. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262884#4262884 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262884

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by jim.ma

CXF jms endpoint can be started without MDB , so the jms address info is only in wsdl or jbossws-cxf.xml. We can write another DeploymentAspect to extract this information . But it seems redundant work to parse the wsdl port address and jbossws-cxf.xml destination configuration. So the another way could be : Place an deployer after TomcatDeployer. In cxf, all the started endpoints will be registered in bus. We can get address info from it . But we only can get it after cxf endpoints started. So this correct jms address deployer should be ordered after TomcatDeployer(the war actually started). What do you think about this ? BTW, I also tried the native jms transport sample . I see there is only jms endpoint registered . The http endpoint is not been list in the services list page . Is it intended ? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262862#4262862 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262862

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"jim.ma" wrote : | Is there any other solution here ? Which way is the better to go ? | I am waiting for your thoughts and comments ... | The correct solution is: * ensure EndpointAddressDA builds correct JMS URI * ensure JMS endpoint is registered with endpoints registry View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261809#4261809 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261809

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"jim.ma" wrote : So far the jms transport testcase I committed in does not register the jms endpoint in EndpointRegistry. | This is wrong of course. Every endpoint have to be registered in endpoints registry. "jim.ma" wrote : | When the jms transport is enabled , we can see the endpoint address is http or https. Can we modify it to real correct jms address value ? | You mean soap:address in published WSDL? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261808#4261808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261808

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by jim.ma

So far the jms transport testcase I committed in does not register the jms endpoint in EndpointRegistry. If we list the services , there is one one endpoint listed in page and the jms transport endpoint is missing . Dug the code and found we use these steps to register endpoint : 1. create Service and Endpoints in WSDeploymentDeployer. 2. set the address in EndpointAddressDeploymentAspect and modify the name in EndpointNameDeploymentAspect (for native stack) . If the transport is MDB jms , the jms: will be appended to name . 3. register these endpoints in EndpointRegistryDeploymentAspect. When the jms transport is enabled , we can see the endpoint address is http or https. Can we modify it to real correct jms address value ? I thought of some possible solutions and to start this discussion here : a. configure the jms address as the servlet parameter and set this jms address in WSDeploymentDeployer. b. parse the wsdl and get the address and endpoint name map , then attach it to deployment . Use this map to match the endpoint's address In EndpointAddressDeploymentAspect. It only works for the service contains a wsdl. How to do with java first service ? Is there any other solution here ? Which way is the better to go ? I am waiting for your thoughts and comments ... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261640#4261640 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261640

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by alessio.soldano＠jboss.com

I'd say start producing a minimal testcase showing how to use with JBossWS-CXF what CXF already provide as is, then we think about possible enhancements / improvements in terms of integration. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260443#4260443 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260443

14 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - jms transport support in jbossws-cxf

by jim.ma

So far the native uses MDB to enable the jms transport. Do we also need to provide such test case or example in cxf stack ? CXF already implemented a jmsTransport to directly send and receive soap message from JMS : <wsdl:service name="JMSGreeterService"> | <wsdl:port binding="tns:JMSGreeterPortBinding" name="GreeterPort"> | <jms:address | destinationStyle="topic" | jndiConnectionFactoryName="ConnectionFactory" | jndiDestinationName="dynamicTopics/test.cxf.jmstransport.topic" | > | | <jms:JMSNamingProperty name="java.naming.factory.initial" value="org.xxx.InitialContextFactory"/> | <jms:JMSNamingProperty name="java.naming.provider.url" value="tcp://localhost:9999"/> | </jms:address> | </wsdl:port> | </wsdl:service> We only provide this kind of jms transport support in CXF stack ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260346#4260346 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260346

14 years, 6 months

1
0
0 / 0

Re: [jbossws-dev] Setting databindings through annotations

by Alessio Soldano

OK Jim, so I'd say on server side you can use this @DataBinding annotation and forget about the servlet parameters stuff. If the user wants more control on the databinding, he's free to provide his own jbossws-cxf.xml file instead of leveraging the generated one. For using the annotation we need to move to Apache CXF 2.2.4, which btw is already scheduled, see. JBWS-2780. I'm doing that (the update) tomorrow if the artifacts are available on central. If you're blocked, in the mean time you can take a look at other issues you already have for 3.2.1 release. Cheers Alessio Daniel Kulp wrote: > Kind of already done. :-) > > On trunk and 2.2.4, we have a @DataBinding annotation that takes the Class of > the databinding. Doesn't really allow configuration though due to > limitations for annotations. :-( It does allow a "ref" attribute that > can point to a bean name in the spring config instead though. > > The other thing is the wsdl2java tool now outputs that annotations -db > xmlbeans and -db sdo. Thus, the generated code works correctly now without > config. > > Dan > > On Tue October 13 2009 4:31:21 am Alessio Soldano wrote: > >> Hi there, >> we're currently looking at ways for programmatically configuring the >> databinding (Aegis for instance) different from the default JAXB one >> (thus without setting it in the cxf.xml config file). >> Jim already took a look at this and we are thinking about contributing >> something for allowing the databinding to be specified using annotations >> (unless there's already something equivalent for doing this). >> What do you think about this? >> I'd see different approaches here, either using the already existing >> @Feature or adding new annotation. >> Cheers >> Alessio >> >> > > -- Alessio Soldano Web Service Lead, JBoss

14 years, 6 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-dev October 2009