[jboss-jira] [JBoss JIRA] Commented: (JBAS-3736) JBoss AS 4.0.5.CR1 does not include jaxen, which is required for using Hibernate XML mapping

Dimitris Andreadis (JIRA) jira-events at jboss.com
Fri Oct 6 04:37:42 EDT 2006


    [ http://jira.jboss.com/jira/browse/JBAS-3736?page=comments#action_12344754 ] 
            
Dimitris Andreadis commented on JBAS-3736:
------------------------------------------

I'm thinking of including jaxen-1.1-beta-9 in the server/default|all/lib directory.

>From the release notes it seems beta-10 introduces some minor incompatibilities, while from beta-7 to beta-9 changes seem compatible.

"The current version is 1.1 beta 10. 1.1 is a major upgrade that significantly improves jaxen's conformance to the underlying XPath specs. Even though it's still officially a beta, this release is a vast improvement over 1.0, and all users are strongly encouraged to upgrade. With a few small exceptions (e.g. the the document() function has moved to the org.jaxen.function.xslt package, the IdentityHashMap class has been deleted, and the ElectricXML navigator has been deleted) 1.1 is backwards compatible with code written to the 1.0 APIs."

Jaxen 1.1 Beta 9
Beta 9 contains some small optimizations, improvements to the documentation, and minor bug fixes. The license should now be the same across all the files. 

Jaxen 1.1 Beta 8
Beta 8 fixes a couple of bugs in XPath evaluation and optimizes the code in several places. The test suite has been expanded. 

Jaxen 1.1 Beta 7
Beta 7 fixes a number of important bugs, especially involving operator associativity, the string and substring functions, and the dom4j navigator. The various root exception classes (JaxenException, JaxenRuntimeException, and SAXPathException) and all their subclasses now support Java 1.4 exception chaining even in 1.3 and earlier VMs. The DOM navigator should compile and run in both Java 1.4 and 1.5 (i.e. DOM level 2 and DOM Level 3). Namespace handling in DOM is more accurate. Paths can be begin with parenthesized steps like (//foo)/x. Beta 7 also features a reorganized, more modular test suite and expanded and improved API documentation. 


> JBoss AS 4.0.5.CR1 does not include jaxen, which is required for using Hibernate XML mapping
> --------------------------------------------------------------------------------------------
>
>                 Key: JBAS-3736
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3736
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading
>    Affects Versions: JBossAS-4.0.5.CR1
>         Environment: SUSE Linux 10.0, Sun JRE 1.5.0_05-b05
>            Reporter: Don Smith
>         Assigned To: Emmanuel Bernard
>             Fix For: JBossAS-4.0.5.GA
>
>
> Hibernate XML mapping requires using the org.dom4j.Document, as shown in this example:
> 		org.dom4j.Document document = saxReader.read(inputXML);
> 		List users = document.selectNodes("//product");
> 		try {
> 			Session session = HibernateUtil.sessionFactory.openSession();
> 			Transaction transaction = session.beginTransaction();
> 			Session dom4jSession = session.openSession(EntityMode.DOM4J);
> 			Iterator iter = users.iterator();
> 			while (iter.hasNext()) {
> 				Object next = iter.next();
> 				dom4jSession.saveOrUpdate("demo.Product", next );
> 			}// end while
> 			transaction.commit();
> 			session.close();
> If any other type of Document is used for the dom4jSession.saveOrUpdate() call, it throws an exception.
> Using SAXReader.read() throws a NoClassDefFound error using JBoss 4.0.5.CR1, unless jaxen (jaxen-1.1-beta-7.jar from the Hibernate 3.2.cr4 download) is added the the server configuration's lib directory.
> I submit that jaxen is required to use the XML Mapping facility of Hibernate, and that it's missing from JBoss 4.0.5.CR1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list