[Design of JBoss Web Services] - JBWS-1260 - Unwrapping empty sequences
by darran.lofthouse@jboss.com
Hopefully the last scenario for this task :-)
According to the JAX-RPC 1.1 specificiation, the third rule for an operation to be unwrappable: -
anonymous wrote : such an element (a wrapper) must be of a complex type defined using the
| xsd:sequence compositor and containing only elements declarations.
I have one scenario with the following types defined in the WSDL: -
<element name='lookup'>
| <complexType>
| <sequence>
| </sequence>
| </complexType>
| </element>
|
| <element name='lookupResponse'>
| <complexType>
| <sequence>
| </sequence>
| </complexType>
| </element>
And on a second scenario I have the following types defined: -
<complexType name='Person'>
| <sequence>
| </sequence>
| </complexType>
|
| <complexType name='TelephoneNumber'>
| <sequence>
| </sequence>
| </complexType>
wscompile is generating the method in the SEI as: -
public org.jboss.test.ws.jbws1260.LookupResponse lookup() throws
| java.rmi.RemoteException;
and
public org.jboss.test.ws.jbws1260.TelephoneNumber lookup() throws
| java.rmi.RemoteException;
This apears to be handling the unwrapping of the return type differently to the unwrapping of the parameters (as discussed in a previous post).
My question is - If the JAX-RPC specification only mentions complex types that contain a sequence of elements does this mean this scenario does not qualify for unwrapping as there are no elements?
If this type can be unwrapped should the return type of the method be void?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995028#3995028
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995028
18 years, 1 month
WS test status
by Thomas Diesler
Folks,
All tests in jaxws, jws, saaj should pass with the current exclude file
I also managed to generate the special WS clients
http://jira.jboss.org/jira/browse/JBCTS-476
This will allow me to run sections webservice, webservice12
Target for next week is that jaxrpc, jaxws, jws, saaj, webservice,
webservice12 passes for the forward scenario.
The exclude file will contain a number of test failures with associated
jira issues that we can then distribute among the team.
From then on, QA should only see all tests passing and we work on
removing the excluded tests from the excludefile.
Test failures would show regression.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 1 month
RE: WS reverse tests
by Jason T. Greene
Ah, I see, that makes sense. I think #3 depends on when we need to
certify JBoss5. If we complete wsimport (wsdl -> java), then we can test
our tools, however, if this is not done by the time that we need to
certify, then we will have to look at bundling their tools. I think the
latter is most likely, and is what I have been telling everyone at the
CTS meeting, since we are looking at a full quarter to implement
wsimport.
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 14, 2006 11:59 AM
To: Jason T. Greene
Cc: Heiko Braun; JBossWS-DEV; JavaEE-TCK
Subject: Re: WS reverse tests
It makes a difference. With reverse tests generated, clients get
deployed to glassfish (not to jboss) for the forward scenario.
I propose
#1 first complete all forward tests without glassfish being involved
(i.e. jboss-jboss)
#2 generate the reverse tests using the RI tools. This will test
interop.
#3 when tools is ready, implement the wstools wrapper and regenerate the
reverse tests. This will test wstools.
To do #1 select sections jaxws, jws, saaj, webservices, webservices12
and set the "forward" keyword in the configuration.
Anil will take care of jaxr. I'll take care of jaxrpc.
cheers
-thomas
Jason T. Greene wrote:
Currently this uses the SUN tools, so there isn't much value in running
them right now. We have to rebundle the glassfish jars in order to get
certified on this. Last we discussed this, we agreed to wait until the
runtime tests pass.
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 14, 2006 3:59 AM
To: Jason T. Greene; Heiko Braun; JBossWS-DEV; JavaEE-TCK
Subject: WS reverse tests
FYI,
with the recent update to SAAJ-1.3 it was possible to generate the
reverse test clients
You need to run
<TS_HOME>/bin/tsant -Dbuild.vi=true clean build
in the jaxws and jws test src directories. On my box it took > 3h to
generate the tests.
Once the reverse tests are generated you MUST have glassfish running to
run any forward or reverse test.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 1 month
RE: WS reverse tests
by Jason T. Greene
Currently this uses the SUN tools, so there isn't much value in running
them right now. We have to rebundle the glassfish jars in order to get
certified on this. Last we discussed this, we agreed to wait until the
runtime tests pass.
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 14, 2006 3:59 AM
To: Jason T. Greene; Heiko Braun; JBossWS-DEV; JavaEE-TCK
Subject: WS reverse tests
FYI,
with the recent update to SAAJ-1.3 it was possible to generate the
reverse test clients
You need to run
<TS_HOME>/bin/tsant -Dbuild.vi=true clean build
in the jaxws and jws test src directories. On my box it took > 3h to
generate the tests.
Once the reverse tests are generated you MUST have glassfish running to
run any forward or reverse test.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 1 month
[Design of JBoss Web Services] - Re: Proposed JAX-WS Docs
by thomas.diesler@jboss.com
>From Axis
* Introduction
o What is SOAP?
o What is Axis?
o What's in this release?
o What's still to do?
* Installing Axis and Using this Guide
* Consuming Web Services with Axis
o Basics - Getting Started
o Naming Parameters
o Interoperating with "untyped" servers
* Publishing Web Services with Axis
o JWS (Java Web Service) Files - Instant Deployment
o Custom Deployment - Introducing WSDD
o Service Styles - RPC, Document, Wrapped, and Message
* XML <-> Java Data Mapping in Axis
o How your Java types map to SOAP/XML types
o Exceptions
o What Axis can send via SOAP with restricted Interoperability
o What Axis can not send via SOAP
o Encoding Your Beans - the BeanSerializer
o When Beans Are Not Enough - Custom Serialization
* Using WSDL with Axis
o ?WSDL: Obtaining WSDL for deployed services
o WSDL2Java: Building stubs, skeletons, and data types from WSDL
o Java2WSDL: Building WSDL from Java
* Published Axis Interfaces
* Newbie Tips: Finding Your Way Around
o Places to Look for Clues
o Classes to Know
* Appendix : Using the Axis TCP Monitor (tcpmon)
* Appendix: Using the SOAP Monitor
* Glossary
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993952#3993952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993952
18 years, 1 month