Nabble - Petals Users

Re: Re: Re: Re: Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-28T23:21:37Z

Hi Vincent,

No I think that it is the right place to announce tools around petals but not the one for support. As you have mentioned in your first mail, the support channel for the eclipse plugin is the PEtALS@EBMWebsourcing forum.

On Sat, Sep 27, 2008 at 7:27 PM, VZ <vincent.zurczak@...> wrote:

Hi.

Christophe Hamerling - eBM WebSourcing a écrit :

This is not the valid mailing list for the Eclipse plugin since it is not (for now) hosted at OW2. You have to post on the forum since there is no mailing list.

That's my fault. I was the first to use it to promote the new version of the plug-ins. I gave the wrong example...
Like Christophe said, the suport for these tools is made on the forum.

BTW, this site.xml contains references to the 1.0.0 plugin...

True. This probably due to the cache of your web browser, which needs to be refreshed. ;)

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Re: Re: Re: Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-27T10:27:43Z

Hi.

Christophe Hamerling - eBM WebSourcing a écrit :
> This is not the valid mailing list for the Eclipse plugin since it is
> not (for now) hosted at OW2. You have to post on the forum since there
> is no mailing list.
That's my fault. I was the first to use it to promote the new version of
the plug-ins. I gave the wrong example...
Like Christophe said, the suport for these tools is made on the forum.

> BTW, this site.xml contains references to the 1.0.0 plugin...
True. This probably due to the cache of your web browser, which needs to
be refreshed. ;)

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Re: Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-27T02:06:56Z

You seem to take into account what I said in good part.
The update site link is now "update".
Thanks for you reactivity.

Richard.

Vincent Zurczak - EBM WebSourcing wrote:

>
>
>
>
>
>
> Hi.
>
> A new version of the PEtALS Eclipse plug-ins is available.
> As a reminder, these plug-ins aims at making the development of SUs and
> SAs for PEtALS easier.
>
> This release comes with several enhancements and bug fixes:
>
>     WSDL import: import all the XML files (XSD, WSDL)
> referenced
> directly or indirectly by the WSDL
>     Project structure: choose between the basic structure
> and a
> Maven structure (+ migration action)
>     XML validation and error markers for jbi.xml files
>     Several improvements about usability and error
> reporting
>     Several bugs corrected
>     New tutorial to create your own plug-in and improved
> documentation
>
>
> More details can be found on the plug-ins'
> topic @ PEtALS' forum .
> Notice also that due to a modification in the plug-ins structure, you
> should uninstall (*) the previous version of the plug-ins you have
> before installing this last version.
> Using the the update site for this migration won't do the job correctly
> (indeed, the former and the new version of the main plug-in will
> co-exist, which is not really clean).
>
> Once again, do not hesitate to post your feedback about the plug-ins
> (the forum fits for that).
> Next updates will probably be announced on the forum rather than on
> this mailing-list...
>
> Regards,
>
>
> Vincent.
>
>
>
> (*) To uninstall the previous versions of the plug-ins, follow these
> steps.
>
> Europa
>
> Help > Software Updates > Manage Configuration
> Select all the PEtALS plug-ins and right-click "uninstall".
> Click yes when you are prompt to restart your Eclipse.
>
>
>
> Ganymede
>
> Help > Software Updates > Installed Software
> Select all the PEtALS plug-ins and click "uninstall".
> Click yes when you are prompt to restart your Eclipse.
>
>
> --
> Vincent Zurczak
> EBM WebSourcing
> +33 (0) 4 76 38 12 16 77
>
>
>
>
>
> --
> You receive this message as a subscriber of the petals-users@...
> mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
View this message in context: http://www.nabble.com/Version-1.0-of-the-PEtALS-Eclipse-plug-ins-tp19666499p19701024.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Re: Re: Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-26T02:54:34Z

This is not the valid mailing list for the Eclipse plugin since it is not (for now) hosted at OW2. You have to post on the forum since there is no mailing list.
BTW, this site.xml contains references to the 1.0.0 plugin...

On Fri, Sep 26, 2008 at 11:47 AM, aillet <richard.aillet@...> wrote:

FYI, the new version 1.0 of the PEtALS Eclipse seems not yet available.
If you try the update site
http://dist.ebmwebsourcing.com/eclipse/petals/site.xml, the old version is
always here.

