[jira] Created: (SM-1108) Versionning of endpoints

[Guillaume Nodet (JIRA)]

Versionning of endpoints


 Key: SM-1108
 URL: https://issues.apache.org/activemq/browse/SM-1108
 Project: ServiceMix
  Issue Type: New Feature
Reporter: Guillaume Nodet
 Fix For: 4.0


As the meta-data associated to the endoint is a map of key-value pairs, it 
should be easy to add a VERSION property which would be used by the NMR.  All 
new exchanges would use the best available version (unless the version is 
explicitely specified maybe).  An existing exchange would still use the version 
it was previously using.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: XBean Namespaces

[Andreas Schaefer (2)]

You can find it in:

/deployables/serviceeingines/servicemix-eip/ 
target/xbean/servicemix-eip.xsd


Otherwise you'll find it in the root of the archive servicemix-eip- 
.jar


There you'll find the URL in the target namespace.

Have fun

Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED]


On Oct 17, 2007, at 1:37 PM, Gordon Dickens wrote:

To better understand XBeans, I wanted to understand where or how  
the namespace is defined for each service type (binding component/ 
service engine).


For example:
For the servicemix-eip wiretap, I see in the  
org.apache.servicemix.eip.patterns.WireTap.java class that the  
xbean is defined as "wire-tap" but I don't see an obvious reference  
to which namespace I should use when defining the xbean.xml for my  
service unit.  I used the following


   
   http://myproject.com/myservice/1.0";
   xmlns:j="http://myproject.com/myotherservice//1.0";
   xmlns:eip="http://servicemix.apache.org/eip/1.0";>

   
   ...


Is the url "http://servicemix.apache.org/eip/1.0"; resolved?  If so,  
where can I find it?


Thanks in advance,
Gordon Dickens




Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED]




PGP.sig
Description: This is a digitally signed message part

Re: ServiceMix Bean issues with send()

[Andreas Schaefer (2)]

Hi Geeks

I am moving this thread to the DEV mailing list because it not about  
using ServiceMix anymore. The problem is that when using the  
asynchronous message exchange that the response is not sent back to  
the calling SU but to the Provider Endpoint of the called SU.


I just keep on spinning here. I have a closer look at the  
MessageExchangeImpl and saw that the Mirror references the same  
packet and beside the ROLE and STATUS everything else is set or  
retrieved from the packet. This means that always the MIRROR is  
pointing to the same service, endpoint etc.


Creating a new ME it will be of role CONSUMER and the mirror is of  
role PROVIDER. The Delivery Channel (DC) will send the ME using the  
mirror and so the DC will send it to the target service PROVIDER  
endpoint. When the response is sent back the DC will use the MIRROR  
(of the MIRROR), which has not the role CONSUMER, but because of the  
same packet it will use the same Service / Endpoint / Interface Name  
meaning the message is sent back to the same service with the only  
exception that the ME is send to the CONSUMER endpoint instead.


But shouldn't it be that the ME references the CONSUMER endpoint of  
the caller (the service that created and sent the message originally)  
and the MIRROR references the PROVIDER endpoint of the called service  
(the service that received the original message) which most likely  
are not the same SU.


This would mean that the addressing parts (service name, endpoint,  
interface name) must be removed from the "packet" and kept separate  
from the ME and its MIRROR. We might also need to swap the ME and  
MIRROR so that the ME is pointing to the PROVIDER and the MIRROR  
pointing to the CONSUMER. This means that the DC will use the ME  
instead of the MIRROR to send the ME and NMR or the receiving DC must  
swap the ME / MIRROR so that the Provider Endpoint receives the  
MIRROR which is subsequently pointing back to the calling service.


Let me know what you think?

Thanks - Andy

On Oct 17, 2007, at 9:11 AM, Andreas Schaefer (2) wrote:


Hi Guillaume

I tried something new using the SCRIPT as the provider service  
rather than another BEAN. Now I think I see a little bit more what  
is going wrong. What is happening is that the response is handled  
by the BeanComponent (which is good) but because it is using the  
MIRROR member to which it sends the response to it fails because of  
an unknown request (it should work because I fix that issue locally).


From my understanding I think the message is properly sent back to  
the correct BC/SE, in this case the Bean Component, but because it  
uses the MIRROR as the address it sends it to the wrong SU, which  
in this case is the SCRIPT SU which is not even a BEAN. It seems to  
me that the MIRROR is pointing to the consumer endpoint of the  
provider SU rather than the consumer SU. That is my log output:


