It depends what you mean by hard coded ;-) They are not in the java code but in the xml configuration file, so you can easily change them. But if you mean that you won't be able to change them at runtime, that's true, but JBI does not offer any way to do that (you could always expose a bean through JMX to change the values dynamically though). As for the actual class to use, it depends on your needs. You can either create a full SE and deploy service units onto it and you would write a Component by extending DefaultComponent and an endpoint by inheriting ProviderEndpoint. If you don't need to write a full SE, you could leverage servicemix-bean, servicemix-jsr181 or write a lightweight component.
On 4/26/07, yinwen fu <[EMAIL PROTECTED]> wrote:
Does this mean I should hard-code to implement the message route?Which class should my hello SE extend?TransformComponent and SimpleEndpoint? gnodet wrote: > > Well, it's up to your own component to create and send JBI exchanges then > ... > You can configure the target as properties on your endpoints and use them > when sending exchanges. > -- View this message in context: http://www.nabble.com/questions-about--SE-invokeing-External-Webservices-tf3635738s12049.html#a10192570 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
