You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Francois Mireaux (JIRA)" <ji...@apache.org> on 2009/04/07 16:21:34 UTC
[jira] Created: (SMXCOMP-502) An Axis2 binding component
An Axis2 binding component
--------------------------
Key: SMXCOMP-502
URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
Project: ServiceMix Components
Issue Type: New Feature
Reporter: Francois Mireaux
Priority: Minor
Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-502) An Axis2 binding component
Posted by "Francois Mireaux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51090#action_51090 ]
Francois Mireaux commented on SMXCOMP-502:
------------------------------------------
I must be more precise. IMHO it's a binding component with interaction with NMR located in specific endpoint code (client or server).
The EchoServiceClient class used in test processes an InOut exchange.
The EchoServiceSkeleton class (used by a consumer endpoint in test) don't use JBI, but it's only by simplification : the delivery channel is accessible trough the configuration context property smx.deliveryChannel and could be used to dispatch message to NMR. One must use this code in a service implementation method :
ConfigurationContext context = MessageContext.getCurrentMessageContext().getConfigurationContext();
channel = (DeliveryChannel)context.getProperty("smx.deliveryChannel");
I have tested the component with a service redispatching the SOAP content received as an attachment file in a mail sended by the servicemix mail binding component. I will try to add a ServiceMix component in test to show a usage .
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-502) An Axis2 binding component
Posted by "Francois Mireaux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Mireaux updated SMXCOMP-502:
-------------------------------------
Attachment: servicemix-axis2-bc.zip
The new version of EchoServiceSkeleton dispatch a JBI message for better demonstration.
The basic question is : does a binding component must have default "marshaler" or not ? Service unit using Axis2 binding component must define client and/or server classes. But I guess default classes could be included with more or less work.
I agree that the proposed component could be improved, for instance with utility or abstract class for service implementation.
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.zip, servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-502) An Axis2 binding component
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51089#action_51089 ]
Freeman Fang commented on SMXCOMP-502:
--------------------------------------
Hi Francois,
If I understand correctly, your "binding component" doesn't interact with NMR at all. It's just a axis2 client or server endpoint.
So it can't talk with other jbi endpoint (from SE or BC) through NMR, right?
IMHO, your patch isn't binding component according to JBI spec, though it can play as a client or server which can talk with externel server or client through http, it's not a JBI component. JBI component should be able to dispatch message to NMR and process message from NMR, which means play with other jbi endpoint through NMR.
Freeman
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-502) An Axis2 binding component
Posted by "Francois Mireaux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Mireaux updated SMXCOMP-502:
-------------------------------------
Attachment: servicemix-axis2-bc.ZIP
Tested with Axis2/Sandesha2 1.3 and ServiceMix 3.2.4-SNAPSHOT
ServiceMix version must be ajusted.
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMXCOMP-502) An Axis2 binding component
Posted by "Francois Mireaux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51087#action_51087 ]
Francois Mireaux commented on SMXCOMP-502:
------------------------------------------
The component acts as standard Axis2 client and/or server. Client and server codes use the templates generated by the Axis2 wsdl2java tool (see Echo service sample used in tests).
By simplification, Echo consumer endpoint bean is not realistic : it directly reply without JBI interaction.
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-502) An Axis2 binding component
Posted by "Francois Mireaux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Mireaux updated SMXCOMP-502:
-------------------------------------
Attachment: servicemix-axis2-bc.zip
There are now to usage modes for the component :
- use the wsdl2java Axis2 utility and write our client with the generated stub and/or our complete server skeleton
- use the default marshallers for consumer (Axis2BcMessageReceiverInOut) and provider (Axis2BcDefaultClient) endpoints. Marshallers handle conversion between SOAP body and JBI message content and manage SOAP headers as message property.
You can use WS-RM with default marshallers.
Limitations of default marshallers :
- no SOAP attachments handling
- no WS-Security handling
See tests sources for more usage details.
> An Axis2 binding component
> --------------------------
>
> Key: SMXCOMP-502
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-502
> Project: ServiceMix Components
> Issue Type: New Feature
> Reporter: Francois Mireaux
> Priority: Minor
> Attachments: servicemix-axis2-bc.zip, servicemix-axis2-bc.zip, servicemix-axis2-bc.ZIP
>
>
> Another SOAP binding component sor those who want to use WS-RM 1.1, not yet implemented in CXF or are more familiar with Axis2 than CXF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.