Hibernate Books

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  [ 16 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: XML Marshalling/Unmarshalling
PostPosted: Mon Nov 17, 2003 9:54 am 
Beginner
Beginner

Joined: Tue Aug 26, 2003 1:02 pm
Posts: 34
Location: Akron, OH
Pretty OT, but I thought I might get some insightful answers here.
Does anyone know of a good marshalling/unmarshalling solution?
XMLBeans only works with JDK 1.4 and we need a 1.3 solution.
Sun's RI of JAXB seems kinda slow. We need something faster, if possible.
Enhydra Zeus doesn't handle our xsd correctly.

Any suggestions would be appreciated.

Thanks

Eric


Top
 Profile  
 
 Post subject: Re: XML Marshalling/Unmarshalling
PostPosted: Mon Nov 17, 2003 2:48 pm 
Newbie

Joined: Sat Aug 30, 2003 12:37 pm
Posts: 16
Hi,

I've been using Castor XML for a few months now and it works great.

http://castor.exolab.org/

You might want to look into Jibx as well. Its supposed to be the fastest framework for binding XML data to Java objects. Its in beta right with a production version 1.0 by end of the year.

http://jibx.sourceforge.net/

slug.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Nov 17, 2003 2:54 pm 
Thanks. I got the Castor recommendation from somone else, as well. Working well so far. My test message now takes 20ms to unmarshall vs 80 - 90 with JAXB.


Top
  
 
 Post subject:
PostPosted: Thu Dec 18, 2003 5:18 pm 
Newbie

Joined: Thu Dec 18, 2003 3:20 pm
Posts: 6
Have you tried the XMLEncoder/XMLDecoder that is part of the JDK1.4?

If you're not worried about the XML structure it might be a good choice.


Top
 Profile  
 
 Post subject: JiBX is close to Hibernate
PostPosted: Sun Feb 01, 2004 1:11 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
The way JiBX works, with an XML mapping file and byte code enhancement, seems very similar to the way Hibernate works.

Since it seems to make sense to unify these mapping technologies (does Castor achieve this?), wouldn't it make sense to extend Hibernate in some similar way so that infrastructure could be unified for Java/SQL/XML mapping? One immediate benefit: if I could do my queries using HQL and get my results as XML without having to create intermediate Java objects...

The benefits should be obvious for architectures which leverage XSLT or web services... Is this even on the radar screen for Hibernate??

See http://jibx.sourceforge.net/index.html for more information on JiBX.

_________________
Stuart Zakon
Objects by Design
http://www.objectsbydesign.com


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 1:13 pm 
Hibernate Team
Hibernate Team

Joined: Mon Aug 25, 2003 9:11 pm
Posts: 4592
Location: Switzerland
Well, I don't think that this is a core functionality of object/relational mapping, but I can see some use as an addon. It's not on any todo list though ;)

_________________
JAVA PERSISTENCE WITH HIBERNATE
http://jpwh.org
Get the book, training, and consulting for your Hibernate team.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 2:06 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
It may not be directly part of O/R mapping but it is definitely part of what real J2EE applications deal with: web services for a service oriented interface and XSLT for a clean MVC framework.

It just seems so inefficient to create artificial boundaries over what goes in a persistence framework when XML, Java, and RDBMS are such core technologies and there continues to be this "impedance mismatch" that everybody is trying to solve. Better to have a single unifying framework. Especially, whereas the mapping technology is so similar.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 2:09 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 12:50 pm
Posts: 5130
Location: Melbourne, Australia
I'm not sure that I understand the notion that a persistence service should do persistence is an "artificial boundary".

Notice that we are talking about two different impedence mismatches here: object/relational and object/heirarchical.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 2:26 pm 
Hibernate Team
Hibernate Team

Joined: Mon Aug 25, 2003 9:11 pm
Posts: 4592
Location: Switzerland
And, there is no end in that logic. We might as well add a GUI validation framework, GUI component databinding and a network communication layer to Hibernate, if we want a unifying framework ;)

We should stop when it can read e-mail though...

_________________
JAVA PERSISTENCE WITH HIBERNATE
http://jpwh.org
Get the book, training, and consulting for your Hibernate team.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 2:29 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 12:50 pm
Posts: 5130
Location: Melbourne, Australia
Actually, the end goal is HibernateOS.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 01, 2004 3:10 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
OK guys, I get the message.

But Gavin, surely you know that all the major RDBMS vendors deal with retrieving query results as XML. It is clearly a real world problem that they have been addressing for a while and with good results. So constraining the problem domain to object/relational prevents hibernate from getting the leverage that these vendors get when they hook up all these components under the hood.

What you're saying is that if I want the efficiency of going from a query to an XML result, I would have to resort to the native database mechanisms (they are all different) rather than having a single portability layer. What is distasteful about this is that then I am building hybrid solutions - half hibernate when I want objects and half native RDBMS when I want XML. With two different query languages.

The alternative is to build the XML persistence piece separate from hibernate. Perhaps that is the answer. Just seems like a lot of duplication of the overlapping technology. Especially if I want to use one query language.

_________________
Stuart Zakon
Objects by Design
http://www.objectsbydesign.com


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 03, 2004 3:15 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
It seems that Microsoft understands the impedance mismatch referred to above very well.

In what appears to be a deliberate leak, a research paper on a new Microsoft language called Xen was published:
http://www.cl.cam.ac.uk/~gmb/Papers/vanilla-xml2003.htm

Xen addresses the impedance mismatch by creating a language that unifies access to XML and SQL data. This looks like exciting stuff and directly addresses the issues raised earlier in this thread.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 03, 2004 3:17 pm 
Hibernate Team
Hibernate Team

Joined: Mon Aug 25, 2003 9:11 pm
Posts: 4592
Location: Switzerland
Microsoft also invented a user interface called "Bob". ;)

_________________
JAVA PERSISTENCE WITH HIBERNATE
http://jpwh.org
Get the book, training, and consulting for your Hibernate team.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 03, 2004 3:18 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
Sorry, corrected URL:
http://www.cl.cam.ac.uk/~gmb/Papers/van ... l2003.html


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 03, 2004 3:23 pm 
Beginner
Beginner

Joined: Mon Nov 24, 2003 10:44 am
Posts: 22
And they also have over 50B in the bank...

Christian, just let your forum readers decide for themselves instead of trying to influence them.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 16 posts ]  Go to page 1, 2  Next

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.