[Notes Andy]: Here I send the InOut Message to he Provider:

2007-10-17 08:51:53,515 [58-0:0-thread-1] INFO   
ScriptInOutControllerBean  - onMessageExchange() send new ME:  
InOut[

  id: ID:10.250.1.197-115aea91258-2:0
  status: Active
  role: consumer
  service: {urn:scout}script-receiver-service
  operation: IdontCare: 0
  in: >DontCareEvenMore0

]
2007-10-17 08:51:53,515 [58-0:0-thread-1] DEBUG  
BeanComponent  - Created correlation id: ID: 
10.250.1.197-115aea91258-2:0
2007-10-17 08:51:53,515 [58-0:0-thread-1] DEBUG  
DeliveryChannelImpl- Send ID: 
10.250.1.197-115aea91258-2:0 in DeliveryChannel{ID: 
10.250.1.197-115aea91258-0:0}


[Notes Andy]: "AS-LOG" are log statements I added to Smx

2007-10-17 08:51:53,515 [58-0:0-thread-1] INFO   
DeliveryChannelImpl- AS-LOG, doSend(), ME: InOut[

  id: ID:10.250.1.197-115aea91258-2:0
  status: Active
  role: consumer
  service: {urn:scout}script-receiver-service
  operation: IdontCare: 0
  in: >DontCareEvenMore0

]
2007-10-17 08:51:53,516 [58-0:0-thread-1] INFO   
DeliveryChannelImpl- AS-LOG, doSend(), send exchange to  
MIRROR: InOut[

  id: ID:10.250.1.197-115aea91258-2:0
  status: Active
  role: provider
  service: {urn:scout}script-receiver-service
  operation: IdontCare: 0
  in: >DontCareEvenMore0

]
2007-10-17 08:51:53,516 [58-0:0-thread-1] DEBUG  
SedaFlow   - Called Flow send
2007-10-17 08:51:53,518 [58-0:1-thread-1] DEBUG  
SedaQueue  -  
[EMAIL PROTECTED] dequeued  
exchange: InOut[

  id: ID:10.250.1.197-115aea91258-2:0
  status: Active
  role: provider
  service: {urn:scout}script-receiver-service
  endpoint: in-out-receiver
  operation: IdontCare: 0
  in: >DontCareEvenMore0

]
2007-10-17 08:51:53,518 [58-0:1-thread-1] DEBUG  
ScriptComponent- Received exchange: status: Active,  
role: provider
2007-10-17 08:51:53,519 [58-0:1-thread-1] DEBUG  
ScriptComponent- Retrieved correlation id: ID: 
10.250.1.197-115aea91258-2:0


...

[Notes Andy]: Script acknowl

Re: XBean Namespaces

[Gordon Dickens]

Thanks Andreas!

Andreas Schaefer (2) wrote:

You can find it in:

Home>/deployables/serviceeingines/servicemix-eip/target/xbean/servicemix-eip.xsd


Otherwise you'll find it in the root of the archive 
servicemix-eip-.jar


There you'll find the URL in the target namespace.

Have fun

Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED] 


On Oct 17, 2007, at 1:37 PM, Gordon Dickens wrote:

To better understand XBeans, I wanted to understand where or how the 
namespace is defined for each service type (binding component/service 
engine).


For example:
For the servicemix-eip wiretap, I see in the 
org.apache.servicemix.eip.patterns.WireTap.java class that the xbean 
is defined as "wire-tap" but I don't see an obvious reference to 
which namespace I should use when defining the xbean.xml for my 
service unit.  I used the following


   
   http://myproject.com/myservice/1.0";
   xmlns:j="http://myproject.com/myotherservice//1.0";
   xmlns:eip="http://servicemix.apache.org/eip/1.0";>

   
   ...


Is the url "http://servicemix.apache.org/eip/1.0"; resolved?  If so, 
where can I find it?


Thanks in advance,
Gordon Dickens




Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED] 

ServiceNames and EndPoints

[Gordon Dickens]

Hello,

If I have a 2 services defined with the same servicename and different 
endpoints and I attempt to pass a message to that servicename without 
specifying the endpoint what would be the expected result?


Provider
serviceName="myService" endpoint="ep1"
...
serviceName="myService" endpoint="ep2"
...

Consumer
targetServiceName="myService"

