Oh, but one question: I assume if one were to make JSP 2.0-style tags (.tag
files) they couldn't be bundled as a plugin, right?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=135292&messageID=207484#2
+1 for sure!
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=135292&messageID=207483#207483
-
To unsubscribe, e-mail: [EMAIL PROTECT
I would be happy to help make this happen. Someone just needs to provide me
with access to the zone, right?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=73585&messageID=138342#138342
-
Yes, this was something I was not pleased about one bit. Fortunately, there are
tricks you can use to disable this logic and stick w/ 2.0 or even 1.2-style
logic. I don't recall the specifics, but I think they are something along the
lines of which doctype you use in web.xml. You may also be abl
Probably wouldn't be a bad idea to get a standalone instance of Forums 5.5
(coming out soon) set up for Struts. Email me if you want to get that going, or
if you can provide me instructions for setting it up (zone login info, etc).
-
Seems like bringing them in would make sense, especially if the people who are
managing them say so. Since I don't experience the pain, I certainly can't vote
-1. So I'm a +0-1 :)
-
Posted via Jive Forums
http://forums.opensympho
Yes, I believe QuickStart has since been removed in favor of encouraging "mvn
jetty:run" or something similar.
The file has been removed.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=70352&messageI
Ted,
What "annotations" are we talking about? The annotations used for
configuration, or something else? Pardon my ignorance on this, I just want
clarification.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?
There a lot of reasons. If you really want to know, try searching the webwork
mailing list/forum archives, or ask here and I'll try to find time to explain.
Otherwise, just keep trying to solve your problem and avoid using the Servlet -
it's not recommended :)
---
+1 for GA
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=65672&messageID=125490#125490
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
+1 for GA - I'm using it in HostedQA now and it is working great.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=62617&messageID=121464#121464
I use all of these with HostedQA.
> It's exciting to see that we've added a number of
> brave, new features
> since Struts 2.0.1.
>
> * codebehind plugin
> * zero configuration
> * REST-ful URLS
> * direct results
>
> As implemented, these features seem solid and useful,
> but I wonder if
> anyo
Tom,
How is this coming along? I imagine that some of this work would also relate to
the ActionMapper interface, since it does have some responsibilities for
rendering out URLs. Keep us posted.
-
Posted via Jive Forums
http://for
Ted,
Your suggestions all sound very reasonable. Rainer and I would be happy to help
set this up (I can do the forums/infrastructure, and I'm sure Rainer can help
by giving releases more compatible version numbers in the future).
---
+1
I think in general the concept of "themes" for the AJAX stuff was a mistake.
Instead, let's do stuff like:
And make those tags part of an external plugin. That way we don't make
migration from WebWork impossible, but we also fix a mistake we made with
WebWork by trying to stuff too much f
Ted,
Making XWork a more "public" project is not a problem - we just hadn't done so
up until now due to no need.
As for the names of the releases (RC, beta, 2.0.1.1.1.1, whatever you
want...)... that is really easy to fix: just ask Rainer or whoever is doing the
release :) OpenSymphony doesn't
That should work just fine. What kind of error do you get? What happens when
you do:
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=55942&messageID=111476#111476
--
+1 for "beta"
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=46988&messageID=95481#95481
-
To unsubscribe, e-mail: [EMAIL PROTECTED
THANK YOU DON.
You said it much better than I did.
Honestly, guys, the reaction here is a little... odd. I wanted to engage the
dialog of how we might address known issues. Unless you've used the Struts 2
tags, it probably is hard to provide any real constructive feedback on this
particular s
Take a look at JXP: http://jxp.sourceforge.net/
This might be very close to the template language I have been looking for that
is JSP-like, but has the advantages that FreeMarker and Velocity provide in
that it can be loaded from the classpath. I've wanted to select something like
this as the t
Toby,
I believe Ted can provide insight here. I gave him access to the plugin source,
but I don't know what happened to it since or in what form it was installed.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa
This is really good stuff, keep working to flesh it out fully. Take a look at
the Stripes i18n/validation scopes for an example of a well-done implementation.
Also, one thing I'd note: we do default the value attribute to the evaluation
of the name attribute already, so the question is all about
Handwaving? Grab the code and fire it up. There are a few actions already set
up (Login, Logout, Register, etc).
> On 8/30/06, Don Brown <[EMAIL PROTECTED]> wrote:
> > Sure, each of these things, by themselves, could be
> debated and aren't
> > strictly necessary, but taken as a whole, they
> rep
I wonder if the maven guys released a new version of the IDEA plugin with bugs.
Were you re-running the "mvn idea:idea" command between each time you ran in to
problems?
-
Posted via Jive Forums
http://forums.opensymphony.com/thr
It works just fine. I suppose it could be its own maven module. What is the
motivation for these questions?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=42012&messageID=84084#84084
---
> > struts.core.disableDynamicMethodInvocation
>
> Is there a reason to add ".core" here?
>
Darn - you caught my attempt to very subtly imply that disabling this feature
disables something core to Struts. It certainly is in my opinion. :)
> We don't specify ".core" in any of the other property
Done.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=41565&messageID=83030#83030
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
> I think that's a fair outcome, but those URLs are a
> spurious argument. That's 2 apps, Jira and Jive, not
> a majority of all apps.
Considering that part of why WebWork is where it is today is due to
contributions and use by these companies, I'd be very wary to make anything
they do not the d
> Yes, and making "dynamic method invocation"
> switchable doesn't affect
> anyone's ability to do any of this.
Agreed.
> Could you please roll back r436991 and r436971 since
> without a switch,
> we cannot explore alternatives that don't require
> special-case code,
> nor can we suppress dynamic
I meant to do this last week - just to provide everyone with some more examples
of the ! syntax in use:
http://jira.openqa.org/secure/CreateIssue!default.jspa
http://jira.openqa.org/secure/UpdateUserPreferences!default.jspa
http://jira.openqa.org/secure/UserVotes!default.jspa
http://jira.openqa.o
Wendy,
That's fine with me - is there any way to make the maven build include those
instructions if the property isn't defined and the xwork profile is being used?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jsp
Done.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=41363&messageID=82541#82541
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
Agreed.
> On 8/25/06, Patrick Lightbody
> <[EMAIL PROTECTED]> wrote:
> > Make sense?
>
> Yes. Since the validation files are acting like
> code-behinds, being
> able to bind to a code artifact, like the method,
> does make sense to
> me. I can understand why
we should encourage people experimenting with their own
ActionMapper any time they choose. They could, for example, change ! to be "/"
so that it looks more like a path. We wouldn't want to bleed our the "!"
pattern to other parts of the application.
> On 8/2/06, P
I cannot underscore how much of a mistake this would be. I would vigorously
fight this decision to keep it off by default for a long time. I'm happy to put
more constraints on the ability to invoke methods via the HTTP request, but I
will not support turning it off by default. See my mini manife
> I'm not 100% sure how that one works... does it
> depend on "!" somehow? I've been stuck on an older
> release of WebWork for a while...
foo!bar.action is the same thing as foo.action?method:bar=whatever
It is defined in DefaultActionMapper.
-
Related to the ! thread, but a more general concept that I want to bring up and
underscore. This is my mini manifesto on why we can't treat the default options
and settings in Struts lightly. These are all my opinions, but I think they are
also fairly common sense.
Goal: It should be our goal t
> Just to step back a moment, let's be clear that the
> original
> suggestion, which stemmed from the "Rough Spots"
> discussion, was that
> we experiment with using wildcards to provide the
> same functionality
> as the "!" syntax. If that experiment provided
> fruitful, we would
> then, only only
> Following up to myself: I want to also make it
> clear
> > that I'm not opposed to changing my way of doing
> > things, but so far I haven't seen anything that
> seems
> > any better than what I'm doing now. I'm happy to
> > explain more about how the ! syntax is used with
> all
> > my forms, so
> > First off: we're *not* deprecating and removing the
> !
> > notation at this point. That is what this
> discussion
> > is entirely about.
>
> Not YET... that's what the conversation was about as
> I read it... when, not if.
It's not a "when" to me - it's an "if" and a "why" type of discussio
> I need everyone to understand this: the goal should
> be for us (the project leaders) to agree on a style
> of development using Struts that we can all feel
> comfortable recommending as the default starting
> point. For example, I think the default starting
> point should be on that encourages l
> > I guess why I don't like this mentality is that we
> > have these kinds of security holes all over the
> > place. If you expose getters or setters that are
> > unsafe in your action or _any_ of your model
> objects,
> > you can get that problem. The fact is that with
> > dynamic reflection that
Whatever Struts ends up doing, we'll also do in XWork.
> On 8/22/06, Don Brown <[EMAIL PROTECTED]> wrote:
> > I'd rather use java.util.logging than
> commons-logging, but I think both
> > are overkill for a library.
>
> Of course, our library is an extension of the XWork
> library.
>
> Do we wan
hat choice.
>
> Since teams migrating from WebWork will have to make
> other changes,
> this is the ideal time to introduce the switch, so
> that it just one
> other thing to do.
>
> -Ted.
>
>
>
> >
> > > On 8/21/06, Patrick Lightbody
> > >
OK, that all sounds good. My only request would be then: can we un-deprecate
the ! syntax and keep it on (by default), while still giving the option to turn
it off and perhaps set up a "Security conscience" page on the wiki that
catalogs all these switches?
> On 8/21/06, Patr
Sure, I agree with all of that. And I've said I'm opening to nailing this down
more with conventions and/or annotations. I'm even open to a switch to turn it
off.
What I'm not open to is just removing/deprecating it entirely without
addressing the fact that it is _widely_ used in a ton of appli
Ted,
I'm still not yet on board with removing the ! syntax until we have a solid
replacement. I don't think pointing to wildcards is enough, especially since
you would have to create a wildcard for every namespace. That is more
configuration than I'm willing to recommend to our users.
I would,
Ted,
Can you email me the changed files? I'll get them checked in once I have them
in my inbox.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37908&messageID=81289#81289
---
Any reason we can't use Maven itself to build the jars? I believe I had that
working at some point.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=40424&messageID=81288#81288
---
Awesome work, Toby!
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=40158&messageID=79981#79981
-
To unsubscribe, e-mail: [EMAIL PRO
You can always view the latest reports here:
https://struts.hostedqa.com/project/7/session/suite/list
I can set up email alerts to go to some list (which one?) as well.
And of course, just let me know if you want a HostedQA account.
---
We should give them unique sequence IDs for each form. We should never
encourage random numbers - that makes things much harder to automate for
testing, which has always been a strong point for WebWork.
Any chance you can make the change in WebWork 2.2.3 too before the release?
-
http://mail-archives.apache.org/mod_mbox/struts-commits/200608.mbox/[EMAIL
PROTECTED]
http://mail-archives.apache.org/mod_mbox/struts-commits/200608.mbox/[EMAIL
PROTECTED]
A few questions:
- What is FormButton.java? Is that new?
- Why are we rendering random numbers? Why not something more pr
Heh - well, that's how this was implemented in the first place. I wrote my own
ActionMapper. My point is that I have seen a lot of success with a combination
of ActionMapper+Convention-based-configuration, and I think we should really
think about pushing this to a broader set of users.
I think
you have a reason for deep paths, and a reason why today's simple
wildcards won't work :)
Patrick
> On 8/3/06, Patrick Lightbody
> <[EMAIL PROTECTED]> wrote:
> > Don and I talked in-depth about using wildcards to
> do the style of conventions I am
> >talk
I think you missed the main point I was trying to make, which is that the
concepts of multiple stacks is something I avoid entirely. Instead, I believe
in one stack that is capable of providing different behaviors based on
conventions.
Don and I talked in-depth about using wildcards to do the style of conventions
I am talking about, and we found that it would require a much more complex
implementation of wildcards. Don, can you add to that?
-
Posted via Jive Fo
OK, I think I see where you are coming from. I guess we are coming across a
difference of opinion, but let me explain how I would do the exact same thing:
- Like you, I would have a single action class that has multiple methods to
invoke (input, save, list, whatever)
- I would not, however, h
Jason, I have to disagree with you on this. I've written a lot of WebWork apps
and multiple aliases is rarely used (maybe 1-5% of the time for me). Perhaps
you can give the common examples you come across so that we can understand your
style better?
> > I'm not suggesting that try to make it im
> > - zero configuration (using conventions instead)
> for actions and results
>
> OK, now define the ideal conventions. :)
Heh - alright. I'll give it a stab. This comes from the conventions I've used
in WebWork for two apps (HostedQA and www.bigbark.net).
- A single package (or set of packag
To automate tests in HostedQA, just log in and import a test from Selenium IDE
or create a new one. It will get run within 30 minutes of a checkin.
HostedQA does have an import tool, so you could store the tests in HTML format
in SVN. But there isn't an automatic way to import those in (yet). I
I would think an ideal application would have the following:
- zero configuration (using conventions instead) for actions and results
- overrides possible in struts.xml, including wildcards
- result overrides via annotations if struts.xml is too verbose
- annotations for validations and type conve
Ted,
Good questions. Related to that - why is it than i18n resource bundles are tied
to the action class rather than the _view_ (the view would tend to make more
sense, I believe).
This is the kind of stuff we should clean up with Struts 2.
One thing I'd add before Jason chimes in is that you c
Wendy,
Your account is set up - I'll follow up with details by email.
I don't see the "selenium" profile in the Struts 2 poms - is this a 1.x thing
for now?
HostedQA doesn't need Selenium Core to be packaged in the webapp. It also can
import HTML files used by Selenium Core (and generated by Se
I'm close to doing it for HostedQA... I've already done the integration on a
branch, but I just haven't deployed it yet as I've been busy with other things.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threa
With the understanding that this is an issue that needs to be treated carefully
to avoid confusion, I think we should really give some serious thought to this.
As someone who _has_ actually done annotation-based result mapping (I have
setups with no xwork.xml - I can explain more if requested),
Correct, the includeParams attribute needs to be set to 'none'.
> The URL tag isn't meant to be used with a query
> string. The best way to write
> this would be:
>
>
>
> s:url>
>
> The reason is the url tag has this "includeParams"
> tag, which can automatically
> include all the query s
+1
> On 7/26/06, Don Brown (JIRA) <[EMAIL PROTECTED]> wrote:
> > I noticed this as well. If no one steps up to
> maintain it, I'm inclined to remove it
> >competely. I'd like to minimize the number of
> example applications
> we maintain, and it
> >seems like any advanced AJAX shopping cart coul
Sounds good to me, provided everyone is aware that 2.0.1 and 2.0.2 will likely
have some large changes.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=38227&messageID=75314#75314
---
The snippet binary is attached with a comment indicating the source and date.
Our snippet macro is a lot more advanced than the one you linked to. It is
based on that one, however.
-
Posted via Jive Forums
http://forums.opensymph
Ted - you have to ask me nicely. Just kidding.
Basically, the snippet macro is currently located here:
https://opensymphony.dev.java.net/source/browse/opensymphony/wiki/snippet/
I build it in IDEA (really ghetto, I know) and just upload the jar. The macro
binary works in both the OpenSymphony a
To follow up to my other forum post I just made - sounds like a
maven2.opensymphony.com would fix this stuff. I'll get started on that.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37898&messageID=7
Would it be helpful if we set up a maven2.opensymphony.com which hosted the
xwork snapshots?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37887&messageID=74502#74502
--
Yup, the xwork profile is very nice for when generating the IDEA projects.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37836&messageID=74501#74501
-
Nathan,
I don't think "tools" will work for us for now because of the body tag
requirements. Perhaps Velocity 1.5 will help?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37739&messageID=74500#74500
I think "surl" is fine. Not super pretty, but I'd rather use the prefix "s" for
JSP, FM, and Velocity than come up with different prefixes for each and/or use
the "s2" prefix. My second choice would be the s2 prefix.
-
Posted via
We could do this, though I think it would actually be better if we just created
a forums instance for Struts in the first place.
Can we use the Zone for that?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?t
+1 to any side projects being at OpenSymphony. I think it will help keep the
bond between Struts and OpenSymphony to continue to be a close one.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37238&me
FYI - I'm working on a maven2 repo for opensymphony that will resolve this
issue.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37086&messageID=73119#73119
-
This is a good question. I've wrestled with this a lot with WebWork. A few
thoughts:
- Does documentation have to be included in the release, or is connectivity
good enough these days to let us get away with just pointing users to the wiki?
- If we are to include a war file for the sample app
Probably, though I haven't looked in to it too much yet.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=36712&messageID=72174#72174
---
+1
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=36623&messageID=72169#72169
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Ted, the javadocs problem may be the case, but remember we can get around those
glitches by utilizing the ant plugin and doing that kind of stuff in Ant.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID
+1
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=35827&messageID=70400#70400
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
My quick thoughts: I think realistically either of the following two outcomes
are positive developments for everyone:
1) We move in the direction of "Struts 2.0", which houses all SAF2 and Shale
and get back for it being OK for folks to say, "I use Struts". We've all said
we want to work togeth
Just to add to what Jason already said: no one is suggesting getting rid of
Dojo, just that we'd move the "ajax" theme as it exists today over to the new
"dojo" theme and then the new ajax theme would be a simpler implementation
based on DWR and possibly Prototype. When users need more, they are
+1 for removing them
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=34665&messageID=67801#67801
-
To unsubscribe, e-mail: [EMAIL PR
How about com.opensymphony.xwork2? :)
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=34229&messageID=66656#66656
-
To unsubscribe,
Don,
I'm totally in favor of that, but only if we make sure that
struts-action-default.xml (originally webwork-default.xml) includes this
pattern as a default. Does that seem fair?
-
Posted via Jive Forums
http://forums.opensymph
Speaking of reviewing the commit messages... can we get FishEye set up? I'd
love to use RSS to review the commits :)
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=33879&messageID=66381#66381
--
OK - what's the consensus here then? I'd be happy to use vmbuild.apache.org.
Or, I was planning on setting up opensource.hostedqa.com/continuum to donate to
various projects. Or we can wait for Sean and James to work it out.
I suppose having multiple ones can't hurt too much.
Anyone have a pref
Frank,
Thanks for taking the time to submit a patch - I've marked it for being fixed
for 2.0, so we'll get to it soon.
Patrick
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=33300&messageID=65334#653
Dave,
I think you are thinking about this the same way we are. Bob Lee and I agreed
when we met up during JavaOne that there should be just one stack to handle 90%
of the needs of users. The actual logical differences in the stack (form submit
vs. "view") should be handled by conventions and/or
Ted,
The plan looks solid. There may be a few other things we might try to sneak in,
but what you have there is definitely the core plan.
Let me know if you need help with the snippet plugin - I have the source code
and can deploy a new version if it is acting up or giving you trouble.
Patrick
Do we have something like Continuum setup for Struts? If not, we should. What's
the process to kick this off? Besides the unit tests we should be running
frequently, I'd like to turn on nightly runs of HostedQA (the product my
company has donated to Struts for doing end-to-end automated tests).
Sounds good to me. I can start the process of migrating to SVN.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=31704&messageID=61925#61925
Let's leave XW at OpenSymphony for now - as we know there is a lot of work to
be focussed on when moving a project to Apache and I'd rather not let that
distract us from the core work that needs to be done on Struts. I say in 6
months or so we see about moving it, once we have a SAF 2.0 release
The builds of xwork are still being done all the time:
http://maven.opensymphony.com/opensymphony/jars/
Perhaps our build is no longer picking up from that repo?
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa
Codehaus.org had a serious hardware problem and so the site is down. I'm not
sure what a good suggested workaround is at this point. Perhaps someone who has
that jar locally can post it up on a site so you can install it temporarily.
---
It looks like this is now basically done (the JIRA issue is complete). The
final step will be to unsubscribe the address [EMAIL PROTECTED] from all lists
except for the dev@ list. That will keep the forums synced on the OpenSymphony
forums limited to just the discussions. I was trying to figure
1 - 100 of 172 matches
Mail list logo
