Actually, the result would be something like dojo:div since the new
tag library couldn't share the same prefix (except in JSP, of course).
Technically, I suppose the Velocity directives could pick whatever name
they want, but you'd want to be consistent.
Don
Patrick Lightbody wrote:
+1
I
First of all Happy New Year to everyone! and then a bit of a
philosophical email - something related to previous post by Rainer and
something that bothered me for the last couple of months.
Before the merge, I was spending a lot of my spare time contributing
to WW and on the XWork side
To fight philosophy with philosophy ;), the goal of Struts 2 has been
pretty much the same since we started: to simplify web development to
create a more developer-friendly framework. We've been following the
Struts Ti plan [1] roughly since late 2005. WebWork was brought on
board as it was
Happy new year guys. :-)
WebWork just like any other open-source project follows the open-source
spirits. It is very much driven by the community itself. Features are often
implemented when they are substantial enough, it doesn't matter if it
originated from users, commiters or the project
On 12/31/06, Rainer Hermanns [EMAIL PROTECTED] wrote:
Thoughts?
I think the way to address any problems with XWork involvement is to
followup on Patrick's post and create the usual project
infrastructure: A user list, a dev list, and a commits lists for the
automatic posts from Subversion,
On 1/1/07, Alexandru Popescu [EMAIL PROTECTED] wrote:
Before the merge, I was spending a lot of my spare time contributing
to WW and on the XWork side along with Rainer, Jason, and occasionally
a couple of more guys. The direction was clear for everybody and
everybody knew where we are heading
I am willing and spending lots of my free time on Struts 2, XWork and
(still) WebWork 2.2.X. to bring this projects to high quality products as
lots of the other developers are doing, but I need more feedback to get
more of the envolved developers in. There are some open issues in Jira
where I
Yeah, but given the problems that most people have at some stage of
debugging with the tags, I thought there would be more traffic ;-)
/Ian
Mitchell James wrote:
That's the wonderful or terrible thing about successful OSS projects,
you are kidding yourself if you think even 5% of the users
Macro snippet errors:
http://struts.apache.org/2.x/docs/validation.html
http://struts.apache.org/2.x/docs/type-conversion.html
http://struts.apache.org/2.x/docs/localization.html
http://struts.apache.org/2.x/docs/action-chaining.html
http://struts.apache.org/2.x/docs/interceptors.html
Thanks for pointing these out, but please feel free to take the next
step and correct them. By editing the original Confluence pages, found
at http://cwiki.apache.org/confluence/display/WW, these snippet errors
can be corrected.
The reason so many are broken is that the pages were pointing
Tonight I was looking at abstracting away OGNL from xwork. (I was
pretty far before I gave up for the night, about a half dozen OGNL
references in xwork that I'll have to look at a little closer) So I
took a look at what it would take to integrate MVEL. First, the lack of
javadoc is a
11 matches
Mail list logo
