And I see the same problems with the dependencies, so I wouldn't
do it.
Jbpm 3 was one jar, the people love it :-)
yes. distro will contain the single jbpm.jar
but heiko is right as well. test cases need to be written using api only. i didn't
consider the jpdl-specific delegation classes yet.
in terms of modules: probably splitting jpdl into jpdl-api and jpdl-impl is the only
option we have.
the alternative is that the jpdl-specific interfaces would be included in the PVM
level api. that is no good. so let's go for the jpdl-api and jpdl-impl modules.
regards, tom.
Bernd Rücker wrote:
Hmm, why not keep it one jpdl jar? Separation is not a big advantage
here,
is it?
And I see the same problems with the dependencies, so I wouldn't do it.
Jbpm 3 was one jar, the people love it :-)
BTW: These discussions should be moved to the forum, or?
-----Ursprüngliche Nachricht-----
Von: Tom Baeyens [mailto:tbaeyens@redhat.com]
Gesendet: Dienstag, 3. Februar 2009 15:36
An: Heiko Braun
Cc: Bernd Rücker; 'dev-jbpm'
Betreff: Re: AW: [jbpm-dev] Published jbpm4 API
Heiko Braun wrote:
> that's not completely true, is it?
> I got the impression that the jpdl api extends the pvm api.
> i.e. the interface org.jbpm.jpdl.ExclusiveHandler is an extension to the
> PVM constructs.
> it's being used in the handler examples
> (org.jbpm.examples.exclusive.handler).
ok i get the point
> something related to that is the required split between API and Impl
jars:
>
https://jira.jboss.org/jira/browse/JBPM-2012
so you mean that also the jpdl module should be get a separate api module
with just a
couple of delegation interfaces.
phew. what a dependency hassle :-(
maybe we should just add the jPDL delegation interfaces to the main api
module...
--
regards, tom.
> /Heiko
>
> On Feb 3, 2009, at 2:31 PM, Tom Baeyens wrote:
>
>> jbpm4 api == pvm api == jpdl4 api
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
--
regards, tom.