Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / August 2005

Tip: Looking for answers? Try searching our database.

Curious problem when applying XSLT.....

Thread view: 
nick@codefresh.com - 26 Aug 2005 10:12 GMT
Hi all,

I've a curious problem at the moment and was wondering whether anyone
might be able to help. I have a SOAPBodyElement object that was
returned from a SOAP call. I then convert this into a Document object
and then attempt to apply a XSLT file to it. Unfortunately the output
produced by this transformation is incorrect. Effectively the XSLT is
not being applied correctly. Bizarrely if I serialize the document to a
byte array and then create a new document based on it (by using
docBuilder.parse()), it works! I've output both documents as strings
and then compared them and they're identical. All very weird. Any
ideas?

Nick
Raymond DeCampo - 26 Aug 2005 12:56 GMT
> Hi all,
>
[quoted text clipped - 8 lines]
> and then compared them and they're identical. All very weird. Any
> ideas?

The first thing that comes to mind is that the implementation of
Document you get from the SOAPBodyElement object is different from the
implementation of Document that you get from parsing the text via a
stream and that one of the implementations has a bug.

HTH,
Ray

Signature

XML is the programmer's duct tape.

Nick - 26 Aug 2005 14:21 GMT
Hmm, I'm using the javax.xml.soap.SOAPBodyElement and
org.w3c.dom.Document classes so I'd be suprised if there was a bug with
these. I suppose it might be the javax.xml.transform.Transformer class
I'm using. I've tried both the default one that comes with WebLogic 8.1
and Xalan but both exhibit the same problem.

Nick
Raymond DeCampo - 27 Aug 2005 02:56 GMT
> Hmm, I'm using the javax.xml.soap.SOAPBodyElement and
> org.w3c.dom.Document classes so I'd be suprised if there was a bug with
> these. I suppose it might be the javax.xml.transform.Transformer class
> I'm using. I've tried both the default one that comes with WebLogic 8.1
> and Xalan but both exhibit the same problem.

I'm not familiar with javax.xml.soap.SOAPBodyElement, but
org.w3c.dom.Document is an interface.  The implementation is provided by
the XML parser, which can be specified by JAXP.

It may be helpful if you could provide a SSCCE, although that may be
difficult in this case.

Ray

Signature

XML is the programmer's duct tape.



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.