Petals Forum (ESB, SOA, Governance)

Petals ESB :: Petals ESB Starter - Day 1

Mathieu — Fri, 03 Sep 2010 12:42:47 GMT

Author: Mathieu
Subject: Petals ESB Starter - Day 1
Posted: Fri Sep 03, 2010 1:42 pm (GMT 1)

Created for a future task.
_________________
Petals ESB, the open source ESB based on standards, and distributed along multiple servers.

Petals ESB :: RE: service with multiple portType

om10 — Fri, 03 Sep 2010 09:10:37 GMT

Author: om10
Posted: Fri Sep 03, 2010 10:10 am (GMT 1)

now i have only the second error when i validate all the project:

Code:

The errors below were detected when validating the file "kpi1.0.xsd" via the file "jbi.xml". In most cases these errors can be detected by validating "kpi1.0.xsd" directly. However it is possible that errors will only occur when kpi1.0.xsd is validated in the context of jbi.xml.

Petals ESB :: RE: service with multiple portType

om10 — Fri, 03 Sep 2010 08:45:07 GMT

Author: om10
Posted: Fri Sep 03, 2010 9:45 am (GMT 1)

yes the portType in Configurable.wsdl is "Configurable"

i validate in PetalsStudio the 3 imported interfaces, no problem but when i validate WebCrawling.wsdl i got this error:

Code:

The errors below were detected when validating the file "Configurable.wsdl" via the file "WebCrawling.wsdl". In most cases these errors can be detected by validating "Configurable.wsdl" directly. However it is possible that errors will only occur when Configurable.wsdl is validated in the context of WebCrawling.wsdl.

and when i validate jbi i got this error:

Code:

Petals ESB :: RE: service with multiple portType

vzurczak — Fri, 03 Sep 2010 08:13:22 GMT

Author: vzurczak
Posted: Fri Sep 03, 2010 9:13 am (GMT 1)

I assume the port type name in the Configurable.wsdl file is "Configurable", as you put it in the jbi.xml.
In which case it may be a bug. We should investigate it.

Questions:
Is your WSDL successfully validated in the studio? (Right-click it and select Validate).
Does the Petals studio mark any error in the project when it validates it?

Petals ESB :: RE: service with multiple portType

om10 — Fri, 03 Sep 2010 07:56:00 GMT

Author: om10
Posted: Fri Sep 03, 2010 8:56 am (GMT 1)

my WSDL:

==================

Code:

==================

my jbi

Code:

<jbi:jbi version="1.0"
...
<jbi:services binding-component="true">
<jbi:provides interface-name="interfaceNs:Configurable"
service-name="serviceNs:WebCrawlingService"
endpoint-name="ConfigurablePort">

<petalsCDK:wsdl>WebCrawling.wsdl</petalsCDK:wsdl>
...

thanks

Petals ESB :: RE: service with multiple portType

vzurczak — Thu, 02 Sep 2010 10:40:56 GMT

Author: vzurczak
Posted: Thu Sep 02, 2010 11:40 am (GMT 1)

Hi,

Can you post your WSDL here?

Petals ESB :: service with multiple portType

om10 — Thu, 02 Sep 2010 10:38:16 GMT

Author: om10
Subject: service with multiple portType
Posted: Thu Sep 02, 2010 11:38 am (GMT 1)

Hi all,

I'm using petals-platform 3.0.5
I have one service with 2 portType, i created a jbi for the first endpoint. When i deployed the corresponding sa i got the following error:

Failed to parse the WSDL description bound to the provided service 'MyFisrtPort'
Caused by: SchemaException: WSDL 1.1: The endpoints of this service do not implement the same interface

any idea to resolve this problem ?

thanks

Petals ESB :: RE: Testing the XSLT component

kk — Wed, 01 Sep 2010 16:33:50 GMT

Author: kk
Posted: Wed Sep 01, 2010 5:33 pm (GMT 1)

Great!!!!! it works.
Thank you very much for your quick (and relevant) answer

Petals ESB :: RE: Testing the XSLT component

vzurczak — Wed, 01 Sep 2010 15:59:51 GMT

