> explained. A special chapter on message styles clarifies the
differences
> between RPC/Encoded, RPC/Literal, Doc/Literal and Wrapped.
I think the thing a new person gets confused about the most is all this
doc literal, rpc encoded, messages style, document style, wrapped style,
rpc style talk.
I have not yet read the JAX-RPC 2.0 spec but if it does mandate JAXB
will a future version of axis that implements JAX-RPC 2.0 allow the user
to plugin any JAXB implementation he wants or will Axis ship with a JAXB
implementation that will have to be used?
> -Original Message-
> From: Dava
Do you think the JAXB spec is mature
enough?
What implementations of JAXB do you think are
useful?
-Original Message-
From: Wei Hsu
[mailto:[EMAIL PROTECTED]]
Sent: Monday, March 22, 2004 2:41 PM
To: [EMAIL PROTECTED]
Subject: Integrating JAXB with
Axis
Hi all,
Go
Software Developer
> insightamerica
> "Those who do not understand Unix are condemned to reinvent it,
poorly."
> --Henry Spencer
>
> -Original Message-
> From: Keith Bohnenberger [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 07, 2004 10:02 AM
> To: [EMAIL
You can try getting the java system property user.dir
Why do you need the path? Can you get away with using
getResourceAsStream(...) instead?
> -Original Message-
> From: Sean Leblanc [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 07, 2004 11:40 AM
> To: '[EMAIL PROTECTED]'
> Subje
Are there any plans to make the "binding" capability in Axis pluggable
so you could choose to use whatever binding tool you wanted in wsdl2java
and in the soap engine at runtime?
It seems that if the JAXB spec ever catches up and is mandated by the
JAX-RPC spec this type of architecture would be ne
astor serialization
Did you make the change to the CastorSerializer class as noted in this
link:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg15150.html
I had issues until I made this change.
Craig
-Original Message-
From: Keith Bohnenberger [mailto:[EMAIL PROTECTED]
Sent: Tu
PROTECTED]
Subject: RE: 1.2 alpha and castor serialization
Did you make the change to the CastorSerializer class as noted in this
link:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg15150.html
I had issues until I made this change.
Craig
-Original Message-
From: Keith Bohnenberger
I am trying to get a modified version of the stock example to work with
built in castor serialization.
I am using the alpha1.2 release from
http://www.apache.org/dist/ws/axis/1_2alpha
However, since it did not include the ...encoding.ser.castor.* classes I
built a new axis.jar from the CVS reposit
The 1.2 alpha release does not seem to have the
org.apache.axis.encoding.ser.castor.* classes in it.
Am I missing something or is that intentional?
I downloaded the 1.2 alpha release from
http://www.apache.org/dist/ws/axis/1_2alpha
Thanks
keith
-Original Message-
From: Hainer Neil [mail
was both JAX-RPC 1.0 and SAAJ 1.1
compliant".
Thanks,
dims
--- Keith Bohnenberger <[EMAIL PROTECTED]> wrote:
> Is Axis 1.2 alpha Jax-RPC 1.1 and SAAJ 1.2 compliant?
>
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, Dec
Is Axis 1.2 alpha Jax-RPC 1.1 and SAAJ 1.2 compliant?
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 10:50 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: 1.2 Alpha
Hi all!
There is an alpha release of Axis 1.2 at
http://www.apache.
Ahhh BP as in Basic Profile.
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 5:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Why choose Axis?
[EMAIL PROTECTED] wrote:
>...
>
>And as for Sun's JWSDK, again, need more info. My understandin
What is WS-I BP and BP-compiant?
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 5:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Why choose Axis?
[EMAIL PROTECTED] wrote:
>...
>
>And as for Sun's JWSDK, again, need more info. My understa
The article that you mention uses the axis "wrapped" programming style
with the Axis CVS version which supports castor serialization. They are
using document/literal web services. Keep in mind that "message",
"document", and "wrapped" are program styles not communication styles or
WSLD styles. A
One of the reasons standards exist is to avoid vendor lock-in.
It is a good architecture goal to avoid vendor lock-in and write code to
the specs/standard apis.
Lets say you didnt know about axis and you implemented a bunch of web
services in Java using some other SAAJ/JAX-RPC implementation. A f
poses.
The
QName doesn't need to be the same as the operation name. It's simply a
matter of mapping the Qname to a method, which you can do in the WSDD.
Anne
At 12:49 AM 11/14/2003, you wrote:
>Keith Bohnenberger wrote:
>
>>It seems to me that the SOAP spec needs a SOAPOpe
Mike,
Can you cut and paste the part of the WS-I profile that recommends
RPC/literal? I missed that when I read it.
Its interesting that the JAX-RPC spec says that an implementation may
support RPC/literal but doesnt have to. That right there would be
enough for me to never implement RPC/litera
Mike,
I agree with all of your points.
I dont understand web services well enough yet so this question may be a
lame one.
The SOAPAction is in the WSDL. How does that translate to the actual
SOAP message that is being sent over the wire? My uneducated guess is
that it doesn't. My guess is that
With document/literal web services you need to define your schema in
such a way that the "wrapper" element or root element will lead you to
the business function. So you are not just defining the data that needs
to be sent but also a wrapper element that suggests the operation to be
performed. Rea
One thing that I forget to mention which I think is very important. Axis
implements the SAAJ and JAX-RPC spec (go to sun to find these). While
you dont have to be to aware of these to use Axis I think it is
important to know what Java specs are out there for implementing Java
web services on the s
I am using Axis 1.1 (not the CVS version
with castor serialization) and doing the castor serialization on the server
side by hand.
Given the following wsdl with an xsd:choice group (this is just an academic example to show the
problem)
...
:schema ...">
:complexType name=
Gene,
Good questions. Let me add a few more for you.
Are you going to send/receive RPC/Encoded messages or Document/Literal
messages?
If you develop RPC/Encoded messages (which many people including me do
not recommend) then you will probably use axis' "rpc" programming
style(axis calls these
23 matches
Mail list logo
