Interesting; I've been thinking in terms of annotations on either the service interface, or on the service implementation, not in the XML. I'm hoping to move the focus in HiveMind back to the Java code, just as we have done in Tapestry (using annotations instead of XML).
On 1/26/06, Liebig, Stefan <[EMAIL PROTECTED]> wrote: > > > Hi, > > I would like to have the possibility to annotate HiveMind constructs similar > to > annotating Java constructs. Additionly it would be necessary to enumerate > all > available (visibel) sertvice points. > With that I would have my special Hessian servlet which collects all as > ´web-service´ > annotated services and would make them available under the specified url. > With that > the web.xml would only contain the Hessian servlet performing the proper > delegation. > E.g.: > > <service-point id="Test" interface="de.test.Test"> > <annotations> > <annotation key="web-service" value="true"/> > <annotation key="url" value="/appxx/test"/> > </annotations> > > <invoke-factory> > .... > </invoke-factory> > </service-point> > > Within ServicePoint the annotations could be represented as a > Map/Properties. > And the Infrastructure could have a getServicePoints( Module module ) with > module==null retrieving all service points. > > Stefan > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