Author: vzurczak
Posted: Wed Sep 01, 2010 4:59 pm (GMT 1)

Hi,

I guess your error comes from the SOAP configuration.
In your consume, you must have put a wrong MEP. It should be InOut.

In fact, your SOAP consume should look like:

Code:

...


<jbi:consumes
interface-name="..."
service-name="..."
endpoint-name="...">


<petalsCDK:timeout>30000</petalsCDK:timeout>
<petalsCDK:operation xmlns:gen0="http://petals.ow2.org/components/xslt/version-2">gen0:transform</petalsCDK:operation>
<petalsCDK:mep>InOut</petalsCDK:mep>


<soap:address>Xslt</soap:address>
<soap:remove-root>false</soap:remove-root>
<soap:mode>SOAP</soap:mode>
<soap:rest-add-namespace-prefix>soapbc</soap:rest-add-namespace-prefix>
<soap:enable-http-transport>true</soap:enable-http-transport>
<soap:enable-jms-transport>false</soap:enable-jms-transport>
</jbi:consumes>

Notice that the next version of the SOAP BC won't need this information.
The MEP will be found out correctly from the request, which is not the case in previously released versions.
And the operations are already found out correctly.
Putting the right MEP should fix your error.

Besides, and independently of your problem, you should know that at the origin, the XSLT services were not designed to be described by a WSDL.
The one which is generated by the studio aims at simplifying its creation. But in practice, the WSDL and the XSL style sheet are tightly coupled.
You may have to update the name of the root elements in the WSDL, depending on the content of your XSL style sheet.
This is important if you plan to create Web Service clients behind. If you directly work with XML messages, that should be OK though.

Petals ESB :: Testing the XSLT component

kk — Wed, 01 Sep 2010 15:22:23 GMT

Author: kk
Subject: Testing the XSLT component
Posted: Wed Sep 01, 2010 4:22 pm (GMT 1)

Hi all,
I am a petals's neophyte and I would like to test the XSLT se component

So, I created a SA XSLT provide including my xsl file and this WSDL :

Code:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="XsltService" targetNamespace="http://petals.ow2.org/components/xslt/version-2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://petals.ow2.org/components/xslt/version-2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">
<wsdl:types>
<xsd:schema elementFormDefault="qualified" targetNamespace="http://petals.ow2.org/components/xslt/version-2">
<xsd:element name="request" type="xsd:anyType"/>
<xsd:element name="response" type="xsd:anyType"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="transformRequest">
<wsdl:part name="transformRequest" element="tns:request">
</wsdl:part>
</wsdl:message>
<wsdl:message name="transformResponse">
<wsdl:part name="transformResponse" element="tns:response">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="XsltInterface">
<wsdl:operation name="transform">
<wsdl:input message="tns:transformRequest">
</wsdl:input>
<wsdl:output message="tns:transformResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PetalsXSLTBinding" type="tns:XsltInterface">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="transform">
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="transcoService">
<wsdl:port name="transcoServiceEndpoint" binding="tns:PetalsXSLTBinding">
<soap:address location="http://localhost:9090/transcoServiceEndpoint"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Then, I created a "SA SOAP consume".

But when testing with SOAPUI I had this exception :

Code:

org.apache.axis2.AxisFault: Server
at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.processJBIResponse(RequestProcessor.java:150)
at org.ow2.petals.binding.soap.listener.incoming.SOAPProcessor.process(SOAPProcessor.java:134)
at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:173)
at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:123)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:194)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
Caused by: java.lang.Exception: Operation '{http://petals.ow2.org/components/xslt/version-2}transform' must use the pattern 'http://www.w3.org/2004/08/wsdl/in-out'
at org.ow2.petals.se.xslt.listener.JBIListener.validateExchange(JBIListener.java:72)
at org.ow2.petals.se.xslt.listener.JBIListener.onJBIMessage(JBIListener.java:113)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOptionalOutAsProvider(MessageExchangeProcessor.java:518)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:381)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:242)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:176)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Any idea, please?

Thanks in advance,

KK

Petals View :: RE: How the View groups flows steps ?

Jérémie Doucy — Mon, 30 Aug 2010 15:47:06 GMT

