| [metro-dev] Request for Help in Experiential Survey |
Hi,
Besides having selected and studied JAX-WS and JAX-RS APIs and the corresponding RIs--Metro & Jersey--for my future professional development work, I am also a researcher in the area of formal models and metrics for service-oriented systems. A deep understanding of these two APIs helped me formulate an improved formal model and some novel metrics for service-oriented systems as part of my Ph.D. work.
I would be highly grateful and much obliged if some of you can help in experientially validating (e.g., expert/professional survey) in the form of sharing some design and code artifacts ( at least skeletal) and providing answers/explanations. I understand the members here are not obliged to answer such queries. I would be happy to share my work and findings once I complete my academic requirements.
1. Given a JAX-WS service, how would you relate terms “inside of a service” or “internal to a service” and “outside of a service” or “external to a service”?
2. Based on your knowledge and experience, would you imagine/visualize a JAX-WS web service as basically the main thread and explicit child thread(s), if any, of the endpoint class with all incoming coupling via service interface and all outgoing coupling emanating from these threads? If possible, kindly provide as long an explanation as you would wish to give.
3. Have you ended up coding an atomic endpoint class—either fresh development or one exposing some legacy code—that had a number of operations such that various pairs of operations either shared a few utility/dependency modules/classes or none? By atomic, we mean, a class that does not invoke any other service. On second thoughts, did you split it up as separate endpoint classes? If possible, kindly provide as long an explanation as you would wish to give.
Thanks for reading!
Regards
Rupinder Singh