JBossDeveloper

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 ;-)

Hi Dirk. Let me take a look at this and get back to you in the next day or so.

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

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.

"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

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

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.

"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.