Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 4.1, 4.2.0, 4.3.0
-
Fix Version/s: 4.4.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Blocker [ 1 ] | |
| Description |
The following error occurs when proxy-ing an external web-service:
{code} sample-0 2013/09/30 17:31:01,405 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description javax.jbi.messaging.MessagingException: Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:463) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:344) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:259) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) {code} |
The following error occurs when proxy-ing an external web-service:
{code} sample-0 2013/09/30 17:31:01,405 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description javax.jbi.messaging.MessagingException: Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:463) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:344) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:259) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) {code} FYI: the operation mentioned in the log trace is a binding operation that is different from the expected operation declared in the port type. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Blocker [ 1 ] | Critical [ 2 ] |
| Assignee | Nicolas Oddoux [ noddoux ] | Christophe DENEUX [ cdeneux ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 4.3.1 [ 10405 ] | |
| Resolution | Fixed [ 1 ] |
| Link |
This issue blocks |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
On the consumer side, the mapping between SOAPAction and message exchange operation must be done between the SOAPAction defined at binding level and operation name at port type level (not binding operation name)