On Tue, May 12, 2009 at 6:16 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: Even more bizarre, the description in the pom.xml is: "JBoss EL is a extended EL implementation, distributed with Seam" Okay, so why isn't it just a Seam module then? The counter-argument is that Spring Web Flow uses JBoss EL, so there are other uses for it. So maybe we should recognize it as being something separate from Seam. -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.

On 12 May 2009, at 23:15, Dan Allen wrote: It's never been made a top level project. I altered the numbering scheme at some point to follow EL spec numbering, not Seam numbering. Really, we should migrate to the EL RI as soon as it has the features we need. It's maintained by us. -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete

On Mon, May 18, 2009 at 2:16 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: Sorry, I was reading that wrong. The quirky syntax was only a suggestion made in this post http://blogs.sun.com/kchung/entry/jsr_245_mr_part_i to deal with method overloading. The default is consistent with what JBoss EL offers. -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.

On Mon, May 18, 2009 at 2:33 PM, Pete Muir <pmuir(a)redhat.com&gt; wrote: Here's what I suggest. Let's make the call as we mature the seam-el module in Seam 3 a bit more...see where it goes and see what the community feedback is. So far, I see this as a cornerstone module for two reasons: a) working with the EL API is still a pain (and seam-el eases a lot of that pain) b) we need a more powerful EL than what the standards body is willing to allow A powerful EL makes it so much simpler to develop an application because you don't have to jump through hoops to get at data, especially against built-in components. For instance, JBoss EL supports static methods, and I would like to see it be able to reference enum constants directly. Let's keep the option on the table and I'll maintain it if it continues to have the influence that I perceive it does. -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.