Author: Jérémie Doucy
Posted: Mon Aug 30, 2010 4:47 pm (GMT 1)

I activate notifications on BC-SOAP. But I use a home made bpel SE (based on the old orchestra one) until yours works fine.
So notifications are send only by BC-SOAP but that's BPEL-SE which calls endpoints deployed on BC-SOAP.
_________________
Information Processing, Control and Cognition (IPCC)
EADS Defence and Security Systems
http://weblab-project.org

Petals View :: RE: How the View groups flows steps ?

sandraT — Mon, 30 Aug 2010 12:36:24 GMT

Author: sandraT
Posted: Mon Aug 30, 2010 1:36 pm (GMT 1)

Hi,
I need more informations to help you.
What are the components present in Petals ESB and which notify.
You are probably missing a step in your flow, which prevents the correlation.

Sandra

Petals View :: RE: How the View groups flows steps ?

Jérémie Doucy — Mon, 30 Aug 2010 08:47:17 GMT

Author: Jérémie Doucy
Posted: Mon Aug 30, 2010 9:47 am (GMT 1)

If the "group by" thing is done using the exchange id, is there a way to "group by" some xpath parameter ?

Thanks in advance.
_________________
Information Processing, Control and Cognition (IPCC)
EADS Defence and Security Systems
http://weblab-project.org

Petals View :: RE: How the View groups flows steps ?

Jérémie Doucy — Thu, 26 Aug 2010 16:52:40 GMT

Author: Jérémie Doucy
Posted: Thu Aug 26, 2010 5:52 pm (GMT 1)

I think I foud why, maybe it's because my exchange id is changing during the flow ?
_________________
Information Processing, Control and Cognition (IPCC)
EADS Defence and Security Systems
http://weblab-project.org

Petals View :: How the View groups flows steps ?

Jérémie Doucy — Thu, 26 Aug 2010 16:50:01 GMT

Author: Jérémie Doucy
Subject: How the View groups flows steps ?
Posted: Thu Aug 26, 2010 5:50 pm (GMT 1)

Hi,
I try to create a flow with 3 steps.
So I configured each SU_KPI with the same processType, but in the view it creates a new flow for each step.
How can I create one flow with 3 steps ?

Thanks in advance.
_________________
Information Processing, Control and Cognition (IPCC)
EADS Defence and Security Systems
http://weblab-project.org

Discussions and general questions :: RE: Technical information of component for monitoring

cdeneux — Tue, 24 Aug 2010 04:50:44 GMT

Author: cdeneux
Subject: Technical information of component for monitoring
Posted: Tue Aug 24, 2010 5:50 am (GMT 1)

Le lundi 23 ao�t 2010 � 16:32 +0200, rnaudin a �crit :

Quote:

[Arrow] About incoming and outcoming processing time, there already time handled in the Router Monitor.
Once the queues evolution done in the NMR, the time spend in NMR queue can be too handled by the Router Monitor. So you will have all the time spent at each step of an exchange life hold in the Router Monitor.
Maybe BCs can propose a transfer processing time? it's up to the BCs implementors, as specific data for specific component will be possible.

Yes, it's a specific data. Have we no way to get it at the kernel level, perhaps with an extension to the JBI API ? If the component doen't support this API extension the feature is deactivated.

Quote:

[Arrow] Number of established connection, good point, as we spoke to pool the connections when possible in all the components, a pool with only 'dynamic' elements (no permanent element).
BTW, what is the difference between

Quote:

connection status (connected, disconnected)

and

Quote:

number of established connections

Yes, they are close and linked. "Number of established connections" is more precise than the other one:
connection status = (number of established connection > 1)
We should keep "Number of established connections"

Quote:

[Arrow] Differ the fault and error, ok, not to hard.

[Arrow] Message per endpoint. I was speaking by SU, as a SU is the administrable element, but we can 'fine grained' to endpoint. We must know what SU is bound to what endpoint in that case.
Although, there is endpoints that can be activated directly by component, so not bound to an SU.
Just a litlle more complex to handle in the CDK.

This can permit to verify the HA at service level.

--Posted via petals mailing-list--