quot;Michael Schuerig" <[EMAIL PROTECTED]>
wrote on 23/11/2004 09:18:32:
> On Tuesday 23 November 2004 09:27, [EMAIL PROTECTED] wrote:
> > I don't think that the BeanSerializer, or any Axis serializer,
can be
> > used on its own. It works via callbacks from Axis, in a
On Tuesday 23 November 2004 09:27, [EMAIL PROTECTED] wrote:
> I don't think that the BeanSerializer, or any Axis serializer, can be
> used on its own. It works via callbacks from Axis, in a particular
> serialization context. I don't think it has an methods that can
> simply
I don't think that the BeanSerializer, or
any Axis serializer, can be used on its own. It works via callbacks from
Axis, in a particular serialization context. I don't think it has an methods
that can simply serialize an object to an XML string, or an XML document.
Tony
-Origin
Title: BeanSerializer
If you
just want to serialise java objects to xml, you could look at
java.beans.XMLEncoder.
However, if you want to see how axis does it this won't
help.
-Original Message-From: Levy, Avi
[mailto:[EMAIL PROTECTED]Sent: Tuesday, 23 November 2004
Title: BeanSerializer
Hi,
I'm trying to use BeanSerializer (from org.apache.axis.encoding.ser) to manualy serialize my Java object into raw XML. However, I don't really understand the javadoc of the serialize method in the class. Anyone knows how to use that class to serialize
( (GenderType)deserialised
);
System.err.println( "Gender is: "
+ g );
}
}
-----
Regards,
- kiru
Laurent CORNELIS <[EMAIL PROTECTED]>
10/18/2004 06:37 AM
Please respond to
[EMAIL PROTECTED]
Hi,
Can someone tell me
how to use BeanSerializer / Deserializer out of the context of a message ? (ie
to encode an object to XML and to parse XML for an object).
For the
serialization I do :
---
MyObject obj = new
Hi,
I have generated my
WebService and bean classes with WSDL2Java. It works
perfectly.
Now, I want to be
able to store some of my beans into an XMLDB, so I need to serialize them in
XML. As my beans already contains a TypeDesc generated by Axis, I want to use
the Axis BeanSerializer
Hi -
I'm trying to test out using XMLBeans with Axis am running into some
problems with the BeanSerializer. I'm trying to create a simple
client application.
It partially works but some of the objects/interfaces that are
generated by the xmlbeans compiler use inheritance and when
e: Mon, 6 Sep 2004 09:42:44 +0200
Subject: Re: BeanSerializer
To: [EMAIL PROTECTED]
hi Mahen,
thanks for your comment... one more question... what about if the
"sub-bean" is an abstract bean-class or the root
of a inheritance-hierarchie? Is this a problem or transparent for the
devep
hen Perera <[EMAIL PROTECTED]>
06.09.2004 08:21
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: BeanSerializer
Hi Sandro,
if the sub beans are also specified using the tag,
then
there should be no problem. No need to use Custom
Serialization
+0200
Subject: BeanSerializer
To: [EMAIL PROTECTED]
Hi all,
Does the beanserializer / deserializer also work if the bean-class has
its "sub-beans"?
We have specified the bean-class unsing the tag in the
wsdd... but now
we get a saxexception for the next "sub-bean"...
Is it
Hi all,
Does the beanserializer / deserializer
also work if the bean-class has its "sub-beans"?
We have specified the bean-class unsing
the tag in the wsdd... but now
we get a saxexception for the next "sub-bean"...
Is it better in this case to use customized
serialize
quot; soapenc:arrayType="xsd:anyType[2]"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
>
>
>
>
> the wsdl contains this element:
>
>
> -Oorspronkelijk bericht-
> Van: Brent Johnson [mailto:[EMAIL PROTECTED]
> Verzonden: maa
2 augustus 2004 21:35
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Newbie: Sending/Receiving Beans with BeanSerializer
Ahh.. so just return the bean that I want.. and I'm guessing I should
use call.setReturnClass(MyBean.class) instead of setReturnType?
Also.. I'm changing my beans to not use col
working correctly.
>
> Thanks for the help,
>
> - Brent
>
>
>
> - Original Message -----
> From: Callahan, Paul <[EMAIL PROTECTED]>
> Date: Mon, 2 Aug 2004 14:07:11 -0400
> Subject: RE: Newbie: Sending/Receiving Beans with BeanSerializer
> To: "[EMAI
tly.
Thanks for the help,
- Brent
- Original Message -
From: Callahan, Paul <[EMAIL PROTECTED]>
Date: Mon, 2 Aug 2004 14:07:11 -0400
Subject: RE: Newbie: Sending/Receiving Beans with BeanSerializer
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Just make the return typ
Title: RE: Newbie: Sending/Receiving Beans with BeanSerializer
Just make the return type of your method the class of the bean you want to return... Axis will serialize it on return, unless you are using collections or complex types.
-pc
-Original Message-
From: Brent Johnson
I want to be able to pass a bean (lets say "Item") to my WebService
and have a bean returned (in this case another "Item" with different
values).
I've read through the Axis documentation and it looks like its pretty
trivial to pass a bean into the service as input using
--- Begin Message ---
EveryThing seems to work well except the fact that the byte array is null!!
I know that, on the server side, the byte array is conformed.
It seems that the byte array isn't serialized from the server to the
client.
I hope that I've clearly exposed my problem and that someb
m Serialization/Deserialization with the
BeanSerializer/Deserializer
Hi all axis-users,
I wanted to get on the client side a bean created on the server side.
The bean is described as follow :
public class XMLRepresentation implements java.io.Serializable {
private byte[] xmlRepresentati
Hi all axis-users,
I wanted to get on the client side a bean created on the server side.
The bean is described as follow :
public class XMLRepresentation implements java.io.Serializable {
private byte[] xmlRepresentation_;
public XMLRepresentation() {
}
public XMLRepresentation(Object represent
that it is also creating a new attribute called alarmHistory;
So I changed the name of the function getAlarmHistory to giveAlarmHistory
and it worked as expected and didn’t make alarmHistory as an attribute.
Is this an expected behavior in BeanSerializer ?
Has any body else seen something
MAIL PROTECTED]
Sent: Monday, June
28, 2004 1:01 PM
To: [EMAIL PROTECTED]
Subject: RE: BeanSerializer and
xml attributes
Per the definition of
"wrapped" in JAX-RPC (and in the way .NET works), wrapped does not
support attributes - only a sequence of elements.
From: We
AIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: BeanSerializer and xml attributes
Date: Mon, 28 Jun 2004 13:01:06 -0700
Per the definition of "wrapped" in JAX-RPC (and in the way .NET works),
wrapped does not support attributes - only a sequence of
Per the definition of “wrapped”
in JAX-RPC (and in the way .NET works), wrapped does not support attributes –
only a sequence of elements.
From: Wei Hsu
[mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 11:56
AM
To: [EMAIL PROTECTED]
Subject: BeanSerializer and xml
Hi all,
I was wondering if anyone knows whether axis's BeanSerializer
actually supports xml attributes. Currently when I try to send a doc/lit
wrapped message with the following xml element:
a
2
The BeanSerializer always ignores the attribute &quo
Are there any Axis developers that monitor this list that might be able
to answer these questions or should I post this on the developer list to
find an answer?
If I have a custom data type that is (de)serialized with the
BeanSerializer and one of the properties of the bean is an int, how can
I
If I have a custom data type that is (de)serialized with the
BeanSerializer and one of the properties of the bean is an int, how can
I specify that it is restricted to a set of integers (i.e. define a
restriction base in the WSDL)?
I had asked another question about making an element so that it
BeanSerializer I defined in my deploy.wsdd
file is being picked up by ?WSDL, because I see the proper
definition in the WSDL in my web browser. However, when I try to run the
Java2WSDL task, I don't get a complex type (I just get my object specified
in the WSDL as an xsd:anyType). How come ?WSDL
the serializer/deserializer, so, the
call seemed to be ok. But now, I need to serialize again the object. I
supposed that I can use the BeanSerializer, but I found that the
serialize method also needs a context and some sax attributes, and I'm
not sure about what to pass in these places.
An
Return Receipt
Your Re: Using built-in BeanSerializer with getPort()
document
Return Receipt
Your Re: Using built-in BeanSerializer with getPort()
document
- Original Message -
From: "Torsten Schlabach" <[EMAIL PROTECTED]>
Newsgroups: gmane.text.xml.axis.user
Sent: Thursday, August 21, 2003 9:24 AM
Subject: Using built-in BeanSerializer with getPort()
> Dear List,
>
> I am not sure if I mix up anything but for w
new QName(nameSpaceUri, portName), QueryService.class);
I understand that I would need to let Axis know that it should use the
built-in BeanSerializer to serialize my comples type. Just where would I do
that.
All samples I found so far were based on the Call.invoke() method.
Torsten
" type mapped by the BeanSerializer and "a" type mapped by my CastorSerializer in my WSDD.
What I end up with at runtime is this:
And my Castor(De)Serializer hacks when it cannot find an "a" within an "a".
If tri
If you mean you want to use the built in BeanSerializer on the client side
then all you have to do is register the bean in the call with a serializer
and push it down. Eg:
Call = Service.getCall();
Call.setTargetEndPoint("http://middle.of.nowhere/service";);
//Begin what I think y
Hi,
If anyone could give me a quick howto on how to use the
org.apache.axis.encoding.ser.BeanSerializer class to marshall a java instane
to an xml file I would appreciate.
Thanks for any hints
- David
Hello,
I have an class, we'll call it path.to.Component, that is a bean. I
have another bean, let's say path.to.Wrapper, that contains a
path.to.Component[] . Now when I navigate to
http://localhost/axis/services/SOAPTEST?wsdl I get server side errors
that it is unable to serialize java.awt.Co
hi,
is it right that wsdl2java generated BeanSerializer/Deserializer will only
work with soap-encoded structures? Or will the BeanSerializerFactory/
BeanDeserializerFactory choose a BeanSerializer/Deserializer depending
on the choosen encoding - like soap-encoding or literal?
Thanx,
Mischa
My bean, Company.java aggregates
an array of another bean: Person. When the BeanSerializer serializes this
object using doc/lit, with a valid array of People, the resulting array is
not wrapped, eg:
SomeCompany
John
24
Tim
24
EMAIL PROTECTED]'
Subject: RE: BeanSerializer
Hi Tom
I think what I was really asking was if there was a way to turn off
serialization in Java2WSDL for certain properties? Is it
something that other users have requested? It would help me as I have a lot
of prexisting classes, some of which
:47 PM
To: '[EMAIL PROTECTED]'
Subject: RE: BeanSerializer
All the data in the Bean is serialized, so all the element show up in the
Schema. It's the other sides responsibility to deserialize the data in to a
data type. The thing on the other end of the wire may not be Java,
2Java will emit a class that will allow the
Schema to be deserialized in to it.
Tom Jordahl
Macromedia Server Development
-Original Message-
From: Mark Rowell [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 9:19 AM
To: '[EMAIL PROTECTED]'
Subject: BeanSerializer
Hi
Hi
I was wondering why it was necessary for Java2WSDL generate an element in a
complex type for properties of a class that are read-only?
After all when deserializing an instance of a class with read-only
properties how is it going to set the value of the property in the new
instance?
Am I wrong o
Johannes,
Can you please file a bug report? (see this howto url -
http://nagoya.apache.org/wiki/apachewiki.cgi?SubmitPatches)
Thanks,
dims
--- Johannes Fiala <[EMAIL PROTECTED]> wrote:
> I have found that there seems to be a typo in the file
> axis-1_1beta/samples/userguide/example5/deploy.wsdd
I have found that there seems to be
a typo in the file
axis-1_1beta/samples/userguide/example5/deploy.wsdd
After I corrected the "qName"
attribute to "qname" the sample worked correctly.
correct version:
Maybe this should be corrected in the
AXIS 1.1beta version as well, because this is quite
Hi there,
I now have removed everything from my
classpath except the Apache AXIS libraries to make debugging easier:
CLASSPATH: e:\axis-1_1beta\lib\axis.jar;e:\axis-1_1beta\lib\jaxrpc.jar;e:\axis-1_1beta\lib\commons-logging.jar;e:\axis-1_1beta\lib\commons-discovery.jar;e:\axis-1_1beta\lib\saaj.j
Hi there,
I just tried the example 5 for bean
serializing/deserializing, but I received the following error:
Error : org.xml.sax.SAXException:
Deserializing parameter 'arg1': could not fin
d deserializer for type {urn:BeanService}Order
The commands I issued:
java org.apache.axis.client.AdminCl
Hi there,
I just tried the example 5 for bean
serializing/deserializing, but I received the following error:
Error : org.xml.sax.SAXException:
Deserializing parameter 'arg1': could not fin
d deserializer for type {urn:BeanService}Order
The commands I issued:
java org.apache.axis.client.AdminCl
Joel,
Creating complex object graphs is the most difficult part of Java/XML
serialization and deserialization (no duh right :-). Well, in your case it
looks like, unless MyObject also conforms to the JavaBean paradigm, you
need to write some classes to handle serialization. Classes like
MyObjec
Title: RE: BeanSerializer support array properties?
i had a similar problem and adding a no argument constructor seemed to fix it. it seems that the BeanSerializer is perhaps not very good at letting you know if your bean does not comply with the java beans spec.
-Original Message
to autogenerate the WSDL right to include the
contained class?
Thanks,
-joel
-Original Message-
From: Shellman, Joel
Sent: Thursday, July 25, 2002 1:31 PM
To: '[EMAIL PROTECTED]'
Subject: BeanSerializer support array properties?
Does the BeanSerializer support indexed p
Does the BeanSerializer support indexed properties?
So if I have:
MyObject[] myObjects;
MyObject[] getMyObjects() {
return this.myObjects;
}
inside my class, will the BeanSerializer automatically handle it? It doesn't
seem to (it ignores that field completely in both the
{ message,env }
);
When Axis tries to
get the serializer it falls to the getSerializerAs method of
BaseSerializerFactory and the tests in that method end up trying call
newInstance on the BeanSerializer class. There is no default constructor
in BeanSerializer and a java.lang.InstantiationExce
BeanSerializer is not adding xsi:type if the value
of the field is null. If xsi:type is missing then the server is not able
to deserialize.
I am using axis nightly drop of 05-31 on client
side and soap toolkit which comes along with Websphere on the server end.
Does any one experience
>
>
>
>
>
> You may also want to try the hint re
> -Djava.endorsed.dirs=path_to_axis_lib
>
> - Original Message -
> From: "Stefan Wagner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 30, 2002 9:24 AM
> Subj
-Djava.endorsed.dirs=path_to_axis_lib
- Original Message -
From: "Stefan Wagner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 9:24 AM
Subject: Error with BeanSerializer
Hi!
I try to use Java2WSDL and WSDL2Java. I created a simple bean which I want
t
Hi!
I try to use Java2WSDL and WSDL2Java. I created a simple bean which I want to
return from a method of my service. When I invoke the service with a tester I
get the following exception:
Exception in thread "main" Internal Server Error
at
org.apache.axis.transport.http.HTTPSender.in
After working with various complex objects with our Axis web services,
we've discovered several rules when using the built-in BeanSerializer
and BeanDeserializer (above and beyond the JavaBean spec).
These constraints were found while using the Axis Beta1 released on
03/19/2002.
They are de
I apologize if this is a stupid question, but is there any way to tell
Axis to use the BeanSerializer by default for any Java class that hasn't
had a specific serializer registered for it ?
I'm trying to write a Java client-side for a generic server service
allowing SOAP clients to ca
> Currently the BeanSerializer is very strict ie it expects a type
> mapping for MyInterface even though the value is null. This means that
> I will have to write a dummy class which implements MyInterface, and
> then add a mapping for this.
>
> Could the BeanSerializer be changed so that it
I have a property in a bean that is declared as
private MyInterface intf;
This property is always null and will never change in my application.
Currently the BeanSerializer is very strict ie it expects a type mapping
for MyInterface even though the value is null. This means that I will have
to
63 matches
Mail list logo
