This will seem like an unusual post :)
A long time ago I added a HttpMarshaller class with the JBoss Remoting gateway code. For some reason (that now appears to be bizarre) I added code to unwrap JBossRemoting InvocationResponse types. I think I must have done this in error, but I'm not totally sure :)
JBossRemoting (at least the CoyoteInvoker) wraps all response objects in a InvocationResponse instance where the client was a JBoss Remoting client. The code I added in the HttpMarshaller totally screws up JBoss Remoting clients as they are expecting an InvocationResponse in the response stream (has no effect on non JBoss Remoting clients).
I think the handling of the InvocationResponse in the HttpMarshaller class is invalid and should be removed. Anyone know of a reason why it should not be removed?
T.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236339#4236339
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236339
"alesj" wrote : "flavia.rainone(a)jboss.com" wrote :
| | Regarding the convertion tool, what do I do with embedded XMBeans and with XMBeans with references to external descriptors?
| |
| It's been a while since I used this, so how does this exactly look like?
| Although we have beans nested within beans, is this it?
This is when you define one of the attributes xmbean-dd (external descriptor) or xmbean-code (embedded), in order to define the interface of the MBean.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236177#4236177
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236177
IMO, there should be a common location for all the jboss specific annotations. Hence i think the ejb3-ext-api is the right place for this.
anonymous wrote : Also we need to be able to extend jboss-metadata to allow plugins, so that the retry function can be enabled via descriptors.
|
I am not really good at xml xsd and similar things, but i guess there would be some option available where in we can say a given xsd element (ex: sessionBeanType) can have multiple different type of sub-elements whose type is not known. Just an example in jboss.xml
<session>
| <tx-retry>numberofattempts</tx-retry>
| ...// later on for some other functionality
| <xyz>blahblahblah</xyz>
| </session>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235975#4235975
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235975