November 2009 - jbossws-dev - Jboss List Archives

[JBoss Web Services Development] - Re: Create new deployer to deploy java first jms transport w

by alessio.soldano＠jboss.com

I agree on having another deployer for jms endoints, as we said on IRC last week. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264987#4264987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264987

15 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Re: Create new deployer to deploy java first jms transport w

by richard.opalka＠jboss.com

"jim.ma" wrote : If this can be deployed without web.xml, it will be more quick and flexible.Can we create another deployer to do this job ? | IMHO this is not good idea :( Why complicate things? I don't see the problem web.xml have to be provided (just my opinion). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264986#4264986 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264986

15 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Create new deployer to deploy java first jms transport webse

by jim.ma

If we deploy a java first jms transport webservice in cxf stack (http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite/...), we also need to provide a web.xml to tell cxf stack, this is web service deployment and it needs CXFServletExt to load the jbossws-cxf.xml when it initializes. If this can be deployed without web.xml, it will be more quick and flexible.Can we create another deployer to do this job ? This deployer can load the cxf descriptor file (eg. cxf/jbossws-cxf.xml) in CXF to start jms trasnport . and resposible for started endpoints registration. It is also mainly for jave first web service in CXF stack . For the requirment to enable a service both with servlet transport and jms transport , and provide wsdl query via servlet transport , we can remain the current deployment approach. Do you see any problems here ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264960#4264960 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264960

15 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Re: New dev: Problem building stack-native

by jim.ma

We are look at these issues now : https://jira.jboss.org/jira/browse/JBWS-2769. You pasted error is the same as https://jira.jboss.org/jira/browse/JBWS-2818? Try to comment that profile to see if it helps . Jim View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264813#4264813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264813

15 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - New dev: Problem building stack-native

by karypid

Hi, I've just successfully built JBossWS-CXF trunk and now need to build JBossWS-Native trunk. With exactly the same environment (WinXP-32 system, Sun JDK 1.6.0_16, Maven 2.2.1) I get an error while building the SAAJ module of Native. I've configured by JBoss AS 5.1.0 location and running "ant deploy-jboss510" fails, saying something about not being able to execute the java compiler: | D:\cxf-dev\projects\jbossws-native-trunk>ant deploy-jboss510 | Buildfile: build.xml | | target-jboss510: | | os-init: | | mvn-settings: | [mkdir] Created dir: D:\cxf-dev\projects\jbossws-native-trunk\target | [exec] [INFO] Scanning for projects... | [exec] [INFO] Reactor build order: | [exec] [INFO] JBoss Web Services - Stack Native | [exec] [INFO] JBoss Web Services - Stack Native SAAJ | [exec] [INFO] JBoss Web Services - Stack Native JAX-RPC | [exec] [INFO] JBoss Web Services - Stack Native JAX-WS | [exec] [INFO] JBoss Web Services - Stack Native JAX-WS Ext | [exec] [INFO] JBoss Web Services - Native Server | [exec] [INFO] JBoss Web Services - Stack Native Client | [exec] [INFO] JBoss Web Services - Stack Native Management | [exec] [INFO] JBoss Web Services - Stack Native Resources | [exec] [INFO] Searching repository for plugin with prefix: 'help'. | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Building JBoss Web Services - Stack Native | [exec] [INFO] task-segment: [help:effective-settings] (aggregator-style) | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] [help:effective-settings {execution: default-cli}] | [exec] [INFO] Effective-settings written to: D:\cxf-dev\projects\jbossws-native-trunk\target\ef | fective-settings.xml | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] BUILD SUCCESSFUL | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Total time: 3 seconds | [exec] [INFO] Finished at: Tue Nov 10 14:21:43 EET 2009 | [exec] [INFO] Final Memory: 10M/18M | [exec] [INFO] ------------------------------------------------------------------------ | [echo] | [echo] jboss500.home=${profiles.profile.properties.jboss500.home} | [echo] jboss501.home=${profiles.profile.properties.jboss501.home} | [echo] jboss510.home=D:\cxf-dev\runtime\jboss-5.1.0.GA | [echo] jboss520.home=${profiles.profile.properties.jboss520.home} | [echo] jboss600.home=${profiles.profile.properties.jboss600.home} | | prepare: | | init: | [echo] java.version=1.6.0_16 | [echo] version.id=3.2.2-SNAPSHOT | [echo] integration.target=jboss510 | | undeploy-jboss510: | [delete] Deleting directory D:\cxf-dev\runtime\jboss-5.1.0.GA\server\default\deploy\jbossws.sar | [delete] Deleting directory D:\cxf-dev\runtime\jboss-5.1.0.GA\server\default\deploy\juddi-service | .sar | | prepare-deploy: | [echo] | [echo] mvn.bat package assembly:directory | [echo] | [exec] [INFO] Scanning for projects... | [exec] [INFO] Reactor build order: | [exec] [INFO] JBoss Web Services - Stack Native | [exec] [INFO] JBoss Web Services - Stack Native SAAJ | [exec] [INFO] JBoss Web Services - Stack Native JAX-RPC | [exec] [INFO] JBoss Web Services - Stack Native JAX-WS | [exec] [INFO] JBoss Web Services - Stack Native JAX-WS Ext | [exec] [INFO] JBoss Web Services - Native Server | [exec] [INFO] JBoss Web Services - Stack Native Client | [exec] [INFO] JBoss Web Services - Stack Native Management | [exec] [INFO] JBoss Web Services - Stack Native Resources | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Building JBoss Web Services - Stack Native | [exec] [INFO] task-segment: [package] | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] [antrun:run {execution: validate-jboss-home}] | [exec] [INFO] Executing tasks | [exec] [echo] | [exec] [echo] profile=${jbossws.integration.target} | [exec] [echo] jboss.home=${jboss.home} | [exec] [echo] | [exec] [INFO] Executed tasks | [exec] [INFO] [site:attach-descriptor {execution: default-attach-descriptor}] | [exec] [INFO] Preparing source:jar | [exec] [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. | [exec] [INFO] [antrun:run {execution: validate-jboss-home}] | [exec] [INFO] Executing tasks | [exec] [echo] | [exec] [echo] profile=${jbossws.integration.target} | [exec] [echo] jboss.home=${jboss.home} | [exec] [echo] | [exec] [INFO] Executed tasks | [exec] [INFO] [source:jar {execution: attach-sources}] | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Building JBoss Web Services - Stack Native SAAJ | [exec] [INFO] task-segment: [package] | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] [antrun:run {execution: validate-jboss-home}] | [exec] [INFO] Executing tasks | [exec] [echo] | [exec] [echo] profile=${jbossws.integration.target} | [exec] [echo] jboss.home=${jboss.home} | [exec] [echo] | [exec] [INFO] Executed tasks | [exec] [INFO] [resources:resources {execution: default-resources}] | [exec] [WARNING] Using platform encoding (Cp1253 actually) to copy filtered resources, i.e. bui | ld is platform dependent! | [exec] [INFO] Copying 3 resources | [exec] [INFO] [compiler:compile {execution: default-compile}] | [exec] [INFO] Compiling 28 source files to D:\cxf-dev\projects\jbossws-native-trunk\modules\saa | j\target\classes | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [ERROR] BUILD FAILURE | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Compilation failure | [exec] Failure executing javac, but could not parse the error: | [exec] The system cannot find the path specified. | [exec] | [exec] | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] For more information, run Maven with the -e switch | [exec] [INFO] ------------------------------------------------------------------------ | [exec] [INFO] Total time: 3 seconds | [exec] [INFO] Finished at: Tue Nov 10 14:21:48 EET 2009 | [exec] [INFO] Final Memory: 16M/29M | [exec] [INFO] ------------------------------------------------------------------------ | | BUILD FAILED View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264804#4264804 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264804

