December 2006 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: jbossws deployer on JBoss AS 5

by thejavafreak

"jason.greene(a)jboss.com" wrote : As of last week its split into two parts a sar and a deployer. Why not join both of it into a .deployer and put it under deployers/ directory? Is there any consideration for not achieving this? With the microcontainer this would be able to be done, wouldn't it? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993683#3993683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993683

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by jason.greene＠jboss.com

Agreed View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993649#3993649 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993649

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by darran.lofthouse＠jboss.com

We can use the holders for standard types but I think it will be easier to get full support for holders in a single task without adding it to this task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993648#3993648 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993648

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by darran.lofthouse＠jboss.com

To get this task finished I will probably fall back to bare style. At the point of this Jira issue (and all the other issues being raised) we have no support for generating holders. I will have a look at what you have so far for holders and will create a new task to add support for unwrapping using holders if needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993647#3993647 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993647

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by jason.greene＠jboss.com

The partial wrapping wscompile does in this situation is wrong. We have two options, either generate holders, or fallback to bare style. The former would be dependent on the code changes I am currently merging into the 1.0 branch, the latter would save time. So I leave it up to you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993645#3993645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993645

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - What when we cannot unwrap the message parts

by jason.greene＠jboss.com

Sure, we probably should print a warning message though. You can do this by using log.warning, the wstools.sh and bat uses a log4j config that echos to the screen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993644#3993644 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993644

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 - What when we cannot unwrap the message parts?

by darran.lofthouse＠jboss.com

If a user has specified the parameter-style as 'wrapped' but the elements can not be unwrapped because the requirements of the spec have not been met how should we handle this situation? For JAX-WS the spec says for operations that fail the requirements they should be mapped using non-wrapped style. The JAX-RPC specification does not go into this level of detail. I have an implementation that can fall back to non-wrapped style if we are unable to unwrap the parts - do we want to do it this way so users can just specify wrapped and we will unwrap where we can or do we want to reject their WSDL if we can not unwrap everything? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993643#3993643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993643

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 - Sequence containing 2 elements

by darran.lofthouse＠jboss.com

Taking the following two elements as the input and ouput parameters: - <element name='lookup'> | <complexType> | <sequence> | <element name='firstName' nillable='true' type='string'/> | <element name='surname' nillable='true' type='string'/> | </sequence> | </complexType> | </element> | | <element name='lookupResponse'> | <complexType> | <sequence> | <element name='areaCode' nillable='true' type='string'/> | <element name='number' nillable='true' type='string'/> | </sequence> | </complexType> | </element> wscompile is generating the SEI method as: - public org.jboss.test.ws.jbws1260.LookupResponse lookup(java.lang.String firstName, java.lang.String surname) throws java.rmi.RemoteException; So the input element is being unwrapped as it can be converted to seperate parameters, however the return type can not be unwrapped so it is not. The JAX-RPC 1.1 specification doesn't seem to say how this should be handled. Previously we were dropping the second element in the return type and would just return a String. Tha JAX-WS spec seems to clarify this by mapping the wrapper children as a parameter using a holder type. Which approach should we be taking, especially as we don't currently generate holders? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993641#3993641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993641

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Unwrapping and complex types with attributes

by jason.greene＠jboss.com

wscompile is incorrect, and it is actually wrong in many areas like this. A complex type should only be unwrapped if there are no attributes. The reason is lack of order which is essential to determining a correct method signature. On this topic, we have a bug where array types are unwrapped if there are attributes. http://jira.jboss.com/jira/browse/JBWS-1189 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993637#3993637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993637

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Unwrapping and complex types with attributes

by darran.lofthouse＠jboss.com

Forget that, the paragraph refers to anyAttribute not attribute. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993636#3993636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993636

18 years, 1 month

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 December 2006