Re: [jboss-dev-forums] [jBPM Development] - JBPM-2537
by Maciej Swiderski
Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion
"JBPM-2537"
To view the discussion, visit: http://community.jboss.org/message/543910#543910
--------------------------------------------------------------
Looks really good. Moreover good to follow standard, especially while bearing in mind v5 that will be based on WS-HT.
If it comes to your question about distinguishing between manual cancellation and timer I would say that it can be important from business point of view.
Since expiration usually means some kind of escalation meaning task (or information that should be gathered within this step) are important for the process and cancellation could be done just to skip certain types of steps in the process and by doing that process can have inconsistent state - no one has completed the task and it was not escalated so some of the information can be missing. Especially that signal can be made by providing any transition from all available.
Perhaps an alternative to have different states/cancellation methods would be to add a task comment while signaling in skip mode?! At least some information why the task was skipped.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/543910#543910]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
Re: [jboss-dev-forums] [JBoss ESB Development] - Camel integration input requested
by David Ward
David Ward [http://community.jboss.org/people/dward] replied to the discussion
"Camel integration input requested"
To view the discussion, visit: http://community.jboss.org/message/543885#543885
--------------------------------------------------------------
Okay, a bit more discussion on the team, and this is looking like the new direction. You would have several options, including some shorthand:
<listeners>
<camel-gateway name="..." from="foo://bar" />
</listeners>
<listeners>
<camel-gateway name="...">
<from uri="foo://bar" />
<from uri="foo://bar" />
</camel-gateway>
</listeners>
<listeners>
<camel-gateway name="..." from="foo://bar">
<from uri="foo://bar" />
<from uri="foo://bar" />
</camel-gateway>
</listeners>
<providers>
<camel-provider name="...">
<camel-bus busid="xxx" from="foo://bar">
</camel-provider>
</providers>
<services>
<listeners>
<camel-gateway name="..." busidref="xxx" />
</listeners>
<actions>...</actions>
</services>
<providers>
<camel-provider name="...">
<camel-bus busid="xxx">
<from uri="foo://bar" />
<from uri="foo://bar" />
</camel-bus>
</camel-provider>
</providers>
<services>
<listeners>
<camel-gateway name="..." busidref="xxx" />
</listeners>
<actions>...</actions>
</services>
You get the idea. ;) Basically, all "from's" associated with a gateway would be combined into a single CamelContext. If you specify multiple camel-gateways in the listeners section that refer to the same bus, then the routes defined in the <camel-bus> section are created separately in each CamelContext - again, one per gateway.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/543885#543885]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
Re: [jboss-dev-forums] [JBoss ESB Development] - Camel integration input requested
by David Ward
David Ward [http://community.jboss.org/people/dward] replied to the discussion
"Camel integration input requested"
To view the discussion, visit: http://community.jboss.org/message/543868#543868
--------------------------------------------------------------
I'm thinking that it would still be nice to have a <providers> section too, so that we can have multiple routes in one CamelContext. Since, if you do this:
<listeners>
<camel-gateway from="file://xxx" />
<camel-gateway from="ftp://yyy" />
</listeners>
, we would have to create 2 different CamelContexts, one for each gateway. However, if we do this:
<providers>
<camel-provider name="...">
<camel-bus busid="foo">
<from uri="file://xxx" />
<from uri="ftp://yyy" />
</camel-bus>
</camel-provider>
</providers>
<services>
<listeners>
<camel-gateway name="..." busidref="foo" />
</listeners>
<actions>...</actions>
</services>
, then we can have multiple Camel routes as part of a single CamelContext - on per bus. I also like using the <from> tag in the <camel-bus> section, as it is familiar to current Camel users. The only caveat - for 4.x, anyway - is that ONLY the <from> tag would be supported by us.
What do you think? Should we also allow the <camel-gateway from="" /> shorthand? I wonder if we can define in XSD that you use either the busidref attribute, OR the from attribute? Or maybe we let them do both, and all "from's" get put into the same CamelContext?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/543868#543868]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
Re: [jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Ales Justin
Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/543855#543855
--------------------------------------------------------------
> - regarding jars in the lib of the server, they should never be treated as BDAs, right? (I know we discussed about this, but I'm so deep in so many details that now I got confused :-) )
No, I think they should -- but, only if they have beans.xml in their metadata location.
> - the Deployment.loadBeanDeploymentArchive(Class<?> beanClass) method should search only for the archives included in the deployment, or for all archives visible from the deployment? A small example to ilustrate my question: if there are two separate ejb-jars deployed, A and B, and I invoke loadBeanDeploymentArchive at the deployment that represents ejb-jar A, using a class that is in ejb-jar B as parameter, should the deployment be able to find it?
I think yes, you should be able to "jump" from deployement to deployment if they can "see" each other.
It would be your (hidden) impl that would easily allow this; e.g. keeping proper overall structure with easy-to-access mapping.
> - this one is still about loadBeanDeploymentArchive method, and I think Ales knows the answer. Since the parameter of this method is a class, I don't need to look for an archive that contains a class with the same name. I could use instead the ClassLoader to determine the module and, hence, to find the corresponding archive. Should I do it this way?
Yes, more or less.
It depends on the impl details how you're gonna map the overall structure.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/543855#543855]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years