In the process of setting up the servlet-booking example for Seam, I tackled the problem of binding the JCDI Manager to JNDI on Jetty. It's just a matter of extending the javax.naming.Reference class. I attached the implementation to <a href="https://jira.jboss.org/jira/browse/WBX-31">https://jira.jboss.org/jira/browse/WBX-31</a>.<br>
<br>Should I commit this Pete? I need a decison on whether we should change the name of the class to reflect that it is an ObjectFactory and a Reference. I think internally Tomcat must create the reference automatically from the resource definition, which is why Jetty doesn't know what to do with a plain ObjectFactory.<br>
<br>...I also noticed that injection is not supported in Jetty. I'm not sure how to handle that problem, but it means no booking yet on Jetty.<br><br>-Dan<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
<br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br>
<br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>from my email. If you contact me, but don't hear back for more than a week,<br>
it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>you feel that it did not reach my attention.<br>