[jboss-dev-forums] [Design of JBoss ESB] - Re: Publish ESB services to web services

[jim.ma]

anonymous wrote : Generating the schema is also an option, perhaps by specifying the types rather than the xsd.

Agreed. So we can modify the configuration file as this :

  <service category="ServiceESB" name="helloworld" description="Hello World">
  |        <actions mep="OneWay" input="org.jboss.esb.Request" output="org.jboss.esb.Response" fault1="org.jboss.esb.Fault">
  |                    <action name="action1" 
  |                    	class="org.jboss.soa.esb.actions.Action1" 
  |                    	process="displayMessage"/>      
  |                     <action name="action2" class="org.jboss.soa.esb.actions.Action2" process="invokeCount"/>
  |         </actions>
  |    </service>	

org.jboss.esb.Request , Response and Fault class can be a  java bean and inherits from  a mew class XMLMessageBase .
XMLMessageBase is a sub class of xml MessageImpl . In XMLMessageBase, we can put the request part value in Esb message body . Also by invoking the method in XMLMessageBase, we can retrieve the response part value from esb message body .
By reflecting the Request class, we can generate schema  using apache  XMLSchema even there is no annotation in it.
anonymous wrote : Again, there is no easy answer to this at the moment.
  | 
  | What do you feel is the right approach for handling this?   

So far ,what I have in mind is building the SOAPFault message using ActionProcessingException.



 


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146447#4146447

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146447