[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-20 15:07
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha-Matthias Kulawik (skulawik)
Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52
Message:
Logged In: YES
user_id=175228
All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.
--
Comment By: David Budworth (dbudworth)
Date: 2004-07-21 12:06
Message:
Logged In: YES
user_id=343354
Added solution to original topic:
http://jboss.org/index.html?module=bb&op=viewtopic&t=51255
Basic jist is, current dom4j-1.5-rc1 does not seem to expose this conflict.
It may not be a 100% proper solution, but it does allow someone to move
from < 3.2.4 to 3.2.4 + without getting the nosuchmethod exceptions
--
Comment By: David Budworth (dbudworth)
Date: 2004-07-21 09:01
Message:
Logged In: YES
user_id=343354
Here is a simple EAR file (source packaged inside) that
shows the conflict with the versions of Jaxen in jdom and
jboss 3.2.4+
(I don't see an attach check box, I'm just hoping that it
will show up after I submit this)
--
Comment By: Sascha-Matthias Kulawik (skulawik)
Date: 2004-05-25 12:57
Message:
Logged In: YES
user_id=362237
Page not created yet?
Do you have the right URL?
--
Comment By: Scott M Stark (starksm)
Date: 2004-05-21 10:44
Message:
Logged In: YES
user_id=175228
3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
If this does not work create an ear which demonstrates the
problem.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-20 15:07
Message generated for change (Comment added) made by dbudworth
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha-Matthias Kulawik (skulawik)
Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
Comment By: David Budworth (dbudworth)
Date: 2004-07-21 12:06
Message:
Logged In: YES
user_id=343354
Added solution to original topic:
http://jboss.org/index.html?module=bb&op=viewtopic&t=51255
Basic jist is, current dom4j-1.5-rc1 does not seem to expose this conflict.
It may not be a 100% proper solution, but it does allow someone to move
from < 3.2.4 to 3.2.4 + without getting the nosuchmethod exceptions
--
Comment By: David Budworth (dbudworth)
Date: 2004-07-21 09:01
Message:
Logged In: YES
user_id=343354
Here is a simple EAR file (source packaged inside) that
shows the conflict with the versions of Jaxen in jdom and
jboss 3.2.4+
(I don't see an attach check box, I'm just hoping that it
will show up after I submit this)
--
Comment By: Sascha-Matthias Kulawik (skulawik)
Date: 2004-05-25 12:57
Message:
Logged In: YES
user_id=362237
Page not created yet?
Do you have the right URL?
--
Comment By: Scott M Stark (starksm)
Date: 2004-05-21 10:44
Message:
Logged In: YES
user_id=175228
3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
If this does not work create an ear which demonstrates the
problem.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-20 15:07
Message generated for change (Comment added) made by dbudworth
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha-Matthias Kulawik (skulawik)
Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
Comment By: David Budworth (dbudworth)
Date: 2004-07-21 09:01
Message:
Logged In: YES
user_id=343354
Here is a simple EAR file (source packaged inside) that
shows the conflict with the versions of Jaxen in jdom and
jboss 3.2.4+
(I don't see an attach check box, I'm just hoping that it
will show up after I submit this)
--
Comment By: Sascha-Matthias Kulawik (skulawik)
Date: 2004-05-25 12:57
Message:
Logged In: YES
user_id=362237
Page not created yet?
Do you have the right URL?
--
Comment By: Scott M Stark (starksm)
Date: 2004-05-21 10:44
Message:
Logged In: YES
user_id=175228
3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
If this does not work create an ear which demonstrates the
problem.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-21 00:07
Message generated for change (Comment added) made by skulawik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha Kulawik (skulawik)
Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
>Comment By: Sascha Kulawik (skulawik)
Date: 2004-05-25 21:57
Message:
Logged In: YES
user_id=362237
Page not created yet?
Do you have the right URL?
--
Comment By: Scott M Stark (starksm)
Date: 2004-05-21 19:44
Message:
Logged In: YES
user_id=175228
3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
If this does not work create an ear which demonstrates the
problem.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-20 15:07
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha Kulawik (skulawik)
>Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
>Comment By: Scott M Stark (starksm)
Date: 2004-05-21 10:44
Message:
Logged In: YES
user_id=175228
3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
If this does not work create an ear which demonstrates the
problem.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss >=3.2.4
Bugs item #957704, was opened at 2004-05-21 00:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha Kulawik (skulawik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Jaxen-based Applications no longer working wth JBoss >=3.2.4
Initial Comment:
Hello,
I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
element in the applications.xml of my ear.
Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=957704&group_id=22866
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
