beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryoush Mehrtash" <dmehr...@bea.com>
Subject XMLBeans in WSM
Date Wed, 08 Jun 2005 22:48:17 GMT
> - does anyone know the status of XMLBean type handling in WSM?

 

This is an easy one!  It works.  But needs more testing, I am
particularly concern about case when we are working with documents from
different namespaces and schema files..

 

Our WSM and Service Control samples demonstrate it also.

 

FYI:  WSM and Service Control both support:

 

XMLBean types

Axis generated Types

POJOs. 

POJOs that either inherit from XMLBeans or Axis Generated Types

POJOs that have XMLBean or Axis generated type attributes.

 

One of the key benefits of the WSM is that (unlike Axis) it doesn't need
any special application code, or external configuration file  to
register any of the above types.  All the magic happens when the JWS is
deployed.

 

For service control the use of POJOs are less interesting than in WSM,
as the normal use case of the service control is to generate the JCX and
types based on WSDL.   Our recommendation is that for any literal (RPC
or Document) web services XMLBean types be generated.  But for
RPC-Encoded we only work with Axis types.  

 

If you are interested in XMLBeans you should take a serious look at our
"from WSDL use case" (shown in wsm-addressbook-fromWSDL sample) and the
Service control generation (shown in controls-webservices-blank).    I
think if you mix in XMLQuery capability to the mix you have the key
technologies to do a complete document based SOA.

 

There has also been confusion over .wsdl and .xsd files with respect to
XMLBean.  XMLBean  is smart enough to generate the types from the WSDL
schema. In cases where we generate source code (e.g. from WSDL use case
in JSR 181) our build commands can generate types from  *.xsd or *.wsdl
files.

 

Just in case you are not familiar with Axis.... Axis can generate types
(just like XMLBeans) from a WSDL.  These classes which I refered to as
"Axis generated types"  use Axis serialization and have special
signature methods that the WSM/ServiceControl use to detect them.  

 

Let me know if you need more on this.

 

Daryoush


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message