<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Cristiano,<br>
<br>
We have to agree with you. That factory approach is really a
"point of risk" for osgi !<br>
<br>
We had problems with hibernate too and we use Open JPA plus Aries
JPA.<br>
<br>
but you told me that there are people using drools with
blueprint. but they wouldn't get into same problems too?<br>
<br>
have you talked about this with the drools/jbpm teams ?<br>
<br>
do you mind if I contact you personally ?<br>
<br>
thanks,<br>
<br>
John<br>
<br>
On 16/12/13 12:31, Cristiano Gavião wrote:<br>
</div>
<blockquote cite="mid:52AF1CD9.8090606@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">John,<br>
<br>
I've passed sometime evaluating 6.x for equinox some months ago.
We end up given up to use it in current project because we found
lot of these classloading issues in that time. almost all
examples failed to run as is... <br>
<br>
I heard that some guys could setup JBPM fine (just a couple of
smoke tests was done, actually) using blueprint. but as I think
blueprint is too much heavy for my needs (I use DS instead) I
didn't take a look, yet...<br>
<br>
Just to anticipate your team, the major problem that identified
was the Factory architecture being used by Drools, Kie and etc.
They was planned to work with java SE <big><b>flat</b></big>
classpaths... in they world, developer just need to put the
needed jar in a place where java could find it... but we know
that is not the reality in the OSGi world.<br>
<br>
Take a look on this KieServices class [1]. that is one of the
most used class that I could see in the examples provided by
drools.<br>
<br>
Observe that this class exists in bundle Kie-API and in the line
165 will try to instantiate another class that exists in the "
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
org.drools.compiler" bundle and worst, using
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Class.forName(). <br>
You will find sentences like this everywhere in source code...
And you won't see any integration tests for each of them...<br>
<br>
As you could note, this breaks OSGi modular concept, and could
be the origin of the classloading issues your team are facing...<br>
<br>
I heard that some people could "bypass" those errors patching
the manifest generation for :<br>
A) to add an import package from the Implementation bundle
inside the API bundle ! :( that is crap<br>
B) or to add a Dynamic Import-Package [2].<br>
<br>
I had negative experiences with Dynamic Import-Package when I
tried to use Hibernate in OSGi many year ago (too many issues
that we lost confidence and moved to gemini + eclipselink). So,
I'm in
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span id="result_box" class="short_text" lang="en"><span
class="hps">skeptical</span></span> with its use in
Drools/JBPM 6, too.<br>
<br>
One solution would be the use of JDK's ServiceLoader api [3] and
the SPI spec in osgi side, but I have doubts that the team would
buy for this route... :)<br>
<br>
anyway, good luck and let us know about your team experiments.<br>
<br>
<br>
[1] - <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/master/kie-api/src/main/java/org/kie/api/KieServices.java#L165">https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/master/kie-api/src/main/java/org/kie/api/KieServices.java#L165</a>
<br>
[2] -
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://keheliya.blogspot.com.br/2013/02/use-of-dynamicimport-package-in-osgi.html">http://keheliya.blogspot.com.br/2013/02/use-of-dynamicimport-package-in-osgi.html</a><br>
[3] -
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://docs.oracle.com/javase/tutorial/ext/basics/spi.html#the-serviceloader-class">http://docs.oracle.com/javase/tutorial/ext/basics/spi.html#the-serviceloader-class</a>)<br>
<br>
best regards,<br>
<br>
Cristiano<br>
<br>
On 16/12/13 10:10, John Shooab wrote:<br>
</div>
<blockquote cite="mid:52AEFBD6.3040505@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Mauricio,<br>
<br>
I could see that many issues were resolved in Drools and JBPM
Jira, that is really good.<br>
<br>
The system environment where we plan to use JBPM is Equinox.
So, what concerned we most are the issues that wasn't raised
yet related running 6.x into OSGi. <br>
<br>
In one entire day one of my team members wasn't able to make
it run. I can't specify the problems right now because he got
out for vacation without pass me the report file. But seems
that it was related to classloading issues... <br>
<br>
I asked to someone to repeat his procedure this week again and
we will raise the issues, if necessary...<br>
<br>
regards,<br>
<br>
John<br>
<br>
On 16/12/13 09:22, Mauricio Salatino wrote:<br>
</div>
<blockquote
cite="mid:CANzbnyXSQoL=GLYvCOtDDCSV5aBa43i65aJn0KGQh3hpkNa2Vg@mail.gmail.com"
type="cite">
<div dir="ltr">HI John,
<div>If you can highlight which issues that you see there
are important to you please let us know. We are still
cleaning Jira for the last release so some of them are
already fixed or not relevant.</div>
<div>Cheers</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Dec 16, 2013 at 1:15 PM,
John Shooab <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jshooab@gmail.com" target="_blank">jshooab@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Alexandre,<br>
<br>
looking the number of issues since 6.0.0.Final at Jira,
for us seems<br>
that the release of Drools and Jbpm 6.0.0.Final.<br>
was a kind precipitated...<br>
<br>
We decided to postpone our prototype with 6.0.x for
while...<br>
<br>
thanks anyway,<br>
<br>
John<br>
<div class="HOEnZb">
<div class="h5"><br>
On 14/12/13 09:33, Alexandre Porcelli wrote:<br>
> Binaries were released, but we're still working
on communication (new web site, new tutorials,
videos, etc...)<br>
><br>
> But if you check <a moz-do-not-send="true"
href="http://www.jboss.org/jbpm" target="_blank">http://www.jboss.org/jbpm</a>
Documentation or Downloads sections there are
references to new release.<br>
><br>
><br>
> Regards,<br>
> ---<br>
> Alexandre Porcelli<br>
> Principal Software Engineer<br>
> Red Hat Business Systems and Intelligence Group<br>
><br>
><br>
> On Dec 13, 2013, at 6:38 PM, John Shooab <<a
moz-do-not-send="true"
href="mailto:jshooab@gmail.com">jshooab@gmail.com</a>>
wrote:<br>
><br>
>> Hello,<br>
>><br>
>> I am in charge to investigate new JBPM and
Drools 6 status.<br>
>><br>
>> I should say that I'm kind confuse.<br>
>><br>
>> Looking at maven central, already have
6.0.0.Final artifacts: <a moz-do-not-send="true"
href="http://search.maven.org/#artifactdetails%7Corg.jbpm%7Cjbpm%7C6.0.0.Final%7Cpom"
target="_blank">http://search.maven.org/#artifactdetails%7Corg.jbpm%7Cjbpm%7C6.0.0.Final%7Cpom</a><br>
>><br>
>> But looking at <a moz-do-not-send="true"
href="http://www.jboss.org/jbpm/" target="_blank">http://www.jboss.org/jbpm/</a>
there are any reference to 6.0.0 !<br>
>><br>
>><br>
>> looking at jira here (<a
moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBPM"
target="_blank">https://issues.jboss.org/browse/JBPM</a>)
I could see the 6.0.0.Final was release, but there
are 3 different versions:jBPM 6.1.0.Final, jBPM
6.0.1.Final and jBPM 6.x !!!<br>
>><br>
>> could someone explain me that ?<br>
>><br>
>> which version should I track in jira? which
source branch is the one that I should clone if I
need to see the examples?<br>
>><br>
>> thanks,<br>
>><br>
>> John.<br>
>>
_______________________________________________<br>
>> jbpm-dev mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
>> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbpm-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
><br>
<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbpm-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr"> - MyJourney @ <a moz-do-not-send="true"
href="http://salaboy.wordpress.com" target="_blank">http://salaboy.com</a>
<div> - Co-Founder @ <a moz-do-not-send="true"
href="http://www.jugargentina.org" target="_blank">http://www.jugargentina.org</a><br>
- Co-Founder @ <a moz-do-not-send="true"
href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br>
<br>
- Salatino "Salaboy" Mauricio -</div>
</div>
</div>
</blockquote>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbpm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbpm-dev">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a></pre>
</blockquote>
<br>
</body>
</html>