15 years, 2 months

1
0
0 / 0

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

by alessio.soldano＠jboss.com

"jim.ma" wrote : "alessio.soldano(a)jboss.com" wrote : | | What I'm thinking about is that you can probably define a new JMSTransportFactory that extends the original one and also uses the information regarding the jms stuff to update the endpoint address in the registry. That information is basically the JMSConfiguration that is currently computed in the jms transport factory. | Now the jms endpoint address comes from the jbossws-cxf.xml now, and CXF will process it internally and set in the JMSCongfiguration. The problem is we want to update/correct the jms endpoint address before servlet initialize (load bus). Because we can not rely on user specifies the load-on-startup to true value . So we decide to parse the jbossws-cxf.xml and extract the jms address in JMSEndpointAddressDA before the stage of servlet really deployed. So IMHO, I do do not think extending the JMSTransportFactory can help this . Correct me if I am wrong, Alessio. | You're right in the usecase where the jbossws-cxf.xml is provided and has the jms address. I'm thinking about the other use case, perhaps my suggestion could be useful for a late setup of the address in that case. But let's start with the first case, then we'll see what we can do. "jim.ma" wrote : | "alessio.soldano(a)jboss.com" wrote : | | Besides this, I was actually thinking about something else. Another interesting think to do would be to consider the jms endpoints too in the endpoint metrics that we provide (the count of messages, etc.). This is something we can deal with later, but keep an eye for possible integration points, idea, etc. | | | AFAIK, CXF offers some JMX bean to count the soap request message and | manage the endpoint and transport destinations : http://cwiki.apache.org/CXF20DOC/jmx-management.html . I also did some work to register these beans in our jboss jmx server : https://jira.jboss.org/jira/browse/JBWS-2805. We can look at how to consolidate it with our management work. Sure, this is what we talked about on IRC yesterday, I agree. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264053#4264053 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264053

