Hi Eric,
Ruwan, we simply have to figure this out... ;-) It is possible that you
don't miss anything and I'm the one who misses something. You know much
more about your software than I do. Right now I have not seen WSO2 WSAS
and don't know it's "try it" feature. I was only thinking about what
information would be needed in order to test a service endpoint. If I
want to check more than just that it is possible to establish a network
connection to that specific host/port combination I would have to know
how to create a proper request. How shall I create a proper request
without knowing
- the transport/network protocol to use
- the application protocol (e.g. SOAP, Hessian) to use
- how a valid request message payload looks like
In the SOAP-case I can easily create some test requests based on the
WSDL of the service. In the Hessian case I would need to know something
about the service interface.
Well, I was not thinking about Hessian services on my last answer. Yes,
for SOAP and most of the other protocols like JMS and so on. WSDL
describes all the bits that you have specified (protocol, operations,
services, port, and schema of the request and response messages) I don't
know how Hessian publishes its service interface, if there is a standard
service publishing mechanism in Hessian I think that can be used to
test, but if there isn't such mechanism (if it is just the service
interface without endpoint details) how can some one discover Hessian
services, or no one is supposed to discover those services and just the
person who knows the endpoint can only access that, is that the case?
I also have another question in mind. If you already have such a "try
it" feature in WSAS, why don't you have this in ESB? Is this planned and
was only postponed due to other features with higher priority?
This will go in to the ESB 2.0 release. We will be releasing the Road
Map within next two weeks. :-)
This (protocol specific sequences) is a trivial fix, but adds more
complexity to the configuration language, IMHO
Is it a trivial fix? Yes, this would be a new option which of course
would increase the complexity of the configuration a bit, but not
necessarily from a user perspective, as the protocol type could be an
optional parameter. Having the meaning that if it is not present, it
would preserve the current behaviour (sequence is always executed).
I agree with this model, and actually this is how I was thinking of
implementing this when you first raise this over the list :-) ? You may
go ahead and create an enhancement JIRA issue on this....
https://wso2.org/jira/browse/ESBJAVA
Thanks,
Ruwan
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
