On 25-09-12 06:11, Greg Trasuk wrote:
I'm afraid I've given the wrong impression, due to e-mail's lack of
intonation. "Don't like" is too strong a phrase. It's more like the
No problem. I don't like spinace can still mean you will eat it, because
of the vitamins. But you wont in this case.
For service definition, I'm thinking something like this (starting from
your DemoServiceImpl class):
@Service(exporter="defaultExport", join="defaultJoin")
@NameEntry("DemoService")
@ServiceInfo(name="DemoService", manufacturer="Apache Software
Foundation",
model="demo-101", version="1.0")
public class DemoServiceImpl
implements DemoService
I like annotations, but feel that using this much will cause friction by
the configuration file users (by choice of by conviction). You probably
read Dan's reply in the mean time.
My thought is that you'd package one or more of these classes in a jar
file (service archive, or ".sar"?) and deploy it to the service
container. Much like in EJB3, the container would scan the jar file for
deployable services, and export, then register them in the appropriate
I like the idea of 'dropping them into a container', but would like a
separation between the dropping/scanning part and the actual service
startup, in such a way that programmed configuration/embedding is still
possible.
Gr. SImon
