Hi Jason I expect others in the project who are closer to some of the non web services bindings will have their own views on this. Am setting the ball rolling by asking some questions. See below.
As a general rule I would try and start simple so I wouldn't necessarily dive into thinking about new bindings, policies etc. in the first instance. Have a go with your front end and an SCA service behind it and then expand from there. Even with this you might be facing the binding/databinding question depending on you service interfaces but lets break the problem down and see what the simple steps are. Regards Simon On 10/18/07, Jason Clark <[EMAIL PROTECTED]> wrote: > > Hello all. I am currently working on transitioning the project I am > working > on from it's current framework to Tuscany. It's already services based, so > that is making things easier. Currently, a custom formatted xml message is > posted through tomcat. When the servlet recieves it, it does some custom > authentication against an LDAP server and then forwards the message to the > appropriate service for processing. It's very much a roll your own > solution > right now. Is service selection a function of authentication or is this based on some information in the message? What's the protocol between the servlet in Tomcat and the service? Is it the sample XM message? What does the service interface look like, i.e. the service that the servlet forwards to? I would like to better leverage existing technologies and Tuscany > capabilities to improve this process. I need to continue to use the > message > format I'm using. Would I need to write a new binding since it's not a > format supported by JSON or WS? Or, would I keep doing what Im doing with > my > current services just now registered on a domain and the servlet receiving > the message continue with the custom validation then use the domain the > fetch the appropriate service to pass the message along to? A new binding is certainly a possibility. What it sounds like you need is a some kind of REST binding to be able to "post" an XML document to a service "post" method. There are a couple of bindings that deal in arbitrary data, I.e. binding.http and the feed bindings binding.rss and binding.atom. None of these fit the bill directly but they we could potentially tailor one. Raymond has been doing some work recently on building a demo showing how XML can be handled (demo/xml-bigbank). This would be worth a look, for example, you can see in the AccountData service how he's dealing with an XMLStreamReader. Venkat has been looking to policy intents to separate the authentication function from the details of the bindings. You can see an example of this in the helloworld-ws-service-secure and helloworld-ws-reference-secure samples. This might be the way to go in terms of associating LDAP based authentication with any bindings you use. That would be a nice addition to Tuscany in it's own right;-) Also, how would I go about writing a TCP/IP window into the app? Just write > my own, or is there some support for this in Tuscany somehow? What do you mean by a TCP/IP window? Socket? Where would that need to provide access to? Pardon my ignorance. I don't quite know all the capabilities and best > practices for dealing with this kind of problem, so I figure it's faster > to > ask, even it my questions don't make sense. No problem at all. It's interesting to hear about your scenario. Thanks. > > Jason. > > > > > > > > >