Richard.

Vincent Zurczak - EBM WebSourcing wrote:
>
>
>
>
>
>
> Hi.
>
> A new version of the PEtALS Eclipse plug-ins is available.
> As a reminder, these plug-ins aims at making the development of SUs and
> SAs for PEtALS easier.
>
> This release comes with several enhancements and bug fixes:
>

>     WSDL import: import all the XML files (XSD, WSDL)

> referenced
> directly or indirectly by the WSDL

>     Project structure: choose between the basic structure

> and a
> Maven structure (+ migration action)

>     XML validation and error markers for jbi.xml files
>     Several improvements about usability and error
> reporting
>     Several bugs corrected
>     New tutorial to create your own plug-in and improved

> documentation
>
>
> More details can be found on the plug-ins'
> topic @ PEtALS' forum .
> Notice also that due to a modification in the plug-ins structure, you
> should uninstall (*) the previous version of the plug-ins you have
> before installing this last version.
> Using the the update site for this migration won't do the job correctly
> (indeed, the former and the new version of the main plug-in will
> co-exist, which is not really clean).
>
> Once again, do not hesitate to post your feedback about the plug-ins
> (the forum fits for that).
> Next updates will probably be announced on the forum rather than on
> this mailing-list...
>
> Regards,
>

>                 

> Vincent.
>
>
>
> (*) To uninstall the previous versions of the plug-ins, follow these
> steps.
>
> Europa
>

> Help > Software Updates > Manage Configuration

> Select all the PEtALS plug-ins and right-click "uninstall".
> Click yes when you are prompt to restart your Eclipse.
>
>
>
> Ganymede
>

> Help > Software Updates > Installed Software

> Select all the PEtALS plug-ins and click "uninstall".
> Click yes when you are prompt to restart your Eclipse.
>
>
> --
> Vincent Zurczak
> EBM WebSourcing
> +33 (0) 4 76 38 12 16 77
>
>
>
>
>

> --
> You receive this message as a subscriber of the petals-users@...
> mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
View this message in context: http://www.nabble.com/Version-1.0-of-the-PEtALS-Eclipse-plug-ins-tp19666499p19685442.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

Re: Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-26T02:47:20Z

FYI, the new version 1.0 of the PEtALS Eclipse seems not yet available.
If you try the update site http://dist.ebmwebsourcing.com/eclipse/petals/site.xml, the old version is always here.

Richard.

Vincent Zurczak - EBM WebSourcing wrote:

Hi.

A new version of the PEtALS Eclipse plug-ins is available.
As a reminder, these plug-ins aims at making the development of SUs and
SAs for PEtALS easier.

This release comes with several enhancements and bug fixes:

    WSDL import: import all the XML files (XSD, WSDL) referenced
directly or indirectly by the WSDL
    Project structure: choose between the basic structure and a
Maven structure (+ migration action)
    XML validation and error markers for jbi.xml files
    Several improvements about usability and error reporting
    Several bugs corrected
    New tutorial to create your own plug-in and improved
documentation

More details can be found on the plug-ins'
topic @ PEtALS' forum .
Notice also that due to a modification in the plug-ins structure, you
should uninstall (*) the previous version of the plug-ins you have
before installing this last version.
Using the the update site for this migration won't do the job correctly
(indeed, the former and the new version of the main plug-in will
co-exist, which is not really clean).

Once again, do not hesitate to post your feedback about the plug-ins
(the forum fits for that).
Next updates will probably be announced on the forum rather than on
this mailing-list...

Regards,

                 Vincent.

(*) To uninstall the previous versions of the plug-ins, follow these
steps.

Europa

Help > Software Updates > Manage Configuration
Select all the PEtALS plug-ins and right-click "uninstall".
Click yes when you are prompt to restart your Eclipse.

Ganymede

Help > Software Updates > Installed Software
Select all the PEtALS plug-ins and click "uninstall".
Click yes when you are prompt to restart your Eclipse.

--
Vincent Zurczak
EBM WebSourcing
+33 (0) 4 76 38 12 16 77

--
You receive this message as a subscriber of the petals-users@ow2.org mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Release petals-se-orchestra v1.0

2008-09-25T05:28:41Z

Hi all,

