Thanks... you're absolutely right. Works great.
On Thu, Mar 26, 2009 at 9:40 AM, Scott Ferguson <f...@caucho.com> wrote:
> On Mar 25, 2009, at 7:27 PM, Jeff Schnitzer wrote:
>> Is there a compelling reason why we must define our beans and services
>> in resin-web.xml? Will this continue to be the case going forward in
>> Resin 4.0?
> You don't need to define the beans in resin-web.xml. You do need a
> marker file like META-INF/beans.xml or META-INF/ejb-jar.xml.
>> It's a minor nuisance, yes, but... it's nice to add a class to the
>> project, annotate it with @Service or @Stateless or whatever, and have
>> it automatically detected as a bean. JBoss works this way :-)
> If you have a META-INF/ejb-jar.xml, Resin should already pick this up.
> -- Scott
>> This actually has some impact on the SubEtha code that Scott and I are
>> working on. SubEtha plugins automatically register themselves with
>> the container when you drop a jar file containing them into the
>> server. This makes it easy for minimally java-savvy people to write
>> some code, drop it in the container, and have it immediately
>> available. Adding xml files complicates the matter.
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list