Re: RE: Re: Re: Re: XML problem with OpenAMF

"Carlos Rovira" <[email protected]>
Newsgroups gmane.comp.java.openamf.user
Message-ID <[email protected]>
Thanks Stephen,

But the XML is well-formed with his xml declaration and a root node. I test it with a simple node (without attrb) but it doesn't work...

btw, I think that if I must kill the attributes...I prefer the String option : )

But Thanks so much Stephen.

----------------------------- Carlos Rovira -- www.carlosrovira.com ------------------------------

----------

> De:: "Jackson, Stephen" <[email protected]>
> Para: [email protected]
> Asunto:: RE: Re: Re: Re: [Openamf-user] XML problem with OpenAMF
> BCC: Mon, 28 Mar 2005 12:33:29 -0500

Look at your xml and make sure you have a root node and it has no attributes.

----------

From: [email protected] [mailto:[email protected]] On Behalf Of Jackson, Stephen
Sent: Monday, March 28, 2005 12:00 PM
To: [email protected]
Subject: RE: Re: Re: Re: [Openamf-user] XML problem with OpenAMF

I have done something to get the same error. I should have a solution soon.

----------

From: [email protected] [mailto:[email protected]] On Behalf Of Carlos Rovira
Sent: Friday, March 25, 2005 6:34 AM
To: [email protected]
Subject: Re: Re: Re: Re: [Openamf-user] XML problem with OpenAMF

Hi Dan,

Thnk you for the guidelines, I'm using last version of OpenAMF (RC11) and JOnAS-Tomcat last version (4.1.2).

That's could be the problem, I try and return when I test your recomendations

Thanks!

C.

----------------------------- Carlos Rovira -- www.carlosrovira.com ------------------------------

----------

> De:: [email protected]
> Para: [email protected]
> Asunto:: Re: Re: Re: [Openamf-user] XML problem with OpenAMF
> BCC: Thu, 24 Mar 2005 19:37:57 -0500

Hi Dan,

Obiously, each developer has his best practices and methods and is free to use it or not. I'm currently sending XML as Strings and it works fine...ok...but I think that you could find a situation where sending XML as an object could be better for you.

I think that if I could send XML in this project would be better for me, although I for now on can continue working in other areas of my project because I have the "String" alternative.

For this reason I think important in order to get a flexible product to be able to use as many techniques as we can. If you limit OpenAMF...you are doing bad for open source alternatives like this, because the other commercial versions supports this. OpenAMF works very well as I use all this time, and this is the only problem I find.... I don't know if I'm doing something wrong or really there's a problem.

I think this is a bug, because I get XML from the server but I can't send XML to the server...

it could be great if someone that send XML to and from could say that it's posible.

thanks.

C.

----------------------------- Carlos Rovira -- www.carlosrovira.com ------------------------------

----------

> De:: Dan Glauser <[email protected]>
> Para: [email protected]
> Asunto:: Re: Re: [Openamf-user] XML problem with OpenAMF
> BCC: Thu, 24 Mar 2005 18:45:13 -0500

Perhaps I'm missing something but why are people trying to send XML via OpenAMF? OpenAMF allows you to send objects, why do those objects need to contain XML? I would think that instead of containing XML these objects could contain other objects. I feel that one of the beauties of OpenAMF is that you don't have to send XML.

On the project where we started using OpenAMF we had one Flash control that used XML which was written into the JSP page. The other Flash control used OpenAMF to get/send information to the server. I must say that the OpenAMF control worked so quickly and was so easy to maintain the we built another app which only used OpenAMF. All we passed back and forth were objects containing integers, strings, and other objects. No XML! This app works great and has become a template for our standard architecture.

Again, you may have unique requirements that I am not aware of but it seems like you may b
e making more work for yourself if you try and send XML via OpenAMF.

Good luck!

--
Dan

On Thu, 2005-03-24 at 18:03, Carlos Rovira wrote:

Thanks, but I'm currently sending it as String and works fine, but I feel like I'm loosing the power of remoting

This is a workaround and we must be able to send XML as an object...

Anybody have the same problem????

...or I'm doing something wrong?

thanks in advance.

C.

