The problem is with the "Drools Runtime". As part of the
setup for creating a Drools Project for the first time, the user is asked to create a
"Drools Runtime". This is new (in the past Drools IDE new which set of jars to
use),
No it didn't - it just had some random copy from inside the drools
plugin which would not necessarily match the server it is running on.
to be consistent with other tools and allow user to select different
Drools Runtimes. The challenge for the user is how to define a Drools Runtime. You can
either find the jars in JBDS plugins, explode them into a folder, and point to them, or
download Drools engine/expert (in this case I had decided to try
jboss-brms-engine-5.ea.zip, since this is the .com version). However when this is
unzipped, some jars are in the root of the folder and some are in a lib directory. At
least four of the ones in the lib directory are required for runtime
(antlr-runtime-3.1.1.jar, core-3.4.2.v_883_R34x.jar, mvel2-2.0.5.jar, xstream-1.3.1.jar),
and the jars in a subdirectory are not added to the runtime classpath. I knew this but
forgot to move antlr-runtime-3.1.1.ja!
r.
Yes, the big problem is that there seem to be no way for us to define a
drools runtime based on SOA-P. That is the last I heard about it from
Kris V.
If someone from SOA-P can tell us which jar's users should use to define
the jars then we could automatically include those in the runtime.
I also need to follow up with the drools functionality since it should
not be a *requirement* to have the drools runtime on a project; it
should just be in the classpath.
/max
I entered a JIRA for this.
Jeff
----- Original Message -----
From: "Max Rydahl Andersen"<max.andersen(a)redhat.com>
To: "Jeffrey Delong"<jdelong(a)redhat.com>
Cc: "John Graham"<jgraham(a)redhat.com>, jbosstools-dev(a)lists.jboss.org,
"Mark Little"<mlittle(a)redhat.com>, "Mark
Proctor"<mproctor(a)redhat.com>, "Kris
Verlaenen"<kverlaen(a)redhat.com>, "Koen Aers"<kaers(a)redhat.com>,
"Burr Sutter"<bsutter(a)redhat.com>, "Leonard
Dimaggio"<ldimaggi(a)redhat.com>, "Kevin
Conner"<kconner(a)redhat.com>, "Garvin
Dean"<garvin.dean(a)amentra.com>, "Edgar A
Silva"<edgar.silva(a)redhat.com>, "Prakasha
Aradhya"<paradhya(a)redhat.com>, "Max
Andersen"<manderse(a)redhat.com>, "Trevor
Kirby"<tkirby(a)redhat.com>
Sent: Wednesday, January 28, 2009 12:34:47 AM GMT -07:00 US/Canada Mountain
Subject: Re: UPDATE: Assistance in testing JBDS with SOA-P
On 28-01-2009 05:07, Jeffrey Delong wrote:
I tested out the Drools IDE in JBDS. I used the Drools icon to create a new Drools
project, and ran the DroolsTest class the wizard created as a Java Application. I got the
following exception:
java.lang.NoClassDefFoundError: org/antlr/runtime/CharStream Please report such things
directly in jira - thanks.
/max
Jeff
----- Original Message -----
From: "John Graham"<jgraham(a)redhat.com> To: "Jeffrey
Delong"<jdelong(a)redhat.com> Cc: "Max Rydahl
Andersen"<max.andersen(a)redhat.com> , jbosstools-dev(a)lists.jboss.org ,
"Mark Little"<mlittle(a)redhat.com> , "Mark
Proctor"<mproctor(a)redhat.com> , "Kris
Verlaenen"<kverlaen(a)redhat.com> , "Koen
Aers"<kaers(a)redhat.com> , "Burr Sutter"<bsutter(a)redhat.com> ,
"Leonard Dimaggio"<ldimaggi(a)redhat.com> , "Kevin
Conner"<kconner(a)redhat.com> , "Garvin
Dean"<garvin.dean(a)amentra.com> , "Edgar A
Silva"<edgar.silva(a)redhat.com> , "Prakasha
Aradhya"<paradhya(a)redhat.com> , "Max
Andersen"<manderse(a)redhat.com> , "Trevor
Kirby"<tkirby(a)redhat.com> Sent: Monday, January 26, 2009 6:53:53 PM GMT -07:00
US/Canada Mountain
Subject: Re: UPDATE: Assistance in testing JBDS with SOA-P
We have run the usual test clients from Eclipse with success, but a lot
depends on environment settings (that would be handled by ant parameters
in the command line version of the Quick Starts). Could you give us more
information about your project so we can see what might be going wrong
with the test client?
-- John
On Mon, 2009-01-26 at 20:42 -0500, Jeffrey Delong wrote:
Next issue I have had is in trying to run a test client. I copied a SendEsbMessage from a
quickstart (along with log4j.xml, juddi.properteies, and jndi.properties) and modified it,
and have tried to run it. I had to add several entries to the Run configuration classpath,
but still get
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Invocation exception. null
at
org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:474)
at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:165)
at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:146)
at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:188)
at org.acme.test.SendEsbMessage.main(SendEsbMessage.java:51)
When I look in debug mode the registry and classname are null???
I don't know if this is a supported feature but it is certainly a requirement to be
able to create and run a test client (both JMS and ESB aware).
Any thoughts?
Jeff
----- Original Message -----
From: "Jeffrey Delong"<jdelong(a)redhat.com> To: "Max Rydahl
Andersen"<max.andersen(a)redhat.com> Cc: "John
Graham"<jgraham(a)redhat.com> , jbosstools-dev(a)lists.jboss.org , "Mark
Little"<mlittle(a)redhat.com> , "Mark
Proctor"<mproctor(a)redhat.com> , "Kris
Verlaenen"<kverlaen(a)redhat.com> , "Koen
Aers"<kaers(a)redhat.com> , "Burr Sutter"<bsutter(a)redhat.com> ,
"Leonard Dimaggio"<ldimaggi(a)redhat.com> , "Kevin
Conner"<kconner(a)redhat.com> , "Garvin
Dean"<garvin.dean(a)amentra.com> , "Edgar A
Silva"<edgar.silva(a)redhat.com> , "Prakasha
Aradhya"<paradhya(a)redhat.com> , "Max
Andersen"<manderse(a)redhat.com> , "Trevor
Kirby"<tkirby(a)redhat.com> Sent: Monday, January 26, 2009 3:57:38 PM GMT -07:00
US/Canada Mountain
Subject: Re: UPDATE: Assistance in testing JBDS with SOA-P
Well I know because I read the latest SOA-P documentation, in particular the
ProgrammersGuide and ServicesGuide fairly thoroughly as I was updating training material.
I don't know how you would know unless someone from the SOA team told you: "here
is what has changed / here is what is new ..."
In this instance SmooksTransformer is still supported, however the documentation
recommends using SmooksAction instead.
Another new feature that is not accounted for in JBDS is EBWS support, which is
configured with:
<actions inXsd="/request.xsd" outXsd="/response.xsd"
faultXsd="/fault.xsd">
I am able to add it by hand to the source without complaint (I guess this is because you
have the latest xsd).
Jeff
----- Original Message -----
From: "Max Rydahl Andersen"<max.andersen(a)redhat.com> To: "Jeffrey
Delong"<jdelong(a)redhat.com> Cc: "John
Graham"<jgraham(a)redhat.com> , jbosstools-dev(a)lists.jboss.org , "Mark
Little"<mlittle(a)redhat.com> , "Mark
Proctor"<mproctor(a)redhat.com> , "Kris
Verlaenen"<kverlaen(a)redhat.com> , "Koen
Aers"<kaers(a)redhat.com> , "Burr Sutter"<bsutter(a)redhat.com> ,
"Leonard Dimaggio"<ldimaggi(a)redhat.com> , "Kevin
Conner"<kconner(a)redhat.com> , "Garvin
Dean"<garvin.dean(a)amentra.com> , "Edgar A
Silva"<edgar.silva(a)redhat.com> , "Prakasha
Aradhya"<paradhya(a)redhat.com> , "Max
Andersen"<manderse(a)redhat.com> , "Trevor
Kirby"<tkirby(a)redhat.com> Sent: Monday, January 26, 2009 1:24:10 AM GMT -07:00
US/Canada Mountain
Subject: Re: UPDATE: Assistance in testing JBDS with SOA-P
On 26-01-2009 04:00, Jeffrey Delong wrote:
Hit send to soon. Also wanted to add that the JBoss ESB EditorSmooks action configuration
is out-of-date. Smooks Transformer Action should really be Smooks Action and the class
should be org.jboss.soa.esb.smooks.SmooksAction. Also there are additional properties that
could be configured (e.g., resultType and javaResultBeanId) and the From Type and To Type
under Advanced are out-of-date as well. How can we know which are the correct ones ?
We basically only have the DTD/XSD to give us that information and we just updated to the
latest greatest .xsd less than a week ago.
Any pointers would be good.
/max
Thanks,
Jeff
----- Original Message -----
From: "Jeffrey Delong"<jdelong(a)redhat.com> To: "John
Graham"<jgraham(a)redhat.com> , jbosstools-dev(a)lists.jboss.org Cc: "Mark
Little"<mlittle(a)redhat.com> , "Mark
Proctor"<mproctor(a)redhat.com> , "Kris
Verlaenen"<kverlaen(a)redhat.com> , "Koen
Aers"<kaers(a)redhat.com> , "Burr Sutter"<bsutter(a)redhat.com> ,
"Leonard Dimaggio"<ldimaggi(a)redhat.com> , "Kevin
Conner"<kconner(a)redhat.com> , "Garvin
Dean"<garvin.dean(a)amentra.com> , "Edgar A
Silva"<edgar.silva(a)redhat.com> , "Prakasha
Aradhya"<paradhya(a)redhat.com> , "Max
Andersen"<manderse(a)redhat.com> , "Trevor
Kirby"<tkirby(a)redhat.com> Sent: Sunday, January 25, 2009 7:38:50 PM GMT -07:00
US/Canada Mountain
Subject: Re: UPDATE: Assistance in testing JBDS with SOA-P
John,
I finally got a chance to download and test out a bit. I have been using prior release of
jboss tools for the past several weeks and have had good success using the jboss-esb
config editor. I actually downloaded CR2 today, but had a couple issues:
1) I tried to use the Smooks Config Editor to configure a Java to XML transformation. I
could not use the Graph view to connect the lines. So I edited the Source by hand, and
then the Graph view correctly displayed the lines.
2) It is not clear how to create an esb archive and deploy it to jbossesb. Is this
functionality supported in this release?
Any documentation?
Thanks,
Jeff
----- Original Message -----
From: "John Graham"<jgraham(a)redhat.com> To: "Mark
Little"<mlittle(a)redhat.com> , "Mark
Proctor"<mproctor(a)redhat.com> , "Kris
Verlaenen"<kverlaen(a)redhat.com> , "Koen
Aers"<kaers(a)redhat.com> , "Burr Sutter"<bsutter(a)redhat.com> ,
"Leonard Dimaggio"<ldimaggi(a)redhat.com> , "Kevin
Conner"<kconner(a)redhat.com> , "Jeffrey
Delong"<jdelong(a)redhat.com> , "Garvin
Dean"<garvin.dean(a)amentra.com> , "Edgar A
Silva"<edgar.silva(a)redhat.com> , "Prakasha
Aradhya"<paradhya(a)redhat.com> , "Max
Andersen"<manderse(a)redhat.com> , "Trevor
Kirby"<tkirby(a)redhat.com> Sent: Thursday, January 8, 2009 12:30:09 PM GMT
-07:00 US/Canada Mountain
Subject: UPDATE: Assistance in testing JBDS with SOA-P
Following up:
1. I should have prefaced the original message with "Please feel free to
forward to anyone else (internal to RH/JB or under the appropriate
agreements for this sort of internal information) who you might think
would be interested in testing." If you do, please let me know, so I can
add them into the list of people receiving these email updates.
2. Related to (1): Why not just use a mailing list like soa-tools? There
are a couple of reasons: (a) There is no single list, or small set of
lists, that covers everyone involved (and, no, I am not sending this
request to thecore ;) ), (b) this is a short term, focused request, (c)
list requests are like talking to a stadium of people, whereas this
subset shows that I am talking to *you* :)
3. (Thanks, Len and Trev!) For the SOA-P download please use:
http://jawa05.englab.brq.redhat.com/released/soa-p-4.3.0.GA/ 4. (Thanks, Max, Len, and
Jeff!) Ignore the "all plug-ins" zips for the
tooling, and use the installer jar instead. You might find that your
browser attempts to open this jar directly instead of downloading it, in
which case you'll need to do a "save as" on the installer jar. Once
downloaded, from the command line issue "java -jar ...." with the jar
name to start the installer.
5. If you test but don't find any problems, still please drop an email
to Max and I saying that you've tried. Since "no response" does not mean
"tried it and found no problems to report," these notes will help Max
and I determine the test coverage in place for this combination.
6. Particular importance of this JBDS release: This is the release that
we'll take to EclipseCon in March, and we'd like to push it hard,
especially in the SOA area. We just need to be sure that what we push
doesn't fall over. :)
Thanks again!
John
On Wed, 2009-01-07 at 15:54 -0500, John Graham wrote:
As we reach the final stages of the JBoss Developer Studio (JBDS) 2.0
release, we are seeking help in testing the JBDS/SOA-P combination. In
particular, we're interested in how the jBPM and Drools distributions
bundled in the SOA-P product work with JBDS.
So, while testing and feedback at any stage is appreciated, the critical
period for release will be over the next 10 days or so. Any timely
feedback will help us to improve the tooling offered for this product
configuration.
The specific builds of each:
* JBDS 2.0: Use
http://reports.qa.atl.jboss.com/binaries/RHDS/release/2.0.0.CR1/200812221... via the
installer. (EAP is optional.)
* SOA-P: Use
http://jawa05.englab.brq.redhat.com/candidate/soa-4.3.0.GA_IR5/ (SOA team:
this is the link that was provided to JBDS QE a while ago; if
a later build should be used, please let us know in this thread.)
If any questions come up during testing, it probably is best to use the
jbosstools-dev(a)lists.jboss.org mailing list, since that will get the
most people in the most time zones. (Of course there's always JIRA for
bugs.)
A number of people on thread have tested various milestones of this JBDS
release, and the input has been very valuable. We hope each of you can
spare a few cycles to help us wrap up testing for this product
combination.
-- John