Welcome to the BPEL component based on Orchestra engine (http://orchestra.ow2.org)!
Component and documentation are available on the components download page : http://petals.ow2.org/download-jbi-components.html
I think that we will provide some demo/tuto in the next weeks because it is not so simple to use it and it is a major PEtALS module.

Regards,
Christophe

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

Re: Error using WsnConsumerClient

2008-09-25T05:14:00Z

Hi Richard,

Sorry, I need to take time to check all these WSN issues.

On Thu, Sep 25, 2008 at 12:51 PM, aillet <richard.aillet@...> wrote:

I try to use the WS notification client WsnConsumerClient to send a data
publication.

Unfortunatly I obtain an error :
"wsa:InvalidAddressingHeader / wsa:MissingAddressInEPR /A header
representing a Message Addressing Property is not valid and the message
cannot be processed"

If you have an idea of the issue...
Thanks for your help.

Below you can see the 'tcpmon' log of my request and the related respose.

Richard.

the SOAP request from my WS client is :
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header>
<wsa:To
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:8080/petals/services/TopicSample</wsa:To>
<wsa:From
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:From>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing" />
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<wsnt:Notify xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:NotificationMessage>
<wsnt:Topic
Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete">TopicSample</wsnt:Topic>
<wsnt:ProducerReference>
<wsa:Address
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:Address>
</wsnt:ProducerReference>
<wsnt:Message>
<text>hi !</text>
</wsnt:Message>
</wsnt:NotificationMessage>
</wsnt:Notify>
</soapenv:Body>
</soapenv:Envelope>

the response is :
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soapenv:Header>

<wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
<soapenv:Subcode>

<soapenv:Value>wsa:InvalidAddressingHeader</soapenv:Value>
<soapenv:Subcode>

<soapenv:Value>wsa:MissingAddressInEPR</soapenv:Value>
</soapenv:Subcode>
</soapenv:Subcode>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">A header representing a
Message Addressing Property is not valid and the message cannot be
processed</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail>
<Exception>org.apache.axis2.AxisFault: A header
representing a Message Addressing Property is not valid and the message
cannot be processed at
org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355)
at
org.apache.axis2.addressing.AddressingFaultsHelper.triggerMissingAddressInEPRFault(AddressingFaultsHelper.java:180)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.extractEPRInformation(AddressingInHandler.java:408)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.extractFromEPRInformation(AddressingInHandler.java:298)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:173)
at
org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:97)
at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at
org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:108)
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:367)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295) at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)</Exception>
<wsa:ProblemHeaderQName>wsa:From</wsa:ProblemHeaderQName>
</soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

--
View this message in context: http://www.nabble.com/Error-using-WsnConsumerClient-tp19667221p19667221.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

Re: Error using WsnConsumerClient

2008-09-25T03:56:16Z

the code of my client class is :

public class PublisherClient {

public static final int PORT = 9999;

public static final String SUFFIX = "/notif/Consumer";

/**
* @param args
*/
public static void main(String[] args) {
final PublisherClient client = new PublisherClient();
Runtime.getRuntime().addShutdownHook(new Thread() {

/*
* (non-Javadoc)
* @see java.lang.Thread#run()
*/
@Override
public void run() {
}
});

client.publish();
System.out.println("Type Control-C to quit");
}

/**
* Subscribe to topic
*/
public void publish() {

// The notification producer EPR
EndpointReference destinationEPR = new EndpointReference(URI
.create("http://10.222.144.171:8080/petals/services/TopicSample"));

// the notification receiver (me)
EndpointReference consumer1EPR = new EndpointReference(URI.create("http://10.222.144.171:"
+ PORT + SUFFIX));

WsnConsumerClient client = new WsnConsumerClient(consumer1EPR, destinationEPR);

QName topic = new QName("TopicSample");
try {
System.out.println("Publishing to topic " + topic + " on WSN consumer "
+ destinationEPR);
NotificationMessage message = new NotificationMessage();
OMFactory fac = OMAbstractFactory.getOMFactory();
OMElement element;

OMNamespace omNs = fac.createOMNamespace("", "");
element = fac.createOMElement("text", omNs);
element.setText("hi !");

message.addMessageContent(element);
message.setTopic(topic);
client.notify(message);

} catch (WsnFault e) {
e.printStackTrace();
}
}

}

