I changed the JIRA version to 2.0.0 and have started to pair down the
actual tickets we are signing up to resolve for 2.0.0. Please go
through the list of those improvements moved to Future and see if there
are any you'd be willing to tackle for this release. Also, I'll be
moving items from o
Joe - Thanks for the detailed reply. While supporting Spring integration
is very important with Strecks, I took the decision to avoid using
Spring to configure the framework extensions - I've wanted to limit
dependencies to those already present in Struts.
Regards,
Phil
Joe Germuska wrote:
> I looked at how to make that change, but I think we
> still need to do some work
> with xwork's config. It makes heavy use of this
> XWorkStatic class with static
> retrieval methods. Worse, the static use creates a
> circular dependency between
> ConfigurationManager and DefaultConfiguratio
Ok, I'm open to change xwork.xml to action.xml and even make that configurable
in struts.properties. Wasn't action.xml the name of the original Struts
configuration file? That has a nice symmetry to it.
I looked at how to make that change, but I think we still need to do some work
with xwork
Thx for the tips Wendy. It is as you predicted, i have an old
xwork-1.2-SNAPSHOT.jar in my target/struts-showcase/WEB-INF/lib temporary build
directory. Doing a clean does the tricks. :-)
Thx a lot.
- Original Message
From: Wendy Smoak <[EMAIL PROTECTED]>
To: Struts Developers List
On 6/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Showcase pom.xml seems to indicate a dependency on struts-core-2.0-SNAPSHOT,
and struts-core's pom.xml indicate dependency on xwork-2.0-SNAPSHOT, i wonder why
xwork-1.2-SNAPSHOT.jar is included in it.
mvn clean
mvn install -X
I tried this
On 6/9/06, tm jee <[EMAIL PROTECTED]> wrote:
When building showcase war file using maven, it seems that
xwork-1.2-SNAPSHOT.jar is being included in /WEB-INF/lib and so is
xwork-2.0-SNAPSHOT.jar. It should only include xwork-2.0-SNAPSHOT.jar i guess.
Showcase pom.xml seems to indicate a depend
created a jira issue at http://issues.apache.org/struts/browse/WW-1336
- Original Message
From: tm jee <[EMAIL PROTECTED]>
To: dev@struts.apache.org
Sent: Friday, 9 June, 2006 9:50:03 PM
Subject: [action2] showcase resources
Showcase resource needs to be in a separate directory for maven
When building showcase war file using maven, it seems that
xwork-1.2-SNAPSHOT.jar is being included in /WEB-INF/lib and so is
xwork-2.0-SNAPSHOT.jar. It should only include xwork-2.0-SNAPSHOT.jar i guess.
Showcase pom.xml seems to indicate a dependency on struts-core-2.0-SNAPSHOT,
and struts-co
On Jun 9, 2006, at 3:10 AM, Antonio Petrelli wrote:
I don't think it is what you mean, because this is already there.
Can you clarify what you mean with an example?
No that's what I meant. I just never have actually used that. How
does that look on the JSP doing ? You'd think I'd
k
Showcase resource needs to be in a separate directory for maven to include them
when doing a war package.
now. eg.
apps/src/main/java/org/apache/struts/action2/showcase/validation/
contains resources like
- FieldValidatorsExampleAction.properties
- FieldValidatorsExampleAction-conversion.prop
A key problem is renaming the xwork.xml file. Last time I looked, the
token "xwork.xml" is hardwired, so we'd have to change the way OS
XWork is configured, or use a "Rube Goldberg" bootstap file.
As to the rest of it, I'm ready to let it drop, as we have other "fish to fry".
-Ted.
On 6/9/06, D
Sorry guys, I missed out xwork-conversion.xml. I should really be more careful
as this is the 2nd time within 2 months. :-P
I'll commit in the missing file asap.
Thx for looking into it, Don and Wendy. Owe you guys one . ;-)
regards
- Original Message
From: Don Brown (JIRA)
Gary VanMatre ha scritto:
Clay symbols are similar to the "put"s. The difference is that they are pushed to all nested definitions and not just a single level. They are scoped from the outer to the inner. They can be overridden at any level.
This would be nice to have in Tiles, though I thi
Greg Reddin ha scritto:
Yep, that's come up before. Personally, I don't like the idea. Think
about how complicated that could become with nested, nested defs.
I don't see it so catastrophic. In certain cases it is better to see an
entire structure as a tree instead of a lot of "see definitio
15 matches
Mail list logo