That's great news, Brian. I'll give it a try on the JPA MailReader,
which is using the CodeBehind plugin right now, and see if it's, well,
plug and play :)
-Ted.
On Dec 29, 2007 12:41 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> I have the first rough version of the convention plugin checked
I think they've backed out the feature, I've just added a comment to WW-2308
and all seemed OK and it's showing up as attached to the issue.
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: 03 January 2008 19:38
To: Struts Developers List
Subject: Re: Struts JIRA read
The backstory is that we proposed bringing over WebWork as Struts 2,
we decided to leave XWork at OpenSymphony. One reason is that most of
us like the strong separation between XWork and Struts 2, so as to
keep HTTP from creeping back in the core API. Another reason is that
incubating a large codeb
If the codebases are to remain separate, I'd like to suggest that all
Struts2 committers are added to XWork. The reason that I say that is the
codebases are so coupled. If you look through comments in XWork, you
start to see more references directly to Struts2. Struts2 won't function
unless X
Not every Struts committer works on Struts 2, and not every committer
working on Struts 2 wants to work on XWork too. It's a security
exception to give people accounts that they haven't requested and may
never use.
AFAIK, to date, anyone here who wanted access to XWork has gotten it
without any tr
