February 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by heiko.braun＠jboss.com

Jibril GUEYE wrote: I'm trying the build WS 2.1.0 for METRO from svn using revision 5561 (which was the lastest stable build) but i can't succeed. Here is ant's output from my console: checkout: -install.adapter: [copy] Copying 1 file to /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/cvs/wsit/wsit [copy] Copying /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/ant-import/metro-build-adapter.xml to /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/cvs/wsit/wsit/metro-build-adapter.xml clean.metro: [exec] Buildfile: build.xml does not exist! [exec] Build failed BUILD FAILED /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/ant-import/build-metro.xml:70: The following error occurred while executing this line: /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/ant-import/build-metro.xml:23: exec returned: 1 can you help me out ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126910#4126910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126910

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

Second identified problem is HA WS-RM in combination with WS-Security. HA WS-RM must reside on top of transport layer (this results from WS-RM specification). Current WS-Security and WS-RM un/marshalling processings reside in JAX-RPC/JAX-WS handlers. In order to support HA WS-RM plus WS-Security joint combinations (as required by e.g. Microsoft Web Services Interop Plug Fest Scenarios) it is necessary to move both WS-RM and WS-Security one layer lower in the processing chain i.e. implement it in transport un/marshallers because of the following two requirements: WS-Security processing must be the last/first thing in client and endpoint outgoing/incoming processing chain. HA WS-RM must reside on top of transport layer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126251#4126251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126251

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS brings Metro/CXF but in what version?

by richard.opalka＠jboss.com

"heiko.braun(a)jboss.com" wrote : Does this make sense to you guys? | Yes, it makes perfect sence to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126248#4126248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126248

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS brings Metro/CXF but in what version?

by heiko.braun＠jboss.com

I would just regard the prefix as branding. As thomas said, it's a new era. Therefore I would opt for jbossws-wsf-XYZ. WSF (web service framework) is something we included in the brand when we started the SPI. It's reflected in the package names as well. | * jbossws-wsf-native-2.0.3 | * jbossws-wsf-metro-1.0.0 | * jbossws-wsf-cxf-1.0.0 | Changes to SPI, framework, etc would trigger new releases of each stack anyway, right? I am looking at this from a users point of view. The prefix versioning just confuses people. "Did they release a new metro version?" This is what I would ask myself. Regardless if that was causing changes to the SPI or the framework. If any fix requires changes to the SPI, all stacks need to update anyway. So I'd say we release by a rule of thumb: - Any change to the SPI, framework requires an update to each stack - At least each stack needs to be run through QA - QA means a tagged framework version and thus an update to the stack (version.properties) In this case I don't see the need for a confusing prefix versioning like 'jbossws-3.0-XYZ'. Does this make sense to you guys? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126246#4126246 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126246

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

First identified problem is HA itself. Imagine the following usecase: Client sends WS-RM message to a webservice endpoint that is not available. The default AS behaviour in such case is 404 (resource N/A). To overcome this problem here are the potential solutions that comes into my mind: 1) Deploy a special servlet that would do the following steps: * will match all http(s) requests that would result in 404 on running AS instance (is it doable?) * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) 2) Deploy a special servlet that would do the following steps: * will reside on /wsrm/* web context * all "GET WSDL" http(s) requests would return a modified WSDL document to reference the endpoint using /wsrm prefix for web context. (Of course only if such WSDL exists - otherwise it would return 404.) Example: | | client request GET .../wsrm/ctx/endpoint?wsdl | special servlet request GET .../ctx/endpoint?wsdl | RETURN modified WSDL or 404 (if above WSDL isn't available) | * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) For both above approaches it is supposed to use ServletContext.getContext() method to gain access to the context for various parts of the server, and as needed obtain RequestDispatcher objects from the context. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126210#4126210 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126210

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : Hi Richard, | | while working with the RM implementation I was wondering about the Quality of Service (QoS) aspect of WS-RM. In my understanding the RM Sender/Receiver must be high available (HA) components such that the Client can (always) communicate with the RM Sender and likewise the RM Sender can always communicate with the RM Receiver. | | | | Client <--> RM Sender <-------> RM Receiver <--> Endpoint | | QoS QoS | | | | Using your implementation, would it (eventually) be possible to deploy the RM Sender/Receiver as separate HA components (i.e. on dedicated boxes)? I created a bug http://jira.jboss.org/jira/browse/JBWS-1976 and investigation results + identified issues will be accumulated in the following jbossws-dev forum topic: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4126102#4126102 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126106#4126106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126106

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

This dev forum topic will accumulate investigation results of research on RM Sender/Receiver as High Available (HA) Components It relates to bug http://jira.jboss.org/jira/browse/JBWS-1976 and was initiated by the following discussion http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126278 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126102#4126102 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126102

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS productization

by nithyaraj

Is any chance for integarate jboss webservice in minimal package using jboss 4.2GA Any one can reply with steps? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125826#4125826 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125826

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Minimal with webservice integration

by nithyaraj

Hi, I have some clarification in jboss ,is there any chance to integrate jboss minimal deployment with web service integration. is there any chance for integrate? if it possible give me the config steps with webservice,swebdeployer service alone... Thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125499#4125499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125499

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [Productivity] Level 2 - Development

by alessio.soldano＠jboss.com

"alessio.soldano(a)jboss.com" wrote : | Speaking of samples, we think to provide meaningful advanced samples. These might cover the testcases I spoke about in the productivity introduction http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095128#4094685, supporting tutorials in the documentation on advanced topics like security, attachments, addressing, etc. Just to keep this thread online, I'm working on the advanced samples. Up to know there're 2 scenarios I'll soon describe in the wiki: - the first one is about ws technologies related to attachments and security+authentication: this means MTOM/XOP, SWA, WS-Security, use of HTTPS, BASIC authentication. Different implementations are showed and the advantages and disadvantages coming from them will be discussed in the documentation - the second one is about technologies providing means of performing asynchronous ws invocations: this means the JAX-WS API (using Future<?>, Response<?> ...), WS-Addressing, JMS endpoints (still need to implement this in the sample). As for the previous scenario, several implementation are provided and will be discussed in the documentation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125409#4125409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125409

16 years, 3 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 February 2008