aillet wrote:

I try to use the WS notification client WsnConsumerClient to send a data publication.

Unfortunatly I obtain an error :
"wsa:InvalidAddressingHeader / wsa:MissingAddressInEPR /A header representing a Message Addressing Property is not valid and the message cannot be processed"

If you have an idea of the issue...
Thanks for your help.

Below you can see the 'tcpmon' log of my request and the related respose.

Richard.

the SOAP request from my WS client is :
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header>
<wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:8080/petals/services/TopicSample</wsa:To>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:From>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing" />
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<wsnt:Notify xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:NotificationMessage>
<wsnt:Topic Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete">TopicSample</wsnt:Topic>
<wsnt:ProducerReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:Address>
</wsnt:ProducerReference>
<wsnt:Message>
<text>hi !</text>
</wsnt:Message>
</wsnt:NotificationMessage>
</wsnt:Notify>
</soapenv:Body>
</soapenv:Envelope>

the response is :
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soapenv:Header>
<wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value>wsa:InvalidAddressingHeader</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value>wsa:MissingAddressInEPR</soapenv:Value>
</soapenv:Subcode>
</soapenv:Subcode>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">A header representing a Message Addressing Property is not valid and the message cannot be processed</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail>
<Exception>org.apache.axis2.AxisFault: A header representing a Message Addressing Property is not valid and the message cannot be processed at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355) at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMissingAddressInEPRFault(AddressingFaultsHelper.java:180) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractEPRInformation(AddressingInHandler.java:408) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractFromEPRInformation(AddressingInHandler.java:298) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:173) at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:97) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:108) 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:367) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) </Exception>
<wsa:ProblemHeaderQName>wsa:From</wsa:ProblemHeaderQName>
</soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Error using WsnConsumerClient

2008-09-25T03:51:53Z

I try to use the WS notification client WsnConsumerClient to send a data publication.

Unfortunatly I obtain an error :
"wsa:InvalidAddressingHeader / wsa:MissingAddressInEPR /A header representing a Message Addressing Property is not valid and the message cannot be processed"

If you have an idea of the issue...
Thanks for your help.

Below you can see the 'tcpmon' log of my request and the related respose.

Richard.

the SOAP request from my WS client is :
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header>
<wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:8080/petals/services/TopicSample</wsa:To>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:From>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing" />
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<wsnt:Notify xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:NotificationMessage>
<wsnt:Topic Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete">TopicSample</wsnt:Topic>
<wsnt:ProducerReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://10.222.144.171:9999/notif/Consumer</wsa:Address>
</wsnt:ProducerReference>
<wsnt:Message>
<text>hi !</text>
</wsnt:Message>
</wsnt:NotificationMessage>
</wsnt:Notify>
</soapenv:Body>
</soapenv:Envelope>

the response is :
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soapenv:Header>
<wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value>wsa:InvalidAddressingHeader</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value>wsa:MissingAddressInEPR</soapenv:Value>
</soapenv:Subcode>
</soapenv:Subcode>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">A header representing a Message Addressing Property is not valid and the message cannot be processed</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail>
<Exception>org.apache.axis2.AxisFault: A header representing a Message Addressing Property is not valid and the message cannot be processed at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355) at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMissingAddressInEPRFault(AddressingFaultsHelper.java:180) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractEPRInformation(AddressingInHandler.java:408) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractFromEPRInformation(AddressingInHandler.java:298) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:173) at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:97) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:108) 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:367) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) </Exception>
<wsa:ProblemHeaderQName>wsa:From</wsa:ProblemHeaderQName>
</soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Version 1.0 of the PEtALS Eclipse plug-ins

2008-09-25T03:00:24Z

Hi.

A new version of the PEtALS Eclipse plug-ins is available.
As a reminder, these plug-ins aims at making the development of SUs and SAs for PEtALS easier.

This release comes with several enhancements and bug fixes:

WSDL import: import all the XML files (XSD, WSDL) referenced directly or indirectly by the WSDL
Project structure: choose between the basic structure and a Maven structure (+ migration action)
XML validation and error markers for jbi.xml files
Several improvements about usability and error reporting
Several bugs corrected
New tutorial to create your own plug-in and improved documentation

