Hello Ruwan, please see my comments below!
> > I also thought of storing a kind of "service or protocol type" > > information in the registry for other reasons - namely testing. > > One other feature I'm missing is a way to check whether my current esb > > configuration is valid. I mean not valid in terms of syntactical checks > > but valid from a functional view. E.g. did the administrator specify the > > right service endpoints? Are hostnames and ports correct? It would be > > cool, if one could easily test this on different levels (single > > endpoint, all endpoints, single proxy service, all proxy services). In > > order to do meaningful testing one would have to generate a proper > > request, send it, and present the result. Maybe one could specify the > > name of an existing test method of the service. How to incorporate this, > > if the esb (registry) does not know, which protocol to use? > Well, to do this do we need to keep the information on protocols in a > central place. If you have a look at WSO2 WSAS, there is a feature > called try it, which gives you a simple UI for any endpoint to test that > (it can be an endpoint external to ESB or an proxy service endpoint > within ESB). But I don't understand why you need to keep the protocol > information in a central place to do this??? Am I missing something or > totally lost? :-( 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. 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 (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). Regards, Eric _______________________________________________ Esb-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
