[seam-dev] laying the tracks for Seam 3

[Dan Allen]

I recognize it's a bit compulsive, but I've added a section on the Seam wiki
about Maven POM guidelines. I am recommending an order of elements to
follow. The actual order is really not important. What is important is that
we are consistent across projects/modules. POM files have a ton of XML and
it is much easier to find stuff when you can rely on where it is located in
the document.

http://seamframework.org/Community/GettingStartedDevelopingTheSeamFramework#H-MavenPOMGuidelines

I'll bring the Seam POMs inline, but as you add new ones, please try to
honor the order. As always, if you have an objection to the order, please
propose a change to this guideline.

-Dan

On Tue, May 5, 2009 at 10:42 AM, Pete Muir <pmuir at redhat.com> wrote:

> Naming sounds good :-)
>
>
> On 5 May 2009, at 15:34, Dan Allen wrote:
>
>  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.
>>
>> 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?
>>
>> 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.
>>
>> -Dan
>>
>> On Thu, Apr 23, 2009 at 6:03 PM, Dan Allen <dan.j.allen at gmail.com> wrote:
>> After a late night, I'm happy to announce that I have all of the following
>> deployments working for examples.
>>
>> packaged EAR to JBoss AS using jboss plugin (booking)
>> exploded EAR to JBoss AS using antrun plugin (booking)
>> packaged WAR to Tomcat using tomcat plugin (servlet-booking)
>> exploded WAR to Tomcat using tomcat plugin (servlet-booking)
>> in place WAR w/ embedded Jetty using jetty plugin (servlet-booking)
>> in place WAR w/ embedded Tomcat using tomcat plugin (servlet-booking)
>>
>> 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.
>>
>> Now, for more functionality and tests ;)
>>
>> -Dan
>>
>>
>> On Wed, Apr 22, 2009 at 7:01 PM, Dan Allen <dan.j.allen at gmail.com> wrote:
>> 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...
>>
>> 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.
>>
>> The scaffolding works beautifully on Tomcat. I'm going to working both the
>> booking and servlet-booking projects as I fill out the functionality.
>>
>>
>> -Dan
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://in.relation.to/Bloggers/Dan
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a
>> week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters.  Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>>
>>
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://in.relation.to/Bloggers/Dan
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a
>> week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters.  Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>>
>>
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://in.relation.to/Bloggers/Dan
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a
>> week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters.  Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>>
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
>


-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20090505/a38e30e4/attachment.html