More details can be found on the plug-ins' topic @ PEtALS' forum.
Notice also that due to a modification in the plug-ins structure, you should uninstall (*) the previous version of the plug-ins you have before installing this last version.
Using the the update site for this migration won't do the job correctly (indeed, the former and the new version of the main plug-in will co-exist, which is not really clean).

Once again, do not hesitate to post your feedback about the plug-ins (the forum fits for that).
Next updates will probably be announced on the forum rather than on this mailing-list...

Regards,

Vincent.

(*) To uninstall the previous versions of the plug-ins, follow these steps.

Europa

Help > Software Updates > Manage Configuration
Select all the PEtALS plug-ins and right-click "uninstall".
Click yes when you are prompt to restart your Eclipse.

Ganymede

Help > Software Updates > Installed Software
Select all the PEtALS plug-ins and click "uninstall".
Click yes when you are prompt to restart your Eclipse.

-- 
Vincent Zurczak
EBM WebSourcing
+33 (0) 4 76 38 12 16 77

WS-Addressing fields in WS-Notification requests

2008-09-25T01:28:45Z

Hello,

I have a question around the attributes WS-Addressing wsa:To, wsa:From in the SOAP header.
Are they used internally by the WS-Notification part of the BC-SOAP ?

If yes, how can they be modified ?

Thanks for your help.

Richard.

Re: RE: Re: RE: Re: Re: PEtALS Releases

2008-09-24T07:08:28Z

The maven sites with all the reports are going to be published soon (by the end of the week)

On Wed, Sep 24, 2008 at 3:52 PM, Richard AILLET <richard.aillet@...> wrote:

OK.

Otherwise is there also a release notes for the following components :

SOAP BC 2.2.1

XQUARE BC 2.0

EIP SE 2.2.1

POJO SE 2.0

XSLT SE 2.2.1 ?

Thanks.
Richard.

De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing
Envoyé : mercredi 24 septembre 2008 15:47

À : petals-users@...
Objet : [petals-users] Re: RE: Re: Re: PEtALS Releases

Now. It will be available on the web site before 4 PM but you can found it as attachment.

On Wed, Sep 24, 2008 at 3:42 PM, Richard AILLET <richard.aillet@...> wrote:

Do you know when it will be generated ?

De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing
Envoyé : mercredi 24 septembre 2008 15:37
À : petals-users@...
Objet : [petals-users] Re: Re: PEtALS Releases

Hi,

You are right the release notes generation tool has not been launched ;o)

On Wed, Sep 24, 2008 at 3:28 PM, aillet <richard.aillet@...> wrote:

Hy Christophe,

Could you publish please the release notes of this release (including NEW
FEATURES, FIXED BUGS, CHANGES) .

