On Fri, Oct 15, 2010 at 1:42 PM, Emmanuel Bernard <emmanuel@hibernate.org> wrote:

Why do you want to rename exactly? Has the project being expanded or shifted?

The motivation behind Seam Catch is that it's provides the "try catch" block for your application (or at least requests). Focus on the "catch" part, which is where its work begins.

The suggestion of the term "control" or "controller" led me to another idea, routing (or router). I think it's more accurate to say that the work the module does is that it first catches (or traps) the bubbled exception, then it routes the exception. However, exception-routing (or exception-router) is just as long as exception-handling. But I like routing better.

We were also using the packaging to help us select the right choice.

org.jboss.seam.exception.handling

org.jboss.seam.exception.routing

org.jboss.seam.catch :)

-Dan

I personally like explicit names

Seam Exception Control(er) SEAMEXCTRL

On 15 oct. 2010, at 19:26, "Lincoln Baxter, III" <lincolnbaxter@gmail.com> wrote:

Actually that is kind of "Catchy"...

Seam Catch
Seam Handle
Seam Except

On Fri, Oct 15, 2010 at 12:57 PM, Jason Porter <lightguard.jp@gmail.com> wrote:

While trying to come up with a good name for the JIRA project I got a little hung up and asked for ideas on IRC. Dan had mentioned Seam Catch. It kinda stuck and seems like a good name. WDYT?

Sent from my iPhone
_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"

_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev