no it is not out yet. 3.2.GA is the latest
http://sourceforge.net/project/showfiles.php?group_id=70542&package_id=145174&release_id=494134
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053215#4053215
Reply to the post :
http://www.jboss.com/index.html?modul
Sorry I'm totally out topic but... Is 3.2.1 GA out? Where can I see if it is
out or not? How can I get it?
I see the 3.2 GA release on SourceForge because I went there before looking
here... If I didn't I would have been stuck with 3.1.4 since it appears to be
the last usable release from here.
Found it!
In your WEB-INF for the console, insert this "weblogic.xml" file:
| http://www.bea.com/ns/weblogic/90";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
|
|
| true
|
|
-Ed Staub
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
You need to include the jars you require in your ear file, and then tell
WebLogic to use them in favor of its built-in jars.
Sorry, I (frustratingly) don't remember where you tell WebLogic to prefer the
ear's jars over its own.
-Ed Staub
View the original post :
http://www.jboss.com/index
The difference between case one and two is no wonder.. in case one the jsf tags
are not interpreted and it is just plain xhtml. In the second case the parser
comes in.
I have no idea about the cause though. I (myself) quit trying to use weblogic
at all because of many similar issues with hibern
"mputz" wrote : It looks like WL is using it's own SAXParser implementation
instead of the apache one (which is bundled in
/lib/endorsed/xercesImpl.jar btw). Have a look at this docu, it's
referring to an older WL version but I guess one of the ways to get around this
issue described there shou
It looks like WL is using it's own SAXParser implementation instead of the
apache one (which is bundled in /lib/endorsed/xercesImpl.jar btw).
Have a look at this docu, it's referring to an older WL version but I guess one
of the ways to get around this issue described there should still work:
ht
"kukeltje" wrote : isn't there more info in the logs? this is to little to be
helpful
Exactly. I have gone through the source code of
org.jbpm.webapp.tag.jbpm.JbpmLibrary as well. Line where it?s showing exception
is written in a constructor of the JbpmLibrary class.
I seems like exception has
isn't there more info in the logs? this is to little to be helpful
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052428#4052428
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052428
