Greg Reddin ha scritto:
Here's what I envision for the controller: I don't think it would
really be used to change the destination of the response. I don't see
the controller as being analogous to a Struts action even though it
could be used in that way. If I wanted the controller to be used
Re-Re-Hi again
I know I am bugging you again but I have another idea.
Personally I don't like using the same tag to define
attributes in a layout page and to insert templates/definitions/strings:
I think the concept of attribute is separated from the rest (it is
somewhat like specified a "setX
hi,
my 2-cents: TilesProvider?
Regards,
Sing Chyun
--- Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> Greg Reddin ha scritto:
> > Here's what I envision for the controller: I don't think it would
> > really be used to change the destination of the response. I don't see
> > the controller as
Greg Reddin ha scritto:
On Oct 5, 2006, at 10:50 AM, Antonio Petrelli wrote:
Greg Reddin ha scritto:
On Oct 5, 2006, at 2:46 AM, Antonio Petrelli wrote:
Greg Reddin ha scritto:
But don't forget about the tag as well. It's
semantics are quite different from . How would it
be affected i
I'm wondering if maybe we should roll this tomorrow afternoon instead.
They might be working on the Internet connection on Monday, and my
tutorial is Monday afternoon. It would be nice to have it before I
leave, so that I can put it on the tutorial CDs, and cover the new S1
compatability bridge cl
The JavaBean design pattern is as good as any. Encapsulate the
functionality as an object, where attributes like the filename are
represented by get and set methods. Instantiate the object, set the
filename property, and call an execute or process method to fetch
whatever it is you are after. If i
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I'm wondering if maybe we should roll this tomorrow afternoon instead.
They might be working on the Internet connection on Monday, and my
tutorial is Monday afternoon. It would be nice to have it before I
leave, so that I can put it on the tutori
I don't have karma to XWork, so it's not something I could tag myself.
-Ted.
On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> I'm wondering if maybe we should roll this tomorrow afternoon instead.
> They might be working on the Internet con
I moved the pages regarding articles, projects, and companies to the
Struts 2 Wiki space, so that they could be maintained as a community
resource.
Right now, we're restricting editing access to the Struts 2 WW space
to individuals with a CLA on file with the foundation. In this way, we
don't hav
I'd like to add AppFuse and SourceBeat to the applications/sites page,
as well as Virtuas to the companies page. How do I go about doing
that? Does my CLA for Roller count?
Thanks,
Matt
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I moved the pages regarding articles, projects, and comp
Ted,
I am planning a beta-1 release of xwork 2.0 for tomorrow.
This will be tagged and build with a fixed version number.
Would this fit into your timeframe?
Rainer
> I don't have karma to XWork, so it's not something I could tag myself.
>
> -Ted.
>
> On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]>
Yes, it would, but the Projects is in the S2WIKI space, which is open
to anyone who opens a free CWIKI account.
* http://cwiki.apache.org/S2WIKI/home.html
-Ted.
On 10/6/06, Matt Raible <[EMAIL PROTECTED]> wrote:
I'd like to add AppFuse and SourceBeat to the applications/sites page,
as well as
Yes.
Though, does XWork the release process allow for updating the bits
from beta to stable or GA?
The reason I ask is that our 2.0.1 release will be tied to whatever
version moniker that XWork uses. If tomorrow's XWork release is tagged
as "beta", and that cannot change for that set of bits, th
On 10/6/06, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Greg Reddin ha scritto:
> Here's what I envision for the controller: I don't think it would
> really be used to change the destination of the response. I don't see
> the controller as being analogous to a Struts action even though it
> cou
XWork does use the alpha, beta, stable tagging of releases, however, the
release process is lightweight and many people have commit access. I
do, and you just need to ask Patrick to get access yourself. To be
honest, this XWork release shouldn't go 2.0.0 final, because the
documentation for X
Saturday afternoon is fine with me, however, I'll be at ApacheCon
already, but I'm sure there will be internet access somewhere. My only
concern, as Wendy said, is to have XWork rolled first.
Don
Ted Husted wrote:
I'm wondering if maybe we should roll this tomorrow afternoon instead.
They mi
ve different levels of 'quality' so to speak. If you
have an experimental plugin, that's no reason to downgrade the core.
Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
a fixed version number (such as 20061006-SNAPSHOT) so that future
snapshots of Ti
On Oct 6, 2006, at 2:27 AM, Antonio Petrelli wrote:
Greg Reddin ha scritto:
Here's what I envision for the controller: I don't think it would
really be used to change the destination of the response. I don't
see the controller as being analogous to a Struts action even
though it could b
the core.
Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
a fixed version number (such as 20061006-SNAPSHOT) so that future
snapshots of Tiles 2 don't break Struts 2.0.1 for Maven users.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Oct 6, 2006, at 6:37 AM, Antonio Petrelli wrote:
Hmm, I can't find any of my examples of using getAsString but I
thought I'd done it like this: name="tilte"/> or something like that. I would be
perfectly fine if I could use in that way if
getAsString goes away. So I guess my answer t
ncy on a beta. But, that's just me. It's a majority vote.
Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
a fixed version number (such as 20061006-SNAPSHOT) so that future
snapshots of Tiles 2 don't break Struts 2.0.1 for Maven users.
I&
Maybe we need and to
handle the 2 types specifically instead of one to
handle them generically.
I don't know. Having used Tiles for a while, I'm used to the way
things are. It doesn't bother me to use the same overloaded tag in
two different ways. I'm not sure if it's confusing to t
base that integrates with a lot of different
libraries and environments.
Don
Personally, I'm not going to vote GA on a set of bits with a
dependency on a beta. But, that's just me. It's a majority vote.
Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
a fix
on have different levels of 'quality' so to speak. If you
> have an experimental plugin, that's no reason to downgrade the core.
>
> Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
> a fixed version number (such as 20061006-SNAPSHOT) so that future
&
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easily manage a codebase that integrat
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Saturday afternoon is fine with me, however, I'll be at ApacheCon
already, but I'm sure there will be internet access somewhere. My only
concern, as Wendy said, is to have XWork rolled first.
Tell you what. Check out the Internet access, and if
Sounds good. I'll be online on MSN, AIM, GTalk, etc. Also, you can
call my cell.
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Saturday afternoon is fine with me, however, I'll be at ApacheCon
already, but I'm sure there will be internet access somewhere. My only
c
Agreed.
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easil
perimental plugin, that's no reason to downgrade the core.
>
> Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
> a fixed version number (such as 20061006-SNAPSHOT) so that future
> snapshots of Tiles 2 don't break Struts 2.0.1 for Mav
On 10/6/06, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Greg Reddin ha scritto:
> Here's what I envision for the controller: I don't think it would
> really be used to change the destination of the response. I don't see
> the controller as being analogous to a Struts action even though it
> co
or
>> > doesn't seem to be working out all that well. Different parts of the
>> > distribution have different levels of 'quality' so to speak. If you
>> > have an experimental plugin, that's no reason to downgrade the core.
>> >
>> > S
y on a snapshot of Tiles 2, so by that
>> > logic you're stuck at Alpha for Struts 2.0.1.
>> >
>> > This policy of grading a release at the lowest common denominator
>> > doesn't seem to be working out all that well. Different parts
of the
>>
Right now, I count 12 Struts 2 JARs, plus struts2-all, 9 of which are
plugins. For a quality vote, I'd expect we could just list them all
and let people break out JARs in a different grade s. For example,
+1 GA
struts2-core
struts2-toolbox
struts2-config-browser-plugin
struts2-sitemesh-plugin
st
Works for me.
Don
Ted Husted wrote:
Right now, I count 12 Struts 2 JARs, plus struts2-all, 9 of which are
plugins. For a quality vote, I'd expect we could just list them all
and let people break out JARs in a different grade s. For example,
+1 GA
struts2-core
struts2-toolbox
struts2-config-br
Has anyone volunteered to work on the XWork docs?
The XW2 docs aren't any better or worse than the XW 1.1 docs, and I
believe that release series was getting the "ready for prime time"
stamp.
Is anyone besides Struts 2.0.x trying to use XWork in production? Is
there even an XWork forum any more?
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easily manage a codebase that integrat
Try this: mvn clean install site -P
xwork,plugins,apps,all,itest,pre-assembly
You don't need core, and I put the toolbox module in the default profile
(there was no toolbox profile).
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymo
Hmm...could Struts 2.0.1 go GA...I hadn't really thought about it
before. For me, the main thing that GA does is mean that you can't
screw with the API anymore in that branch. Therefore, if we needed to
do anything significant, we'd have to do it in a new branch, and put the
old API through t
Well, we wouldn't want to *break* the API in the same release series,
since that's what a release series is suppose to mean. If we want to
break the API, we should go onto the next series (2.1 or 3.0). Though,
if we were to break the API, we'd also break WW2 compatibility, and
that's suppose to be
Yeah, sorry, that is what I was trying to say - I'm fine with freezing
the API here, pushing future improvements into 2.1 or 3.0. I think we
are 100% on the same page here :)
Let's get this puppy rolled!
Don
Ted Husted wrote:
Well, we wouldn't want to *break* the API in the same release ser
Yep, that does it!
-Ted.
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Try this: mvn clean install site -P
xwork,plugins,apps,all,itest,pre-assembly
You don't need core, and I put the toolbox module in the default profile
(there was no toolbox profile).
Don
Ted Husted wrote:
> On 10/6/06,
41 matches
Mail list logo
