Jason +1. That would really make XWork much easier to unit test.
I can help with that part of the work.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=28543&messageID=56542#56542
Not sure about the requirements you're talking about, but it should make almost
everything easier when programming to the config APIs, so I'd hazard a guess of
"yes".
-
Posted via Jive Forums
http://forums.opensymphony.com/thread
Agreed. Would this make it easier/possible to have a Properties-based config
and/or support wildcards?
Don
Bob Lee wrote:
That would be awesome.
Bob
On 5/1/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
Speaking of which, I was planning on doing some work on XWork
configuration refactoring
That would be awesome.
Bob
On 5/1/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
Speaking of which, I was planning on doing some work on XWork configuration
refactoring and making it runtime changeable along with removing some
singletons on my flights to SFO for JavaOne... Any objections?
Speaking of which, I was planning on doing some work on XWork configuration
refactoring and making it runtime changeable along with removing some
singletons on my flights to SFO for JavaOne... Any objections?
-
Posted via Jive Fo
TED]>
To: Struts Developers List
Sent: Monday, May 1, 2006 2:40:31 PM
Subject: Re: RoughSpots ramp down
I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at
the JavaOne BOF, we can discuss the tickets and their fix schedules fur
rd to type it all out. Can
we discuss fix schedules in JIRA / on this list? Teleconference? :-)
- Original Message
From: Don Brown <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Monday, May 1, 2006 2:40:31 PM
Subject: Re: RoughSpots ramp down
I agree - I think we should
+1
On 5/1/06, Don Brown <[EMAIL PROTECTED]> wrote:
I agree - I think we should break this document down into JIRA tickets and
track the discussion there. When we meet at
the JavaOne BOF, we can discuss the tickets and their fix schedules further.
Don
Patrick Lightbody wrote:
> I propose that
I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at
the JavaOne BOF, we can discuss the tickets and their fix schedules further.
Don
Patrick Lightbody wrote:
I propose that everyone get their last two cents in to the RoughSpot
I propose that everyone get their last two cents in to the RoughSpots document
today so that we can ramp down the discussions and then pick apart each issue,
decide which we want/can attack right now, and come up with proposals.
10 matches
Mail list logo