I just checked in a new example to Seam 3, servlet-permalink. It is a very simple blog with comments (you can't post a new entry yet). This example is very important because it demonstrates the view parameters (i.e., page parameters) that Red Hat (Pete and I) contributed to JSF 2 (hence the name permalink). It of course uses JSR-299 beans as well, but no database.<br>
<br>I am moving forward with the convention of prefixing WAR projects that target a servlet environment with servlet-. Thus, I'm thinking about having a cooresponding prefix for Java EE projects (EARs). I propose the prefix jee-. So I may change booking to jee-booking. Thoughts?<br>
<br>Of course, there may be other prefixes in the future like wicket-booking and groovy-booking. I just want the example name to help poeple understand what it is demonstrating. Just trying to find the best approach.<br><br>
-Dan<br><br><div class="gmail_quote">On Thu, Apr 23, 2009 at 6:03 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
After a late night, I'm happy to announce that I have all of the following deployments working for examples.<br><br>packaged EAR to JBoss AS using jboss plugin (booking)<br>exploded EAR to JBoss AS using antrun plugin (booking)<br>
packaged WAR to Tomcat using tomcat plugin (servlet-booking)<br>exploded WAR to Tomcat using tomcat plugin (servlet-booking)<br>in place WAR w/ embedded Jetty using jetty plugin (servlet-booking)<br>in place WAR w/ embedded Tomcat using tomcat plugin (servlet-booking)<br>
<br>Everything is done with native Maven 2 except for the exploded EAR to JBoss AS. I made the antrun configuration as elegant as possible to support that use case, and I think it works out nicely. Instructions are in the readme.txt. The instructions are still missing some details, but I should have all gaps filled in soon.<br>
<br>Now, for more functionality and tests ;)<br><font color="#888888"><br>-Dan</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Apr 22, 2009 at 7:01 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I just checked in the scaffolding for the servlet-booking example, a WAR which will target Tomcat and Jetty (and perhaps even JBoss AS once I get the profiles setup). In the process, I believe I solved the issue of binding the JCDI Manager to JNDI in Jetty. What's really strange though is that once I get the Manager, it doesn't find any beans on my classpath. But that might have to do with...<br>
<br>Jetty is still in a crippled state. First, JSF 2 does not appear fully on Jetty. If I use the @ManagedBean annotation, the bean cannot be found. If I used the @Named annotation, same thing. Both examples work unchanged on Tomcat. So I'm not sure yet. Going to contact the Mojarra team.<br>
<br>The scaffolding works beautifully on Tomcat. I'm going to working both the booking and servlet-booking projects as I fill out the functionality.<div><div></div><div><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" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br><a href="http://in.relation.to/Bloggers/Dan" target="_blank">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>
</div></div></blockquote></div><br><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" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">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>
</div></div></blockquote></div><br><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>