[JBoss jBPM] - Re: jpdl and sca tuscany integration - any?
by Radu3000
Tom,
Thanks for your reply.
In the end it boils down to the age old question: what is first chicken or the egg? Process importing components or components importing process.
Let's take the approach of process importing components - chicken first. Given the current process fragment:
<node name="Parse service request">
| <action class="com.bofa.crme.gps.servlet.RequestParserImpl"/>
| <transition name="next" to="Transform GCIB request to WCC request"/>
| </node>
I could change it to:
import ..\sca\ConsumerFacade.composite
| ...
| <node name="Parse service request">
| <action sca-component-reference="RequestParser"/>
| <transition name="next" to="Transform GCIB request to WCC request"/>
| </node>
And done! Isn't this a cleaner separation of process and assmbly responsibility? With a bit more work to integrate an sca tuscany runtime and jpdl runtime - there is so much to gain! JPDL can tap into any (almost any - sca component types are constantly growing ...) type of components defined in sca. The component impls would also implement ActionHandler - easy right?
The SCA api is straight forward:
// line below can be triggered by the above
| // "import ..\sca\ConsumerFacade.composite" statment
| scaDomain = SCADomain.newInstance("ConsumerFacade.composite");
|
| // line below is triggered when you need the action to be executed
| requestParserService = scaDomain.getService(RequestParserImpl.class, "RequstParserComponent");
So what is left?
1. Change jpdl schema to allow:
<action sca-component-reference="RequestParser"/>
2. Make some room in jpdl api to allow references to scaDomain.getService(...) calls.
I would be glad to contribute some time to the above.
Regards,
Radu Marian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149815#4149815
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149815
18 years, 1 month
[JBoss jBPM] - Re: jpdl and sca tuscany integration - any?
by Radu3000
Tom,
Thanks for your reply.
In the end it boils down to the age old question: what is first chicken or the egg? Process importing components or components importing process.
Let's take the approach of process importing components - chicken first. Given the current process fragment:
I could change it to:
-----------
import ..\sca\ConsumerFacade.composite
...
<action sca-component-reference="RequestParser"/>
-----------
And done! Isn't this a cleaner separation of process and assmbly responsibility? With a bit more work to integrate an sca tuscany runtime and jpdl runtime - there is so much to gain! JPDL can tap into any (almost any - sca component types are constantly growing ...) type of components defined in sca. The component impls would also implement ActionHandler - easy right?
The SCA api is straight forward:
// line below can be triggered by the above
// "import ..\sca\ConsumerFacade.composite" statment
scaDomain = SCADomain.newInstance("ConsumerFacade.composite");
// line below is triggered when you need the action to be executed
requestParserService = scaDomain.getService(RequestParserImpl.class, "RequstParserComponent");
So what is left?
1. Change jpdl schema to allow:
<action sca-component-reference="RequestParser"/>
2. Make some room in jpdl api to allow references to scaDomain.getService(...) calls.
I would be glad to contribute some time to the above.
Regards,
Radu Marian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149814#4149814
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149814
18 years, 1 month
[JBoss Portal] - Re: Implementing portlet-specific help
by Nickerson
Thanks for the suggestion. We had already tried this and it !sort of! works, but not quite. It does pop the help window and the portlet content remains intact but it also replaces the help icon in the title bar with a "CANCEL" icon (and, incidentally, scrambles the title bar a bit, which I think is another bug altogether because we've seen it when we use the normal JBoss portlet help mechanism, no subterfuge required.) The solution we've implemented is to create a "help" portlet and install instances of it on each of the pages where we need more comprehensive explanation. When a user clicks the help button the help window appears (via a processAction call) and no other portlets on the page are disturbed. The help portlet determines the page where its button was clicked and generates the right help content URL.
Steve Bulick
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149812#4149812
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149812
18 years, 1 month
[JBossWS] - Web Service Client
by bsisson
I have found several very good tutorials for creating a web service using annotations (JSR-181). I am struggling however creating a web service client using annotations. I'm working with Eclipse 3.3 and Seam 2.0. I did the old web service client way of creating a project, then generating a web service client from the wsdl which generates the stubs and this works fine. However, I want to be able to do this with annotations instead and am struggling. I have seen examples that use the @WebServiceRefs annotations but no complete explenation. I would expect if I use annotations that I will not have to generate the stubs from the WSDL but have no clarity. If you can point me to a good tutorial that would be great? If you could clarify whether I need to generate the stubs from the WSDL that would be helpful as well?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149807#4149807
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149807
18 years, 1 month