-
15. Re: COM Gateway
dirkbangel Feb 26, 2008 11:46 AM (in response to dirkbangel)We have already gone deep into technical details and there are a lot of
advantages to mention. Nevertheless the following links could be quite
interesting for you tfennelly .
http://j-interop.org/advantages.html and
http://j-interop.org/introduction.html
Thanks for the replies,
best regards,
Dirk -
16. Re: COM Gateway
marklittle Feb 27, 2008 6:35 AM (in response to dirkbangel)Whatever works best for you. It's been about 7 years since I did anything with COM, so I'm happy for you to lead the technical discussions ;-)
-
17. Re: COM Gateway
dirkbangel Mar 11, 2008 3:40 PM (in response to dirkbangel)Hi Mark, Hi Kurt
After an "long" evaluation phase we now came to some more detailed questions. As proposed in the ESB developers guide we
intended to use the JBOSS_XML message type. Therefore we pass our message content into the esb message body.
Does this match with your expiriences or should we better use an own MessagePlugin to fully implement our own message
layout?
If you propose the JBOSS_XML message type, we have to provide a implementation of the MarshalUnmarshalPlugin for
serializing and deserializing our Java instances in a XML representation. If so,
is there an general way of registering our plugin to the esb container (providers section of the deployment descriptor?)
or do we have to put a jbossesb-property.xml into each deployment (.esb)?
Last but not least, if we choose the JBOSS_XML representation and if we serialize our content into XML, which is the
more or less human readable, is the XML representation encrypted on the wire - encrypted while transportation over the
esb? Can we enable an automatic encryption for messages trough the esb? We ask because we currently have a stateless
listener and we pass all "of our session information", including credentials, into the messages. The messages are passed
around the client(caller) and our esb listener.
A first roughly summarized "structural design" document can be found (all IP protected stuff is dropped out) at http://jbossesb.javainteroperability.com/ext/structuraldesign.pdf. We are happy to recieve all comments.
Thanks for your replies,
Best regards
Dirk -
18. Re: COM Gateway
marklittle Mar 12, 2008 5:03 AM (in response to dirkbangel)Hi Dirk. Let me take a look at this and get back to you in the next day or so.
-
19. Re: COM Gateway
dirkbangel Mar 25, 2008 3:26 PM (in response to dirkbangel)Hi Mark, Hi Kurt
We would like to ask if JBoss ESB plans to introduce Java- Annotations
instead of the deployment descriptor? We were hoping for something on
the lines of JSR 109 for Webservices- something like @ESBListener
(JSR109:@WebService) and @ESBAction (JSR109: @WebMethod).
We hope you had time to read through our rough ("filtered")
implementation design. We are happy to all comments- also critical comments.
Thanks for your replies,
Best regards
Dirk -
20. Re: COM Gateway
kconner Mar 26, 2008 1:18 AM (in response to dirkbangel)Hiya Dirk.
Yes, we are planning on providing annotation support for the actions. We are currently involved in a team 'face 2 face' meeting this week and this is one of the topics on our agenda.
Kev -
21. Re: COM Gateway
marklittle Mar 26, 2008 5:59 PM (in response to dirkbangel)Hi Dirk. Yes, I read through the doc but haven't had a chance to post my response. I'm in the meeting Kevin mentioned so will try to get to this at the weekend.
-
22. Re: COM Gateway
lihui_pang Mar 27, 2008 2:25 PM (in response to dirkbangel)"DirkBangel" wrote:
Hi Mark, Hi Kurt
After an "long" evaluation phase we now came to some more detailed questions. As proposed in the ESB developers guide we
intended to use the JBOSS_XML message type. Therefore we pass our message content into the esb message body.
Does this match with your expiriences or should we better use an own MessagePlugin to fully implement our own message
layout?
Did you get answer on this? How do you register the plugin, is there any sample?
If you propose the JBOSS_XML message type, we have to provide a implementation of the MarshalUnmarshalPlugin for
serializing and deserializing our Java instances in a XML representation. If so,
is there an general way of registering our plugin to the esb container (providers section of the deployment descriptor?)
or do we have to put a jbossesb-property.xml into each deployment (.esb)?
Last but not least, if we choose the JBOSS_XML representation and if we serialize our content into XML, which is the
more or less human readable, is the XML representation encrypted on the wire - encrypted while transportation over the
esb? Can we enable an automatic encryption for messages trough the esb? We ask because we currently have a stateless
listener and we pass all "of our session information", including credentials, into the messages. The messages are passed
around the client(caller) and our esb listener.
Did you get answer on this too?
A first roughly summarized "structural design" document can be found (all IP protected stuff is dropped out) at http://jbossesb.javainteroperability.com/ext/structuraldesign.pdf. We are happy to recieve all comments.
Thanks for your replies,
Best regards
Dirk
Please share your result with us. Thanks. -
23. Re: COM Gateway
lihui_pang Mar 27, 2008 2:27 PM (in response to dirkbangel)I am evaludating JBoss ESB too. I have the similar questions, e.g. if the message is non-serializable, do we need to implement MarshalUnmarshalPlugin, or is that existing plugin for us to use?, how to register plugin? -- I can't find any sample on this.
If you have answers on this , please share.
Many thanks,
Lihui -
24. Re: COM Gateway
marklittle Apr 4, 2008 9:22 AM (in response to dirkbangel)Dirk, sorry for the delay in getting back to you, but here are some comments on your document.
1: on page 3 you state "The listener implementation class is not
serializeable. This not allows to use the JBoss ESB message type JAVA_SERIALIZED,
because we not provide MarshalUnmarshalPlugin only for the message type JBOSS_XML. " I didn't understand that. Why does the serializability (or not) of the listener affect the Message?
2: the use of JAXB makes perfect sense AFAICT from what you want to achieve. -
25. Re: COM Gateway
marklittle Apr 4, 2008 9:28 AM (in response to dirkbangel)"lihui_pang" wrote:
I am evaludating JBoss ESB too. I have the similar questions, e.g. if the message is non-serializable, do we need to implement MarshalUnmarshalPlugin, or is that existing plugin for us to use?, how to register plugin? -- I can't find any sample on this.
Yes, the idea is that you can add a MarshalUnmarshalPlugin for each datatype so you get direct control over how to marshal (or unmarshal) it to (from) the Message. You may want to monitor http://jira.jboss.com/jira/browse/JBESB-1643.