+1
--
James Mitchell
678.910.8017
On Oct 23, 2006, at 8:21 PM, Ted Husted wrote:
Late last week there were issues with Minotaur's RAID. It survived the
move to Portland, but I don't know if it's back up to snuff yet.
It's only our first S2 beta, but should we submit 2.0.1 for mirroring
to
On 10/23/06, Ted Husted <[EMAIL PROTECTED]> wrote:
Late last week there were issues with Minotaur's RAID. It survived the
move to Portland, but I don't know if it's back up to snuff yet.
It's only our first S2 beta, but should we submit 2.0.1 for mirroring
to take some of the heat off Minotaur?
+1
Ted Husted wrote:
Late last week there were issues with Minotaur's RAID. It survived the
move to Portland, but I don't know if it's back up to snuff yet.
It's only our first S2 beta, but should we submit 2.0.1 for mirroring
to take some of the heat off Minotaur?
-Ted.
-
Late last week there were issues with Minotaur's RAID. It survived the
move to Portland, but I don't know if it's back up to snuff yet.
It's only our first S2 beta, but should we submit 2.0.1 for mirroring
to take some of the heat off Minotaur?
-Ted.
Sorry, I'm not being clear.
A GA tag on a distribution in the 2.0.x series will have no affect on
the new API. The API is marked optional, and work can continue, and
further distributions made in the 2.0.x series, regardless of how much
work is, or isn't, being done. We had several GA release in
Whether we finalize the API or scrap it for GA doesn't really matter to
me. What concerns me is the fact that the state it's in right now is
rather confusing to the developer.
Once I get through a few tiles and other issues I'm working with right
now, I'll be willing to dive into the API stuf
Or, jump in and help with the new API. It's been a work in progress
for some time now.
-Ted.
On 10/23/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
Excellent, I'm glad I asked. I'll just let it be for now. . .
David
Don Brown wrote:
> Talk to Bob Lee. He is in the middle of creating a new
Let's see. The API is already being used to an extent, but I believe
there is remaining work to do. The 2.0.1 distribution is already in
its final form. The only question is the quality grade. Right now,
it's heading toward beta, and it will probably be stuck there since it
has a dependency on XW
The API is there, but I don't believe it is fully implemented yet.
Don
Eric Molitor wrote:
Somewhat related (but mostly not)
What parts (if any) of the new API (The bob_lee_api) will be in 2.0.1
(final)?
Cheers,
Eric
On 10/23/06, Rene Gielen <[EMAIL PROTECTED]> wrote:
[ X ] +1 Be
Excellent, I'm glad I asked. I'll just let it be for now. . .
David
Don Brown wrote:
Talk to Bob Lee. He is in the middle of creating a new API that would
replace how Struts 2 apps currently interact with the framework. In
that work, he is creating new Struts interfaces, many of which simply
Somewhat related (but mostly not)
What parts (if any) of the new API (The bob_lee_api) will be in 2.0.1 (final)?
Cheers,
Eric
On 10/23/06, Rene Gielen <[EMAIL PROTECTED]> wrote:
[ X ] +1 Beta grade for 2.0.1 "all"
Regards,
Rene
---
[ X ] +1 Beta grade for 2.0.1 "all"
Regards,
Rene
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This was with 0.3.1 which is the current release. I posted a message on
their mailing list.
musachy
Don Brown wrote:
Have you tried this with the Dojo 0.4 release? Any reason we
shouldn't upgrade to it?
Don
Musachy Barroso wrote:
Would something like this include all the current functional
Ted Husted wrote:
Excellent, with my +1 beta, that makes three binding and two
supporting votes.
Unless there is a rash of -1s over the next day, I'll make the user
list announcement on Monday.
Meanwhile, are we close to a stable XWork 2 release? I believe a
stable XWork 2 is the only thing ke
Have you tried this with the Dojo 0.4 release? Any reason we shouldn't
upgrade to it?
Don
Musachy Barroso wrote:
Would something like this include all the current functionality in
BindDiv? (events for stop/start timer, refresh, start after a delay,
advisor via dojo's "handler" property). Thi
Talk to Bob Lee. He is in the middle of creating a new API that would
replace how Struts 2 apps currently interact with the framework. In
that work, he is creating new Struts interfaces, many of which simply
wrap xwork ones so that a Struts 2 application wouldn't be tied to or
even know about xw
Both the API and the Core modules have defined the Aware interfaces
(RequestAware, ResponseAware, and ParamaterAware). Only the versions in
the core module are actually used by the interceptor.
I would suggest that we do one of three things:
1) Remove the interfaces defined in org.apache.stru
Is it possible to change the Struts 2.0.1 pom so it loads xwork from
repo1.maven.org instead of people? I just started getting the
following error from CruiseControl today. I'm guessing this is caused
by the Struts pom, but I could be wrong.
[INFO] Installing
/opt/openlogic/blueglue/cruisecontr
Excellent, with my +1 beta, that makes three binding and two supporting votes.
Unless there is a rash of -1s over the next day, I'll make the user
list announcement on Monday.
Meanwhile, are we close to a stable XWork 2 release? I believe a
stable XWork 2 is the only thing keeping us form a a GA
Would something like this include all the current functionality in
BindDiv? (events for stop/start timer, refresh, start after a delay,
advisor via dojo's "handler" property). This way BindDiv will be easier
to maintain (dojo's ContentPane + timer) and the Tab widget can be
deleted (doesn't add
+1 for "beta"
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=46988&messageID=95481#95481
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Hmm, I forgot something until I went to implement this approach. . .
It will be nearly impossible to avoid accessing the
TilesApplicationContext in order to create the TilesRequestContext
unless we change a couple of things. The reason is that we currently
provide access to factories through
Excuse my dropping in the matter...
I am not so experienced on the versions of the various jars, but I have got the
same problem with struts custom validator, tiles ecc...
my question is:
is it possible to raise the commons validator version to solve this problem and
not to raise also the struts
23 matches
Mail list logo
