[Design of JBoss ESB] - Re: COM Gateway
by lihui_pang
"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.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139430#4139430
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139430
16 years, 3 months
[Deployers on JBoss (Deployers/JBoss)] - Re: jee module's alt-dd
by scott.stark@jboss.org
"alex.loubyansky(a)jboss.com" wrote :
| I guess, I misunderstand this. AFAICS, the alt-dd is specified in the application.xml per module. Like this
|
| ...
|
| The ModuleMetaData has a property for alt-dd but it's not used except in the web deployer.
Sure, your right, I was thinking it could also show up at the descriptor level. That would be silly.
"adrian(a)jboss.org" wrote :
| Then the metadata classes could implement it and parsing deployers check it
| regardless of where it appears.
|
...
On Alex's point, these just need to be added as attachments by the EarStructure
and checked by the relevant parsing deployer.
Good point, the EarStructure is where this should be done. The AltDD interface would need to be in the deployer project so that the general handling of the alt path can be handled in AbstractVFSParsingDeployer.
If were using the AltDD interface as the typed path/key, wouldn't the programtic usage be:
| addAttachment(Class<T> type, T attachment);
| VFSDeployment d = new VFSDeployment(ejbjar);
| AltDD altDD = ...("al.ternatelocation");
| d.addAttachment(AltDD.class, altDD);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139425#4139425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139425
16 years, 3 months