15 years, 2 months

1
0
0 / 0

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

by jim.ma

"alessio.soldano(a)jboss.com" wrote : | What I'm thinking about is that you can probably define a new JMSTransportFactory that extends the original one and also uses the information regarding the jms stuff to update the endpoint address in the registry. That information is basically the JMSConfiguration that is currently computed in the jms transport factory. Now the jms endpoint address comes from the jbossws-cxf.xml now, and CXF will process it internally and set in the JMSCongfiguration. The problem is we want to update/correct the jms endpoint address before servlet initialize (load bus). Because we can not rely on user specifies the load-on-startup to true value . So we decide to parse the jbossws-cxf.xml and extract the jms address in JMSEndpointAddressDA before the stage of servlet really deployed. So IMHO, I do do not think extending the JMSTransportFactory can help this . Correct me if I am wrong, Alessio. "alessio.soldano(a)jboss.com" wrote : | Besides this, I was actually thinking about something else. Another interesting think to do would be to consider the jms endpoints too in the endpoint metrics that we provide (the count of messages, etc.). This is something we can deal with later, but keep an eye for possible integration points, idea, etc. | AFAIK, CXF offers some JMX bean to count the soap request message and manage the endpoint and transport destinations : http://cwiki.apache.org/CXF20DOC/jmx-management.html . I also did some work to register these beans in our jboss jmx server : https://jira.jboss.org/jira/browse/JBWS-2805. We can look at how to consolidate it with our management work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264037#4264037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264037

15 years, 2 months

1
0
0 / 0

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

by alessio.soldano＠jboss.com