Will both endpoints get the message?  Will only one?  Which one?

Thanks,
Gordon Dickens

Re: ServiceNames and EndPoints

[Guillaume Nodet]

Only one, and you can not control which one in a standard JBI way.
However, ServiceMix has a notion of Endpoint resolver and policy, but
these are currently configured at the container level.

On 10/18/07, Gordon Dickens <[EMAIL PROTECTED]> wrote:
> Hello,
>
> If I have a 2 services defined with the same servicename and different
> endpoints and I attempt to pass a message to that servicename without
> specifying the endpoint what would be the expected result?
>
> Provider
> serviceName="myService" endpoint="ep1"
> ...
> serviceName="myService" endpoint="ep2"
> ...
>
> Consumer
> targetServiceName="myService"
>
> Will both endpoints get the message?  Will only one?  Which one?
>
> Thanks,
> Gordon Dickens
>


-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

[jira] Created: (SM-1109) attachment should be supported in cxf se and bc

[Freeman Fang (JIRA)]

attachment should be supported in cxf se and bc
---

 Key: SM-1109
 URL: https://issues.apache.org/activemq/browse/SM-1109
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-cxf-bc, servicemix-cxf-se
Reporter: Freeman Fang
Assignee: Freeman Fang
 Fix For: 3.2


cxf bc should handle soap message with mtom attachment and save the attachment 
into NormalizeMessage then deliver to cxf se, cxf se should handle attachment 
correctly

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Possible Solution to a camel serviceengine problem or only a bad workaround??

[Kristian Köhler]

Hi all

I found a solution for my problem regarding the routing problem yesterday 
(http://www.nabble.com/How-to-route-a-MessageExchange-using-camel-to-ode-tf4641042s12049.html#a13255218).
 I wasn't able to route a message coming over HTTP Binding through camel to ODE 
service engine. I specified a routing rule like this:

--- 8< ---

String fromUri = 
"jbi:endpoint:http://gaswerk.sourceforge.net/soa-stack/enpoint";;
String toUri = 
"jbi:endpoint:http://gaswerk.sourceforge.net/soa-stack/sample/bpel/SampleBPELProcess/SampleBPELProcessPort?mep=in-out";;

from(fromUri).to(toUri);

--- 8< ---

This results in the following error in the ODE service engine: "Operation not
found". If I route the message directly from HTTP binding to the ODE service
engine everything works fine.

I haven't found a syntax for specifying a operation for an endpoint within the
routing expression shown above. (Makes this sense at all??)

After some investigation I found in the camel service engine (JbiExchange.java)
a property "jbi.operation" which is set for the camel exchange (line 151) but I
couldn't figure out where it is used. 

I'm absolutly not sure about my next step. ;-) 

In the JbiBinding a new JBI Message Exchange is created to route the message
back to the NMR (createJbiMessageExchange). I added some lines to set the
operation on the resulting MessageExchange (see attached patch). 

Now my sample works fine but as mentioned before I'm not sure if this is
correct. Does this makes sense??? Is it a bug or a bad workaround for my
problem?? 

The question to me is: Is it correct to 'loose' the information about the
operation?? Do I have to add this information within my routing rule reading the
property (how?)?

Thanks!

Kristian

-- 
Kristian Köhler
software architect
dmc digital media center GmbH
Rommelstraße 11
70376 Stuttgart (Germany)
Telefon: +49 711 601747-434
Telefax: +49 711 601747-141
Internet: www.dmc.de

Handelsregister: AG Stuttgart HRB 18974
Geschäftsführer: Andreas Magg, Daniel Rebhorn, Andreas Schwend

-

Bessere Gespräche, besseres E-Business.

Willkommen auf dem Deutschen Versandhandelskongress 2007.
Besuchen Sie uns in der dmc Lounge im Foyer 1. Stock. 

Wir sehen uns. Mehr Infos: www.dmc.de/lounge

[jira] Resolved: (SM-1109) attachment should be supported in cxf se and bc

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/SM-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved SM-1109.
--

Resolution: Fixed

> attachment should be supported in cxf se and bc
> ---
>
> Key: SM-1109
> URL: https://issues.apache.org/activemq/browse/SM-1109
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-cxf-bc, servicemix-cxf-se
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 3.2
>
>
> cxf bc should handle soap message with mtom attachment and save the 
> attachment into NormalizeMessage then deliver to cxf se, cxf se should handle 
> attachment correctly

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.