except in the
simplest of use-cases. I do feel the approach is great and needed
though and I'm looking forward to the enhancements.
regards,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
of that opinion helps right now. I'm not using
SmartURLs in any for-production code at the moment as 0.18 didn't pass
my evaluations. I am using the REST plugin however primarily because I
preferred its URL mapping.
regards,
Jeromy Evans
Brian Pontarelli wrote:
Jeromy Evans wrote:
While on the topic, with respect to defaults/exceptions etc, can I
ask the specification addresses how invalid URLs are handled. In the
current implementation (0.18) invalid URL's return (unexpected?)
success results.
They shouldn't unless
unable to reproduce this.
regards,
Jeromy Evans
Brian Pontarelli wrote:
Okay. The example is in the SmartURLs repository:
http://smarturls-s2.googlecode.com/svn/trunk/apps/crud-example/
It works pretty well. A few things I think could help reduce the
overall code bloat:
1. Support public
Brian Pontarelli wrote:
Brian Pontarelli wrote:
Okay. That should be finished. It was somewhat tricky because the
XWork runtime configuration returns a valid ActionConfig for any URL
that ends in a / if you have a index action at the root. This is the
default handling that I'm not very fond
to coexist with non-smarturl configuration in 2.0.x.
cheers,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
What is the correct way to serialize an enum to JSON?
The struts2plugin can't handle enums quite right (Issue 9:
http://code.google.com/p/jsonplugin/issues/detail?id=9) and while trying
to finalize a patch I haven't found a consistent opinion.
There's two schools of thought:
- an enum should
the coming months and will
contribute where I can. Hope that helps.
regards,
Jeromy Evans
I'm very interested in using/supporting this plugin as well. If we can
come up with a better acronym for SOFEA/SOUI architectures - I think
this stuff will really take off.
Matt
On Nov 24, 2007 7:58
Eric Martin wrote:
Is there a way to suppress or remove unwanted attributes from showing up for
a tag?
In 2.1 there's @StrutsTagSkipInheritance in core.
Merging this annotation and the corresponding apt config (?) to 2.0
would be the least effort.
that's missing is what to provide when an html response
is requested but there's no corresponding view, in which case a
server-side transformation to html would be valuable.
regards,
Jeromy Evans
Tom Schneider wrote:
Personally, I !!HATE!! writing xsl. I try to avoid it at all costs,
but maybe
browers with
better tooling. My client-side template merging process is shoddy though.
Jeromy Evans wrote:
Don will provide much more insight, but I thought I'd mention that the
REST plugin already automatically serializes the model as XML when an
xml response is requested (xstream).
The client
Don Brown wrote:
2. A new attribute on the action element called 'allowedMethods',
which takes a comma-separated list of method names to allow
3. A new @ActionMethod annotation for the codebehind plugin that
declares a method as callable
I'm thinking about doing all three, but I'm not sure #2
this? Are there any
thoughts on the direction of UIBean? Or have I missed something?
regards,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Adam Hardy wrote:
Is it right to assume that no-one is interested by the idea of
extending the S2 Result to allow extra configuration or classes at
this location in the architecture?
Hi Adam, I haven't been convinced yet that there's a strong argument for
this compared to alternative
Al,
There is indeed a related bug, but the issue is only realized when the
head tag CANNOT be processed within the current page context.
(eg. within a fragment loaded via XHR)
https://issues.apache.org/struts/browse/WW-2398
regards,
Jeromy Evans
Musachy Barroso wrote:
you are missing
, because I believe the current situation creates an error
which is too obscure for the average developer to easily discover what
the problem is.
Anyone have any other thoughts?
Al.
- Original Message - From: Jeromy Evans
[EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org
, 5.02.2008, 05:37, schrieb Ted Husted:
Please join us in welcoming Jeromy Evans as a new Struts committer.
Jeromy has been posting to the user list since May 2007, and to dev@
since July 2007, and has submitted two issues to JIRA, both with
patches.
Welcome, jeromy@ ... WW-2398 is all yours now
, or OGNL
wrapped so UEL can be used in the tags, but it's not going to be easy!
See the thread(s) from November 07 containing JUEL plugin in the subject
reagrds,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Dave Newton wrote:
--- Don Brown [EMAIL PROTECTED] wrote:
Well, most of those were patches so I can't really take any credit.
Strangely, many of the patches were from Jeromy...someone should tell
him he can commit his own patches now :)
Maybe he forget ;)
I was saving my patches
Can someone with power please grant me write access to the WW space at
http://cwiki.apache.org/confluence/display/WW/Home?
My existing login (jeromy) currently only has write access to the
S2WIKI: http://cwiki.apache.org/S2WIKI/home.html
Thanks!
Jeromy
Thanks Don. Sorry, the confluence username is jeromyevans (with an o)
Don Brown wrote:
I tried, but I don't see your account. Could it be under something else?
Don
On 2/18/08, Jeromy Evans [EMAIL PROTECTED] wrote:
Can someone with power please grant me write access to the WW space
I started an Issues section and a Goals section to explicitly
identify the problem(s) that needs to be solved.
http://cwiki.apache.org/confluence/display/S2WIKI/OGNL+replacement
Brian Pontarelli wrote:
Yeah, this is one of the frustrations that most beginners encounter
and that I'd really
Musachy Barroso wrote:
I never thought this would generate such a long thread. Yeah we should
fix it, but c'on, we have a ton of bugs to fix and new/cool stuff to
implement :).
musachy
Yeah, this thread is a classic case of non-urgent non-important chatter
(ref Steven R. Covey's book
Brian Pontarelli wrote:
Dave Newton wrote:
--- Al Sutton [EMAIL PROTECTED] wrote:
Is there a list of gotchas for a 2.0 to 2.1 migration?
One was started at
http://cwiki.apache.org/S2WIKI/troubleshooting-guide-migrating-from-struts-20x-to-21x.html
There are more that should be
Ian Roughley wrote:
Dave Newton wrote:
--- Musachy Barroso [EMAIL PROTECTED] wrote:
Yikes.
The issue with the Dojo plugin (and any other, like my somewhat-waylaid
jQuery plugin) is that I end up writing all the JavaScript anyway,
and the
tags don't help me very much in all but the
than the parent ${pom.version}so they could
build if the latest core API had changed. I believe that's been
rectified, or perhaps it only applied in the non-bundled plugins I've
examined.
cheers,
Jeromy Evans
Don Brown wrote:
Yes, you are missing my original point #2 - We need to be able
Blake Byrnes wrote:
I dealt with the ajax result discrepency (ie, if you make an ajax request,
you generally want a different result, but probably want to share the same
action) by writing a few things:
1) A sitemesh filter that ignores requests with the content header
into
another big plugin... my mini-framework also supports auto-back on post and
a bunch of other things...).
Blake
On Fri, Feb 22, 2008 at 12:18 AM, Jeromy Evans
[EMAIL PROTECTED] wrote:
Blake Byrnes wrote:
I dealt with the ajax result discrepency (ie, if you make an ajax
request
expression definitely doesn't call getTexts(name) when a
TextProvider is available (in Struts 2.1.1). Does anyone know if OGNL
has changed and texts('name') used to be a match getTexts(String), or
is this just a bug?
Thanks,
Jeromy Evans
PS. In the case that the call fails to find a resource bundle
Hi Brian,
Yes, you're right that by default the templates are retrieved from the
jar. It's a normal performance improvement to extract them from the
java to improve performance and this may be why others haven't noticed
the problem.
Do you have time to copy them out and observe the
My opinion is that the criticality is overstated.
However it is useful to draw attention to the vulnerability.
Don Brown wrote:
Looks good. Thanks for creating a security bulletin as well.
Don
On 3/4/08, Rene Gielen [EMAIL PROTECTED] wrote:
The release has been submitted for mirroring.
Bob Tiernay wrote:
If adding a jstl enabled tld is because it's dangerous with ognl expression use, then
make the uri: struts-dangerous! If it's because there is a process issue, lets discuss
:)
Bob
Process issue : an APT task automatically generates the TLD using
annotations on each
On Mon, Mar 10, 2008 at 12:57 PM, Dave Newton [EMAIL PROTECTED] wrote:
Mostly I'm trying to mitigate the amount of teeth-pulling necessary to get
questions asked in a way they can actually be answered because it's driving
me insane.
Do you think any of this can be attributed to
Shouldn't validation just be fixed?
The root problem is that validation only uses the action alias and
doesn't check if a method name is provided in a parameter.
The user of a wildcard just works-around that limitation to creating an
alias it can match.
For historical reasons there's at
Dale Newfield wrote:
Jeromy Evans wrote:
Shouldn't validation just be fixed?
What you really want to say in the s:submit tag is run this action
instead what we're currently saying is run this method instead.
Because of this, you're getting different validation than you want
because
and funky tags; add standard interceptors
models to ease integration with the client-side libraries, groovy,
grails, JSF, struts1 (and others?). tags move to plugin.
- I don't have an opinion about portal support but I'm sure it's important
I think I ran out of hours already!
cheers,
Jeromy Evans
Niall Pemberton wrote:
I just saw the following comment
FreeMarker is very similar to Velocity, as both are template
languages that can be used outside of a Servlet container. The
framework utilizes FreeMarker because FreeMarker has better error
reporting. However, both are good alternatives to
Jonathan Revusky wrote:
Thanks for the detailed argument Jonathon.
Jeromy Evans wrote:
Niall Pemberton wrote:
I just saw the following comment
FreeMarker is very similar to Velocity, as both are template
languages that can be used outside of a Servlet container. The
framework utilizes
-replacement.html
regards,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm available to perform a good chunk of testing.
Ted, if you do it can you keep some notes on the tasks you perform? Or
is there anything with more detail than [1] or a previously used release
plan for 2.x?
I'd hoped to perform a dry-run myself but don't see how I can do that
without
Wendy Smoak wrote:
On Fri, Mar 28, 2008 at 7:57 PM, Jeromy Evans
[EMAIL PROTECTED] wrote:
I'd hoped to perform a dry-run myself but don't see how I can do that
without committing via mvn release:prepare.
What do you mean by dry run? The release:prepare goal has a
-DdryRun=true
That's as far as I got because I shouldn't have to install:install-file
xwork-2.1.1 into my localRepository, so I guess I have to wait a little
longer for it to replicate?
regards,
Jeromy Evans
Ted Husted wrote:
I'm still heads-down, but I could run a build through the gauntlet.
Can anyone
I had a miror configured (http://mirrors.dotsrc.org/maven2). I've
passed that hiccup using the central repository.
Rainer Hermanns wrote:
Jeromy,
that's strange... XWork 2.1.1 jars are all available from the central
repository.
See here:
-SNAPSHOT/version
Jeromy Evans wrote:
Ted, I tried to get you started with a dryRun of release:prepare but
I'm still missing xwork.jar:2.1.1. The mvn output is at
http://people.apache.org/~jeromy/buildlog1.txt
Other details:
* JIRA: No open issues except the omnibus ticket
(https
Ted Husted wrote:
Yes, it is something we should do first. It's on the list, but I
usually forget about it until the last minute ... :)
Are you setup to digitally sign the releases, Jeromy?
I've started working my way through it now. I'll have to come back to
it tomorrow as it's too late
Agreed. The Dojo 0.43 plugin in Struts2.1.1 contains significant
improvements over the Dojo 0.40 tags bundled in 2.0.x. It's worth
releasing as-is and I'd give it a +1 today.
It sounds like there's enough people interested to complete a Dojo 1.x
plugin. I also think it's worth creating a
Dave Newton wrote:
Nutshell: what's anybody's take on the effort this would require, and who's
available to make that effort?
I share similar sentiment and at most will just be able to convert my
existing 2.1.1 test applications over to use the Dojo 1.x plugin to
investigate the
Martin Cooper wrote:
On the other hand, creating the project in the Struts sandbox means that it
is immediately open to any Struts committer, all of the resources are
already set up, and getting a release out is dependent only upon a vote to
move the code from the sandbox to the main code
No objections from me. The latter two or three don't have to be
plugins, just build artefacts.
I hate that junit circular dependency. I wish there was a better way.
There's several base test classes that would be useful to users if they
were available in a struts-test jar.
Don Brown
I've signed struts-annotations-1.0.3 using [EMAIL PROTECTED] and copied
to [1].
Can some please take a moment to check these? If they're okay I presume
the artefacts then just need to be copied to the right location for
rsync to ibiblio. Any other formalities for struts-annotations?
[1]
Jeromy Evans wrote:
I've signed struts-annotations-1.0.3 using [EMAIL PROTECTED] and
copied to [1].
Can some please take a moment to check these? If they're okay I
presume the artefacts then just need to be copied to the right
location for rsync to ibiblio. Any other formalities
Martin Cooper wrote:
Please do *not* edit that file directly. The KEYS file is maintained in SVN,
so you need to update that and then refresh the file on the site from that.
https://svn.apache.org/repos/asf/struts/maven/trunk/build/KEYS
Fixed. I've updated the instructions:
Wendy Smoak wrote:
On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans
[EMAIL PROTECTED] wrote:
I've signed struts-annotations-1.0.3 using [EMAIL PROTECTED] and copied to
[1].
Where/how did you sign them? Were the files re-built? Generally you
only sign what you build yourself, while it's
Martin Cooper wrote:
If the binaries Jeromy created are bit-for-bit identical to the ones you
built, then I don't have a problem. If they're not, then what he has built
is not the same as what was voted on.
And more to the point, actually, it's not what people tested before they
voted.
Martin Cooper wrote:
On Tue, Apr 8, 2008 at 6:57 PM, Jeromy Evans
[EMAIL PROTECTED] wrote:
Understood. Can I sign and distribute Don's binaries[1] or *must* they be
signed by the person that built them?
I've lost track of why Don can't sign them himself, but I would consider
S2.1.1 isn't without bugs. I want it tagged and released (non GA) so
more people can try it and so we can get some momentum again.
Al Sutton wrote:
So would this mean that the S1 plugin for S2.1.1 wont work if the
developer uses the S1.3.8 libraries instead of the S1.3.5 the plugin
is being
issues.
regards,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Don Brown wrote:
Sounds good. Are there any performance implications?
Don
According to https://issues.apache.org/struts/browse/WW-1681 the
performance implications are very significant (significantly improved).
getText(String) invoked via OGNL and and getText(key, defaultValues,
args)
, but stack manipulation is permitted within the tag.
Any better thoughts on this issue?
cheers,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks Don! Looks like you had another late night.
I'll migrate a large 2.0.9 application to 2.1.1 this weekend, updating
the migration guide as I go.
James Mitchell wrote:
Don, I'm checking out the tag now and will be giving it a thorough test
drive today and tomorrow.
Thanks
On Thu, Apr
Antonio Petrelli wrote:
Hi all
Since the license headers are an annoying problem, I wish to add the
Maven License plugin:
http://code.google.com/p/maven-license-plugin/
This plugin can *add* license headers on top of files *automatically*
Thoughts?
I may be guilty of forgetting to add the
Don Brown wrote:
The test build of Struts 2.1.1 is available.
Release notes:
* http://struts.apache.org/2.0.11.1/docs/version-notes-211.html
Any idea why this published Version 6 of the release notes dated 19 Feb
08 instead of Version 11 that was current at 17 Apr 08?
Note the incorrect
I spent several hours migrating applications to Struts2.1.1 today. I've
applied a significant overhaul to the migration guide [1].
Summary of results:
core: no new issues encountered after following the migration guide
tiles 2 plugin: no new issues encountered after following migration guide
Wes Wannemacher wrote:
Can anyone else confirm this for me before I put it in JIRA?
Hi Wes,
I just did a quick test in a non-blank application that's running off
the current snapshot and it had no such problem.
Potential differences:
- do you have the mandatory actionPackages
Wes Wannemacher wrote:
Thanks for taking a look Jeromy, but I don't have a struts.xml in my
test-case app. On my bigger project, I am using action scanning and it
is working fine. I noticed it when I tried to hit an action that should
have gotten automatically mapped (i.e. /index.action where
actionMapper) {...
It only gets complicated when you need to mix injection with beans
created outside the container, as described by Wes.
cheers,
Jeromy Evans
PS. this is far inferior to the current functionality of Guice
. I don't want to pass more flags in from the action tag.
Has anyone got some suggestions on a tidy way to resolve this? Removing
the ThreadLocals would be nice.
cheers,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Dave Newton wrote:
My naïve reaction would be to put it on a stack, since we're talking nested
contexts, and set the thread local from it. But I can't even find that code
right now :/
Dave
Yeah, that seems a major change to xwork. By use of threadlocals it
appears it was not intended to
Dave Newton wrote:
Can someone tell me if I'm nuts and/or my Eclipse/Maven thing is going crazy?
What should I get as a plugin snapshot version number in trunk, 2.1.1 or
2.1.2, when building via Maven?
Thanks, and *agh*,
Dave
Right now, at rev 651477: 2.1.2-SNAPSHOT
issues in JIRA in the near future and this one is the list.
regards,
Jeromy Evans
.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Putting aside the technology for a moment:
- ability to deploy new actions/replace actions and pages without a
container restart: highly desirable
- ability to deploy new/replace business-layer services without a
container restart: highly desirable
- ability to evolve Struts2 without fear of
Musachy Barroso wrote:
I am refactoring that out of FilterDispatcher so it becomes another
extension point.
musachy
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jay Bose wrote:
Thanks Antonio, that solved it.
Just wondering, how does one know that before attempting mvn
assembly:assembly, they must run the release,all,alljars,j4 and
pre-assembly profiles?
Is it just a matter of digging through the pom until you find the right
profiles?
(It's
Hi Jay,
This question about the use of Struts 2 should be asked in the
struts-users forum.
The quick answer is that XWork provides a DI mechanism. The
ValidatorFactory can be injected into a property or constructor using
the @Inject annotation in objects created by the framework. See the
+1
[X] Beta
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Martin Cooper wrote:
I think involving the foundation in anything like this could open up a
legal minefield.
Indeed. I would encourage anyone who really wants to go down that path to
engage with the prc@ and legal-discuss@ first, to gain a full understanding
of what would be acceptable for the
Al Sutton wrote:
P.S. imho we should just spin-off (or kill off) the dojo plugin, if it
needs paid-for time just to keep it up to date then I would say that
it's not something we can support to a level that's acceptable to the
users. I recently had a shot at updating it, but found it was
Ensure you're following these instuctions:
http://struts.apache.org/2.x/docs/building-the-framework-from-source.html
and running a clean with the all profile:
mvn clean install -Pall
As a last resort, clear your maven repository/use an alternate empty one.
All tests have to pass for a
Struts Two wrote:
Websphere version: 6.1.0.13 (which includes the fix - the fix was included in 6.1.0.7). I have also set the following flag to 'true' in the server custom properties for filter-compatibility: com.ibm.ws.webcontainer.invokefilterscompatibility
the blank.war for struts 2.0.11
I haven't tested the latest Convention plugin yet so I can't vote yet,
but I'd probably give a [-1] because I don't like the options provided.
I support moving Convention plugin from the sandbox to become the
recommended convention for new users, replacing ZeroConfig and CodeBehind.
However, I
I wouldn't rush into this decision.
Users of the REST plugin require @Namespace, @Result, etc annotations.
Creating a duplicate set of annotations with the same purpose is not
sensible.
It's appropriate that the REST plugin has a dependency on the plugin
that auto-populates the
Jeromy Evans wrote:
I wouldn't rush into this decision.
Users of the REST plugin require @Namespace, @Result, etc
annotations. Creating a duplicate set of annotations with the same
purpose is not sensible.
It's appropriate that the REST plugin has a dependency on the plugin
that auto
the problem with REST is easy to fix; one blocker down. Now,
about supporting Codebehind from Convention, any other opinions
(before pulling a vote on it)?
musachy
On Fri, May 16, 2008 at 2:30 AM, Jeromy Evans
[EMAIL PROTECTED] wrote:
Jeromy Evans wrote:
I wouldn't rush into this decision
/controller definitions come from same Configuration instance).
Musachy Barroso wrote:
My head is spinning now :). Can you use REST with Xml Conf?
musachy
On Fri, May 16, 2008 at 2:30 AM, Jeromy Evans
[EMAIL PROTECTED] wrote:
Jeromy Evans wrote:
I wouldn't rush into this decision.
Users
packages are created/joined.
eg. @Namespaces([EMAIL PROTECTED](/baseA), @Namespace(/baseB))
This is something I need but Codebehind can't easily be adapted for it.
Thanks,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Musachy Barroso wrote:
Convention now supports @Namespaces (class and package level)
musachy
Thanks Musachy! I'll definitely migrate one of my REST plugin apps to
use Convention behind it..
-
To unsubscribe, e-mail:
,
Jeromy Evans
PS. rest howcase on trunk can't build as it uses @Results and now needs
an explicit dependency on CodeBehind/Convention added to its pom.
Musachy Barroso wrote:
I created a proposal page on the wiki for this:
http://cwiki.apache.org/confluence/display/S2WIKI/Convention%2CCodebehind
Musachy Barroso wrote:
WW-2667 is fixed on trunk. Has anybody taken a look at the multiple
unknown handlers proposal? I have the code ready to go but I am still
waiting for some confirmation :)
Hi Musachy, I think the proposal is fine. The use of multiple unknown
handlers will be rare.
Musachy Barroso wrote:
Yes, that option is totally viable now that they can co-exist(assuming
that multiple unknown handlers are supported). One drawback it has, is
that for new users of the plugin, it would be confusing to have 2 sets
of similar annotations. The other problem would be the
exist?
Thanks,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yeah, it is REST plugin related. At the moment a result is mandatory
(enforced by xwork) even though many of the restful operations its
meaningless to declare a result.. In those cases its also inappropriate
to use to ServletRedirectResult so a NullResult can be used.
However, you're
, but starts a
useful convention)
I get the impression that few users use TilesResult though (but do use
Tiles within JSPs).
Any thoughts?
cheers,
Jeromy Evans
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
that knows which method to invoke
based on the current context.
I don't think these belong in the rest plugin as we eventually want to
achieve independence of the tag implementation though.
Any interest? If not I may just push them onto googlecode.
cheers,
Jeromy Evans
Anyone know how to work-around this? It's caused by the updated
annotation processor:
http://opensource.bamboo.atlassian.com/browse/STRUTS-MAIN-851
http://opensource.bamboo.atlassian.com/browse/STRUTS-MAIN-852
[INFO]
Don Brown wrote:
Why not put them in the rest plugin?
Well... I thought we planning on moving the S2 tag support out of core
into a tags-plugin eventually.
Including tags in the rest-plugin will complicate that issue further,
won't it? UIBean does come with a lot of coupling baggage.
There's been updates to annotations, xwork and s2 today. It's building
now on bamboo (10mins ago) so just find which one's not up-to-date locally.
Dave Newton wrote:
I'm still getting it; what do I need to do to get... um... the latest thing(s)
that make it not broken?
Dave
Dave Newton wrote:
Are you using a local annotations?
Yeah, I'm using a local struts-annotations snapshot that includes Don's
fix to tag.ftl (rev 670136).
That's available in struts-annotations-1.0.4-20080621.043234-3
(referenced in struts-parent pom.xml) if you can retrieve that
Dave Newton wrote:
Nobody else is getting build errors in the codebehind plugin?
No,
s2 rev 670268 mvn clean install -Pall passes
but
xwork rev 1839: tests fail due to a date locale problem (I haven't
looked at the code, but there must be a US dateFormat assumption in a
validator test)
dusty wrote:
I think this is what is holding me back from using the REST plugin. I have
plenty of S2 RESTfully designed applications, but without the routing
support I feel like I am fighting the framework to make it do things like
URLs that people think RESTful systems should do.
If
Jeromy Evans wrote:
Those are the two biggest areas I've had to fight with in S2 to moving
towards a restful design so far.
I forgot, the other area that is a major pain is the
absolute/non-hierarchical namespace implementation.
For example, if all my resources support, say, Notes, then I
1 - 100 of 156 matches
Mail list logo
