wsdl, I can just manually edit the wsdl and change
the property to nillable=”false” and then run wsdl2java to generate the java
stub code and this will require that the element be sent assuming it is fixed
in axis.
From:
Sheptunov, Bogdan [mailto:[EMAIL PROTECTED
It is
supposed to be implemented via nillable="false" in WSDL, but I don't think
it is working right in 1.2RC1.
-Original Message-From: Jairam, Roopnaraine
[mailto:[EMAIL PROTECTED]Sent: Tuesday, December 14, 2004
9:05 AMTo: [EMAIL PROTECTED]Subject: RE: data
validation
Axis uses log4j for logging. In your log4j configuration file, set level to
higher than DEBUG for org.apache.axis classes. Here's how I do it in my
log4j.xml (syntax will be different if you are using a plain text version of
your config):
If you dont have a log4j co
TED]
> Sent: Tuesday, November 30, 2004 11:40 AM
> To: [EMAIL PROTECTED]
> Subject: RE: hiding a property from Axis serializer?
>
>
> Try using the bean info class to define what properties exist
> for the bean.
> Axis seems to obey this Java Bean rule.
>
> -----Origin
Hello,
I am trying to determine what the value of (wsdl)soap:address attribute should
be, and to what extent that value is supposed to reflect the real URL at which
the corresponding service is avaliable.
In a WSDL, the following sample section describes a service itself:
Yes I saw that, thank you Adrian. I understand that I should be able to
specifying which properties I want serialized by writing a custom serializer.
However, I do not wish to do that. I do not see any "special circumstances" in
what I am trying to do that Axis should not be able to handle.
As
> A "filter all those properties" approach is to create a
> interface for
> each of those beans you would like to serialize, but just including
> getters and setters for those properties you really want to be
> serialized; then let your bean implement that interface
> (already does!)
> and
oving the public modifier, might do the trick. If Axis made use of a BeanInfo class, you might be able to
hide properties that way, but I think Axis just assumes the standard JavaBean
conventions, without BeanInfo modification. Otherwise, you'd probably have to write your own serializ
Hello,
Axis serializer by default picks up everything that looks like a JavaBean
property, and puts it into response. This leads to an undesirable side effect:
some of the class internals that have bean-like access, become exposed to the
outside and end up being automatically included into the
Afaik, there's no versioning spec as of yet.
Try this article as a jump start:
http://www-128.ibm.com/developerworks/webservices/library/ws-version/
> -Original Message-
> From: Luca Manganelli [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 25, 2004 7:59 AM
> To: [EMAIL PROTECTED]
> S
Hello,
I was following the Axis installation instructions document that came with 1.2RC1, and
noticed there's an inaccuracy there that might confuse some people.
http://ws.apache.org/axis/contact.html says to post the comments about documentation
in this list, so here goes. I apologize if this
11 matches
Mail list logo
