<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.5945" name=GENERATOR>
<STYLE>@font-face {
font-family: 宋体;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana color=#000080 size=2>Hi Andrea,</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>Export service is much easier than handle the
persistence layer.</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>Hibernate is truely hard to integrate into OSGi
environment. Since it just store the classname as String and initialize
instance everytime. I don't know other JPA framework could handle
this.</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>And in the jBPM 4, there is still some classloader
issue for running on OSGi environment. Or Maybe we should provide an
OSGi platform with jbpm as a system package. So we needn't worry about the
classloader issues.</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>regards</FONT></DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#c0c0c0 size=2>2010-05-27 </FONT></DIV><FONT
face=Verdana color=#000080 size=2>
<HR style="WIDTH: 100px" align=left color=#b5c4df SIZE=1>
</FONT>
<DIV><FONT face=Verdana color=#c0c0c0 size=2><SPAN>
<DIV>
<DIV><FONT face=Verdana size=2></FONT>Xu Hui Sheng</DIV>
<DIV>WebSite: <A
href="http://www.family168.com/">http://www.family168.com/</A></DIV></DIV></SPAN></FONT></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT face=Verdana size=2><STRONG>发件人：</STRONG> Andrea Zoppello
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间：</STRONG> 2010-05-27 16:13:24
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人：</STRONG> jbpm-dev </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送：</STRONG> </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题：</STRONG> Re: [jbpm-dev] Proposal for
jBPM5 first release </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>
<DIV>Hi Kris,</DIV>
<DIV></DIV>
<DIV>I'am a jBPM 3 and ( maybe i'm wrong ) i've always considered jBPM as a </DIV>
<DIV>"the process engine" and drools as "the rule engine" and</DIV>
<DIV>in myprojects i've try to keep it separated, in my typical use case i've </DIV>
<DIV>used mainly jBPM and i've implemented some custom handler powered by</DIV>
<DIV>drools to inject in my processes the ability to take different flow </DIV>
<DIV>according to business rule for which rules are the right solution.</DIV>
<DIV></DIV>
<DIV>So talking about an OSGi integration, i really means a deep integration </DIV>
<DIV>within JBPM. In particular:</DIV>
<DIV></DIV>
<DIV>1) Be able to expose jBPM API throuhg OSGi services</DIV>
<DIV>2) Be able to use OSGi services within jBPM</DIV>
<DIV>3) Be more indepent by persistence layer ( hibernate could be </DIV>
<DIV>problematic within OSGi.... )</DIV>
<DIV></DIV>
<DIV>In my current project ( www.spagic3.org ) i've just solved 1) and 2) ant </DIV>
<DIV>it was not so easy...</DIV>
<DIV>For the 3) point the only solution i've found quite know it to keep jbp, </DIV>
<DIV>hibernate and all the</DIV>
<DIV>dependencies incapsulate in my own bunlde.... and expose through OSGi a </DIV>
<DIV>my custom API interface..</DIV>
<DIV></DIV>
<DIV>Andrea</DIV>
<DIV></DIV>
<DIV>Il 26/05/2010 14:17, Kris Verlaenen ha scritto:</DIV>
<DIV>> Andrea,</DIV>
<DIV>></DIV>
<DIV>> This is actually a feature that is currently supported in Drools, so </DIV>
<DIV>> we would like to use the same approach here. So yes, it should be </DIV>
<DIV>> part of the first release. Anyway, it would be useful if you could </DIV>
<DIV>> review the approach taken there to see if it would satisfy your </DIV>
<DIV>> requirements:</DIV>
<DIV>> http://blog.athico.com/2010/01/drools-osgi-ready.html</DIV>
<DIV>></DIV>
<DIV>> Kris</DIV>
<DIV>></DIV>
<DIV>> Andrea Zoppello wrote:</DIV>
<DIV>>> Hi,</DIV>
<DIV>>></DIV>
<DIV>>> Very good map. The only observation i've on this roadmap, is that </DIV>
<DIV>>> unfortunately i've not seen</DIV>
<DIV>>> any plan towards OSGi integration.</DIV>
<DIV>>></DIV>
<DIV>>> This would be a very important feature for me....</DIV>
<DIV>>></DIV>
<DIV>>> Andrea</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Il 25/05/2010 17:06, Kris Verlaenen ha scritto:</DIV>
<DIV>>>> A proposal for the jBPM5 roadmap is presented here:</DIV>
<DIV>>>> http://kverlaen.blogspot.com/2010/05/proposal-for-jbpm5-roadmap.html</DIV>
<DIV>>>></DIV>
<DIV>>>> Feedback welcome !</DIV>
<DIV>>>></DIV>
<DIV>>>> Kris</DIV>
<DIV>>>> _______________________________________________</DIV>
<DIV>>>> jbpm-dev mailing list</DIV>
<DIV>>>> jbpm-dev@lists.jboss.org</DIV>
<DIV>>>> https://lists.jboss.org/mailman/listinfo/jbpm-dev</DIV>
<DIV>>>></DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> jbpm-dev mailing list</DIV>
<DIV>>> jbpm-dev@lists.jboss.org</DIV>
<DIV>>> https://lists.jboss.org/mailman/listinfo/jbpm-dev</DIV>
<DIV>></DIV>
<DIV></DIV>
<DIV>_______________________________________________</DIV>
<DIV>jbpm-dev mailing list</DIV>
<DIV>jbpm-dev@lists.jboss.org</DIV>
<DIV>https://lists.jboss.org/mailman/listinfo/jbpm-dev</DIV></FONT></DIV></BODY></HTML>