Hm... gd is a jboss gravel tag... So maybe try add gravel.jar to the project - maybe it will help...
link to jboss gravel page http://www.jboss.org/gravel/
Good thought, but gravel.jar is already in the deployed pacakge, here:
The problem seems to come from the EL processor trying to interpret the expressions in the attributes of the gd: tags...
JBoss EL has some extension for passing parameters to methods (at least afaik) maybe those are in the way
This seems to be still an issue, which is a bit disgusting for Glassfish users :-( Anybody has new thoughts on this? Or solved it without just removing sorting and filtering?
It's most likely caused by the same thing as why the console does not run out of the box on JBoss AS5. Solutions can be found in combining things from Jira and reading some posts in the forum for additional info. I unfortunately cannot make the time to fix these.
thanks for the answer! Could be, unfortunately I run out of time for this issue as well :-/ But with removing all gravel sort and filter tags as proposed, the console works on Glassfish correctly, which is OK for me at this moment...
Please, help me somebody know how install jbpm on glassfish?
Which version of jBPM -- 3 , 4 or 5?
Do you know how install jbpm on glassfish?
(Sorry for misspelling your name!)
It shouldn't be that much more different than installing it on jBoss. I don't have much experience with Glassfish but I took a quick look at how it works last week and given that it's also a java EE 5/6 compliant application server, I don't expect there to be that many problems installing jBPM on it.
What I'm planning to do is to essentially look at what the jbpm-installer installs on the jBoss server and duplicate that on Glassfish and see if that works. (I would like to know how install jBPM on glassfish for myself!)
You can find the ant build file at the link below. The ant file has targets that execute all of the installer actions and thus install jBPM -- and some other helpful things -- on a Jboss server:
I probably won't get around to doing this for another week or two. If you do run into any problems, please do post them on the forums!
"For others who end up reading this thread, a workaround has been found for this problem: see the modified gravel jar attached tohttps://issues.jboss.org/browse/JBPM-3302"
Thanks Marco, this fix the problem on Weblogic 12c too.