"jim.ma" wrote : | "alessio.soldano(a)jboss.com" wrote : | | - consider taking a look at the CXF JMSTransportFactory, perhaps there's an easy hook for getting/setting the address. We currently overwrite the SoapTransportFactory in the bus in CXFServletExt.loadBus(..) in order to implement our own soap address rewriting rules for http endpoints. Perhaps a similar approach might be useful here (extending the jms transport factory, etc.) for the jms case. | Do you mean we can specify the jms address in servlet initial parameter and set it in the JMSDestination when initialize servlet ? | No, I don't think allowing the jms address to be provided in servlet initial parameters is useful, considering the same can already be achieved using the other descriptor (jbossws-cxf.xml). What I'm thinking about is that you can probably define a new JMSTransportFactory that extends the original one and also uses the information regarding the jms stuff to update the endpoint address in the registry. That information is basically the JMSConfiguration that is currently computed in the jms transport factory. Besides this, I was actually thinking about something else. Another interesting think to do would be to consider the jms endpoints too in the endpoint metrics that we provide (the count of messages, etc.). This is something we can deal with later, but keep an eye for possible integration points, idea, etc. "jim.ma" wrote : | "alessio.soldano(a)jboss.com" wrote : | | - we might think about something (an annotation?) to mark a jms endpoint when doing java-first, assuming there's not an equivalent way in CXF yet. That could be looked for in the DA to properly write the jbossws-cxf that is generated on the fly when not provided by the user. | | Annotation is another way to specify jms transport and address. IMHO, It's flexible to define the jms configuration in web.xml. You do not need to compile the code when you change the queue name . | Yes, I see what you mean, let's stick with the descriptor for now (the jbossws-cxf.xml) "jim.ma" wrote : | "alessio.soldano(a)jboss.com" wrote : | | - is the CXF JMSFeature (http://cxf.apache.org/docs/using-the-jmsconfigfeature.html) configuration of any use to us? | IMO, it is another format to attach the jms configuraiton to the client and endpoint. If user provides the jbossws-cxf.xml like this format , we do not support to parse ,extract the jms address information and register the endpoint. We will just support one format like the jbossws-cxf.xml in current jms transport sample. OK View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263872#4263872 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263872

15 years, 2 months

1
0
0 / 0

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

by jim.ma

Thanks for your input , Alessio. "alessio.soldano(a)jboss.com" wrote : | - consider taking a look at the CXF JMSTransportFactory, perhaps there's an easy hook for getting/setting the address. We currently overwrite the SoapTransportFactory in the bus in CXFServletExt.loadBus(..) in order to implement our own soap address rewriting rules for http endpoints. Perhaps a similar approach might be useful here (extending the jms transport factory, etc.) for the jms case. Do you mean we can specify the jms address in servlet initial parameter and set it in the JMSDestination when initialize servlet ? <servlet> | <servlet-name>MyServletName</servlet-name> | <servlet-class>com.mycompany.MyServlet</servlet-class> | <init-param> | <param-name>jmsJndiRequestQueue</param-name> | <param-value>queue/RequestQueue</param-value> | </init-param> | </servlet> "alessio.soldano(a)jboss.com" wrote : | - we might think about something (an annotation?) to mark a jms endpoint when doing java-first, assuming there's not an equivalent way in CXF yet. That could be looked for in the DA to properly write the jbossws-cxf that is generated on the fly when not provided by the user. Annotation is another way to specify jms transport and address. IMHO, It's flexible to define the jms configuration in web.xml. You do not need to compile the code when you change the queue name . "alessio.soldano(a)jboss.com" wrote : | - is the CXF JMSFeature (http://cxf.apache.org/docs/using-the-jmsconfigfeature.html) configuration of any use to us? IMO, it is another format to attach the jms configuraiton to the client and endpoint. If user provides the jbossws-cxf.xml like this format , we do not support to parse ,extract the jms address information and register the endpoint. We will just support one format like the jbossws-cxf.xml in current jms transport sample. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263846#4263846 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263846

15 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Access SOAP message content

by oechevarria

Hello, I have an implementation of a web service using the @WebServiceProvider annotation. This web service receives a SOAP message (via the public SOAPMessage invoke(SOAPMessage soapMessage) API). I am trying to get the contents of the message using the standard API calls such as SOAPPart soapPart = message.getSOAPPart(); Source source = soapPart.getContent(); However getSOAPPart() gives me what appears to be a partial message, i.e the contents of the body are empty even though the envelope and the header are good. Further, if I 'print' the message using an output stream I am able to see the entire message contents. Can anyone provide any clues as to what may be happening? I am using JBoss AS 5.1.0 and JBoss WS native 3.2.0 on Windows. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263807#4263807 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263807

15 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev November 2009