----------------------------- Carlos Rovira -- www.carlosrovira.com ------------------------------

----------

> De:: [email protected]
> Para: [email protected]
> Asunto:: Re: [Openamf-user] XML problem with OpenAMF
> BCC: Tue, 22 Mar 2005 21:25:47 -0500

Hi,

I'm using a ValueObject with a org.w3c.dom.Document property in it and I'm having problems when I send XML docs to the server.

if I send the VO to flash I have no problems, but when I fill the XML property in the Flash VO and send it to openamf gateway (running in JOnAS-Tomcat installation) I get the following trace:

[Fatal Error] :1:92: Content is not allowed in trailing section.

11:50:49,061 : XMLUtils.convertToDOM : org.xml.sax.SAXParseException: Content is not allowed in trailing section.

org.xml.sax.SAXParseException: Content is not allowed in trailing section.

at org.apache.xerces.parsers.DOMParser
.parse(Unknown Source)

at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)

at org.openamf.util.XMLUtils.convertToDOM(XMLUtils.java:101)

at org.openamf.io.AMFDeserializer.readData(AMFDeserializer.java:346)

at org.openamf.io.AMFDeserializer.readObject(AMFDeserializer.java:191)

at org.openamf.io.AMFDeserializer.readCustomClass(AMFDeserializer.java:166)

at org.openamf.io.AMFDeserializer.readData(AMFDeserializer.java:348)

at org.openamf.io.AMFDeserializer.readArray(AMFDeserializer.java:226)

at org.openamf.io.AMFDeserializer.readData(AMFDeserializer.java:335)

at org.openamf.io.AMFDeserializer.readBodies(AMFDeserializer.java:144)

at org.openamf.io.AMFDeserializer.<init>(AMFDeserializer.java:83)

at org.openamf.DefaultGateway.deserializeAMFMessage(DefaultGateway.java:154)

at org
. openamf.DefaultGateway.service(DefaultGateway.java:85)

....

11:50:49,191 : DefaultGateway.logRequestException : Error in service

java.io.IOException: Error while parsing xml: Content is not allowed in trailing section.

at org.openamf.util.XMLUtils.convertToDOM(XMLUtils.java:104)

at org.openamf.io.AMFDeserializer.readData(AMFDeserializer.java:346)

at org.openamf.io.AMFDeserializer.readObject(AMFDeserializer.java:191)

at org.openamf.io.AMFDeserializer.readCustomClass(AMFDeserializer.java:166)

at org.openamf.io.AMFDeserializer.readData(AMFDeserializer.java:348)

.....

it seems that OpenAMF doesn't like the XML object send in the valueobject because I don't reach the requested method and all the problem is deserializing the XML member. make it sense?

Maybe
I' m doing something wrong or is a bug?

Anyone knows about some kind of problem sending XML objects?

thanks.

Carlos.

----------------------------- Carlos Rovira -- www.carlosrovira.com ------------------------------

Comparte tus fotos y revélalas sin moverte de casa. Papel Kodak Royal, ¡Sólo 1 Euro gastos de envío!
OFERTA ANIVERSARIO: 15x20 por sólo 0.50eur.Tus fotos digitales en PIXELIN.COM

http://www.lycos.es/cgi-bin/nph-bounce?piemail_mail300mb|http://secure.mail.lycos.es/services/content/packs.jsp?id=free&TARGETCODE=es_footer_mail_free300_all

Lycos amplía todas las cuentas a 300Mb.
¿Todavía no tienes la tuya?

Comparte tus fotos y revélalas sin moverte de casa. Papel Kodak Royal, ¡Sólo 1 Euro gastos de envío!
OFERTA ANIVERSARIO: 15x20 por sólo 0.50eur.Tus fotos digitales en PIXELIN.COM

http://www.lycos.es/cgi-bin/nph-bounce?piemail_mail300mb|http://secure.mail.lycos.es/services/content/packs.jsp?id=free&TARGETCODE=es_footer_mail_free300_all

Lycos amplía todas las cuentas a 300Mb. ¿Todavía no tienes la tuya?

Lycos amplía todas las cuentas a 300Mb. ¿Todavía no tienes la tuya?
piemail-300mb.gif (image/gif, 5.9 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.