| Author |
Message |
nguyen
Member
Joined: 30 Sep 2008
Posts: 17
|
 Posted: Fri Oct 24, 2008 9:11 am |
 |
|
Hi,
I use the petals-se-eip-2.2.1 component in the petals-quickstart-2.2 platform. I would like test the EIP dynamic-router pattern.
The Petals UseEIP Eclipse wizard for the dynamic-router hasn't genered the <eip:dynamic-router-condition> clauses in the SU jbi.xml created. I have to insert the <eip:dynamic-router-condition> conditions manually in the jbi.xml.
But when I deployed and tested the pattern in the Petals sample client, I got the error
| Code: |
Consumes sections for the pattern DynamicRouter]]></faultstring><faultactor>http://exemple.eip.acoss.fr/dynamic-router/</faultactor><detail><stackTrace><![CDATA[org.ow2.petals.component.framework.api.exception.SOAP11FaultServerException: PEtALSCDKException - The Service Unit must define (numberOfConditions+2) Consumes sections for the pattern DynamicRouter
at org.ow2.petals.component.framework.listener.MessageExchangeProcessor.processInOutAsProvider(MessageExchangeProcessor.java:537)
at org.ow2.petals.component.framework.listener.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:421)
at org.ow2.petals.component.framework.listener.MessageExchangeProcessor.process(MessageExchangeProcessor.java:308)
at org.ow2.petals.component.framework.listener.MessageExchangeProcessor.run(MessageExchangeProcessor.java:145)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
]]></stackTrace></detail></soapenv:Fault>
|
This is my SU jbi.xml file
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated JBI descriptor for the PEtALS component "petals-se-eip" (EIP), version 2.3 -->
<jbi:jbi version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:eip="http://petals.ow2.org/components/eip/version-2.3"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:generatedNs="http://exemple.eip.acoss.fr/dynamic-router/">
<!-- Import a Service into PEtALS or Expose a PEtALS Service => use a BC. -->
<jbi:services binding-component="false">
<!-- Import a Service into PEtALS => provides a Service. -->
<jbi:provides
interface-name="generatedNs:dynamic-router"
service-name="generatedNs:dynamic-routerService"
endpoint-name="dynamic-routerServiceEndpoint">
<!-- CDK specific elements -->
<petalsCDK:wsdl>dynamic-router.wsdl</petalsCDK:wsdl>
<!-- Component specific elements -->
<eip:eip>dynamic-router</eip:eip>
<eip:dynamic-router-condition>count(//*)>0</eip:dynamic-router-condition>
</jbi:provides>
<!-- Consumed project 1 ( Service to Test ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC17"
service-name="iConsumeNsPrefix:XC17Service"
endpoint-name="xc17"
xmlns:iConsumeNsPrefix="http://xc17.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
<!-- Consumed project 2 ( condition = count(//*)>0 ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC18"
service-name="iConsumeNsPrefix:XC18Service"
endpoint-name="xc18"
xmlns:iConsumeNsPrefix="http://xc18.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
<!-- Consumed project 3 ( Default ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC21"
service-name="iConsumeNsPrefix:XC21Service"
endpoint-name="xc21"
xmlns:iConsumeNsPrefix="http://xc21.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
</jbi:services>
</jbi:jbi>
|
Thank in advance |
|
| Back to top |
|
 |
rnaudin
Member
![]()
Joined: 17 Jul 2008
Posts: 20
|
| Posted: Tue Oct 28, 2008 10:15 am |
|
|
Hello,
If you check the XML schema embedded in the EIp component, you will see that the expected parameter is 'dynamicrouter-condition' not 'dynamic-router-condition'.
Maybe the plugin doesn't generate the good Su for the component EIP 2.2.1.
Regards,
/Roland |
|
| Back to top |
|
|
alouis
Member
Joined: 04 Aug 2008
Posts: 15
|
| Posted: Tue Oct 28, 2008 10:39 am |
|
|
maybe the parameter name has changed in the component without reporting
the modification in the Eclipse plugin...
Le Oct 28, 2008 10:15 AM, rnaudin <petals-components@ebmwebsourcing.com>
a écrit :
| Quote: | Hello,
If you check the XML schema embedded in the EIp component, you will
see that the expected parameter is 'dynamicrouter-condition' not
'dynamic-router-condition'.
Maybe the plugin doesn't generate the good Su for the component EIP
2.2.1.
Regards,
/Roland
|
|
|
| Back to top |
|
|
nguyen
Member
Joined: 30 Sep 2008
Posts: 17
|
| Posted: Tue Oct 28, 2008 10:45 am |
|
|
Hi,
As the EIP plugin doesn't genered automatically the conditions in SU, I have to insert it manually by referencing in the document petals-se-eip-2.2-en.pdf, page 14, where there is the condition dynamic router syntaxe for example :
<eip:dynamic-router-condition>sum(/items/item/value) > 100</eip:dynamic-router-condition>
<eip:dynamic-router-condition>name(/*)='coucou'</eip:dynamic-router-condition>
Maybe the document isn't updated for the current version of EIP component.
Thank very much.
 |
|
| Back to top |
|
|
vzurczak
Member
Joined: 17 Jul 2008
Posts: 35
Location: Grenoble
|
| Posted: Tue Oct 28, 2008 12:14 pm |
|
|
Hi.
| nguyen wrote: | This is my SU jbi.xml file
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated JBI descriptor for the PEtALS component "petals-se-eip" (EIP), version 2.3 -->
<jbi:jbi version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:eip="http://petals.ow2.org/components/eip/version-2.3"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:generatedNs="http://exemple.eip.acoss.fr/dynamic-router/">
<!-- Import a Service into PEtALS or Expose a PEtALS Service => use a BC. -->
<jbi:services binding-component="false">
<!-- Import a Service into PEtALS => provides a Service. -->
<jbi:provides
interface-name="generatedNs:dynamic-router"
service-name="generatedNs:dynamic-routerService"
endpoint-name="dynamic-routerServiceEndpoint">
<!-- CDK specific elements -->
<petalsCDK:wsdl>dynamic-router.wsdl</petalsCDK:wsdl>
<!-- Component specific elements -->
<eip:eip>dynamic-router</eip:eip>
<eip:dynamic-router-condition>count(//*)>0</eip:dynamic-router-condition>
</jbi:provides>
<!-- Consumed project 1 ( Service to Test ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC17"
service-name="iConsumeNsPrefix:XC17Service"
endpoint-name="xc17"
xmlns:iConsumeNsPrefix="http://xc17.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
<!-- Consumed project 2 ( condition = count(//*)>0 ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC18"
service-name="iConsumeNsPrefix:XC18Service"
endpoint-name="xc18"
xmlns:iConsumeNsPrefix="http://xc18.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
<!-- Consumed project 3 ( Default ) -->
<jbi:consumes
interface-name="iConsumeNsPrefix:XC21"
service-name="iConsumeNsPrefix:XC21Service"
endpoint-name="xc21"
xmlns:iConsumeNsPrefix="http://xc21.snv2sxml.technical.services.esb.cirso.fr/1.0">
<!-- CK specific fields for this consume -->
<petalsCDK:mep>InOut</petalsCDK:mep>
</jbi:consumes>
</jbi:services>
</jbi:jbi>
|
|
I guess this one was generated by the plug-ins.
And you're right, it is weird that the conditions were not written in the provide part.
As Adrien said, it is possible that the component has been updated and not the associated plug-in.
In particular, if the "condition" element associated to this pattern was renamed, it could explain these errors. 
I'm going to get the last XSDs from the component and make corrections if necessary. |
|
| Back to top |
|
|
vzurczak
Member
Joined: 17 Jul 2008
Posts: 35
Location: Grenoble
|
| Posted: Tue Oct 28, 2008 1:35 pm |
|
|
OK.
I fixed it in the trunk. The condition renaming in 2.3 messed it up all.
This change went through my check out last time.
Since the version 2.3 is still in the trunk, I hope this is not a too much annoying problem to wait until the next plug-ins release. |
|
| Back to top |
|
|
fgardes
Member
Joined: 27 Jun 2008
Posts: 38
Location: Tolosa
|
| Posted: Mon Nov 03, 2008 3:34 pm |
|
|
I will add an splitter pattern as soon. It will be under a "real" 2.3 wich will be released, and different of the 2.2 so  |
|
| Back to top |
|
|
vzurczak
Member
Joined: 17 Jul 2008
Posts: 35
Location: Grenoble
|
| Posted: Mon Nov 03, 2008 4:22 pm |
|
|
| fgardes wrote: | | I will add an splitter pattern as soon. It will be under a "real" 2.3 wich will be released, and different of the 2.2 so |
I guess this change will be reported in the XSD files of the EIP component (added into the available patterns).
If you can also add these XSDs in the EIP plug-in, that would be nice. That will be enough for the plug-in to show this new pattern.
Then, if your pattern has a specific behavior, we will see together to integrate this into the plug-in (e.g. manage conditions as it works with the dynamic-router). |
|
| Back to top |
|
|
fgardes
Member
Joined: 27 Jun 2008
Posts: 38
Location: Tolosa
|
| Posted: Mon Nov 03, 2008 4:29 pm |
|
|
All right. As soon as I 'll finished the splitter pattern EIP documentation, I 'll see how to extend the EIP eclipse plugin. It has got "specific behaviors" which will be detailed into the docs, so it will be more efficient that I call you when it will be finished.
Thanks! |
|
| Back to top |
|
|
|
