Markus,
Can you give me details of what you've tried to get and the errors that
you're getting? I'd imagine at lot of the issues are JSF / GWT / Seam
related , on top of the 1.5 v 1.4 problems. I may be able to make some
suggestions when I get time - day jobs pemitting :-) On a unrelated
project , we did manage to get a similar app working on an older Sun App
Server; If I had to do it again I would spend my time to get a more
modern app server!
Remember that typically the BRMS is an editing tool used by 2-10 people,
so a case could be made for a 'local' Tomcat or JBoss. The rules can
then be exported from this and deployed on the existing production
Websphere (JVM version permitting) - no BRMS needed there.
Paul
www.firstpartners.net/blog
Markus Helbig wrote:
tried it for several hours, but hadn't success to get it running ...
2007/10/17, Mark Proctor <[EMAIL PROTECTED]>:
Paul Browne wrote:
Haven't tried it in this context , but would using Retroweaver help
?(Java 5 code compiled to work in Java 1.4 JVM)
It may do, but we don't have the resources to QA this, so its up to the
community to see if that works.
Mark Proctor wrote:
Markus Helbig wrote:
that's a real pitty ... it's a great thing ... but WebSphere 6.0.x is
using JRE 1.4 ... damned
There are still people out there using drools 2.x because they are on
JDK1.3. But their comes a time when the advantages of moving
outweight the advantages of staying, its not an easy decision but
jdk1.4 has been around since 2003, so I think we've supported it long
enough. Our next major release will be jdk1.5 only, both BRMS and
engine.
2007/10/15, Mark Proctor <[EMAIL PROTECTED]>:
Markus Helbig wrote:
Hi,
i tryed to deploy the BRMS on a WebSphere Server, but i get
incompatibility errors. It seems BRMS can not be used with JRE 1.4.x,
right? Why? JRE 1.4.x is still very common and often used in
enterprises ...
yup the BRMS is JDK1.5 - welcome to the future :)
Cheers
Markus
Stacktrace is:
Could not be defined due to: (org/jboss/seam/servlet/SeamListener)
bad
major version at offset=6
This is often caused by having a class defined at multiple
locations within the classloader hierarchy. Other potential causes
include compiling against an older or newer version of the class
that has an incompatible method signature.
Dumping the current context classloader hierarchy:
==> indicates defining classloader
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
------------------------------------------------------------------------
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