FYI, in the 'PEtALS news' page of your website
(http://petals.objectweb.org/news.html), the "release notes" link is broken
(url=http://petals.objectweb.org/releasenotes/release-notes-petals-kernel-2.2.1.txt).

Regards,
Richard.

Christophe Hamerling wrote:

>
> Hi all,
>
> We have just released the petals standalone v2.2.1 distribution and some
> JBI
> components (SOAP BC 3.1.1, XQUARE BC 2.0, EIP SE 2.2.1, POJO SE 2.0 and
> XSLT
> SE 2.2.1).
> You can get more information and links for downloads on the project
> website
> at http://petals.ow2.org.
>
> Enjoy,
> Christophe
>
> --
> Christophe Hamerling
> PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
> http://petals.ow2.org
> http://petals.ebmwebsourcing.com
> Phone : +33534320314
> Skype : christophe.hamerling
>
>
> --
> You receive this message as a subscriber of the petals-users@...
> mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
View this message in context: http://www.nabble.com/PEtALS-Releases-tp19631881p19648876.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

RE: Re: RE: Re: Re: PEtALS Releases

2008-09-24T06:52:00Z

OK.

Otherwise is there also a release notes for the following components :

Thanks.

Richard.

De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing
Envoyé : mercredi 24 septembre 2008 15:47
À : petals-users@...
Objet : [petals-users] Re: RE: Re: Re: PEtALS Releases

Now. It will be available on the web site before 4 PM but you can found it as attachment.

On Wed, Sep 24, 2008 at 3:42 PM, Richard AILLET <richard.aillet@...> wrote:

Do you know when it will be generated ?

De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing
Envoyé : mercredi 24 septembre 2008 15:37
À : petals-users@...
Objet : [petals-users] Re: Re: PEtALS Releases

Hi,

You are right the release notes generation tool has not been launched ;o)

On Wed, Sep 24, 2008 at 3:28 PM, aillet <richard.aillet@...> wrote:

Hy Christophe,

Could you publish please the release notes of this release (including NEW
FEATURES, FIXED BUGS, CHANGES) .

FYI, in the 'PEtALS news' page of your website
(http://petals.objectweb.org/news.html), the "release notes" link is broken
(url=http://petals.objectweb.org/releasenotes/release-notes-petals-kernel-2.2.1.txt).

Regards,
Richard.

Christophe Hamerling wrote:

>
> Hi all,
>
> We have just released the petals standalone v2.2.1 distribution and some
> JBI
> components (SOAP BC 3.1.1, XQUARE BC 2.0, EIP SE 2.2.1, POJO SE 2.0 and
> XSLT
> SE 2.2.1).
> You can get more information and links for downloads on the project
> website
> at http://petals.ow2.org.
>
> Enjoy,
> Christophe
>
> --
> Christophe Hamerling
> PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
> http://petals.ow2.org
> http://petals.ebmwebsourcing.com
> Phone : +33534320314
> Skype : christophe.hamerling
>
>
> --
> You receive this message as a subscriber of the petals-users@...
> mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
View this message in context: http://www.nabble.com/PEtALS-Releases-tp19631881p19648876.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

Re: RE: Re: Re: PEtALS Releases

2008-09-24T06:46:30Z

Now. It will be available on the web site before 4 PM but you can found it as attachment.

On Wed, Sep 24, 2008 at 3:42 PM, Richard AILLET <richard.aillet@...> wrote:

Do you know when it will be generated ?

De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing
Envoyé : mercredi 24 septembre 2008 15:37
À : petals-users@...
Objet : [petals-users] Re: Re: PEtALS Releases

Hi,

You are right the release notes generation tool has not been launched ;o)

On Wed, Sep 24, 2008 at 3:28 PM, aillet <richard.aillet@...> wrote:

Hy Christophe,

Could you publish please the release notes of this release (including NEW
FEATURES, FIXED BUGS, CHANGES) .

FYI, in the 'PEtALS news' page of your website
(http://petals.objectweb.org/news.html), the "release notes" link is broken
(url=http://petals.objectweb.org/releasenotes/release-notes-petals-kernel-2.2.1.txt).

Regards,
Richard.

Christophe Hamerling wrote:

>
> Hi all,
>
> We have just released the petals standalone v2.2.1 distribution and some
> JBI
> components (SOAP BC 3.1.1, XQUARE BC 2.0, EIP SE 2.2.1, POJO SE 2.0 and
> XSLT
> SE 2.2.1).
> You can get more information and links for downloads on the project
> website
> at http://petals.ow2.org.
>
> Enjoy,
> Christophe
>
> --
> Christophe Hamerling
> PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
> http://petals.ow2.org
> http://petals.ebmwebsourcing.com
> Phone : +33534320314
> Skype : christophe.hamerling
>
>
> --
> You receive this message as a subscriber of the petals-users@...
> mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
View this message in context: http://www.nabble.com/PEtALS-Releases-tp19631881p19648876.html
Sent from the Petals Users mailing list archive at Nabble.com.

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : +33534320314
Skype : christophe.hamerling

Release Notes
OW2 Consortium PEtALS -- petals-kernel Version 2.2.1 (2008-09-19)

Introduction
------------
PEtALS Services Platform

Maintenance release

See the project website at http://petals.ow2.org for more information.

Please refer to our issue tracker for more details on issues with id [xxx]
http://forge.objectweb.org/tracker/?group_id=213

Changes in this release
-----------------------

FIXED BUGS:
* [310333] - Space character in petals Path
* [310647] - Merge from branch petals-kernel-1.4 : Bottleneck in the MessageExchangeSerializer.

CHANGES:
* [310973] - Unactive autoloader in production environment
* Cleaner Exception handling when interrupting component acceptor thread while PEtALS stops.
* Update container configuration info displayed in PEtALS console

Enjoy!
-The PEtALS team

--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws