The key attribute is for simple resource properties lookup only, without
MessageFormat. The tag is able to deal with MessageFormat in
particular.
In your case you could either use specialized properties in your bundle:
reject.to=Reject to
reject.to.larry=%{getText('reject.to')} Larry
or use the
FWIW, JAX-RS/Jersey provides both a Filter and a Servlet option as a
controller, however the Servlet came first.
http://java.net/jira/browse/JERSEY-122
Note the bug mentions Wicket also uses a Filter. The bug also provides an
interesting reason for the use of a filter
to interc
No worries, always good to question - review - rethink
If there is serious interest in an alternative servlet dispatcher besides
FilterDispatcher, contributions are welcome. From the top of my head, the old
dispatcher is still around as deprecated, and most of the dispatcher
functionality resid
>> I remember more than one case where I found WAS / Websphere Portal to
>> implement a very ... say ... at least ... imaginative interpretation of the
>> specs
That is exactly the point,the compromise of "clear-cut" sections of spec in
favor of "unclear, murky, interpretive" sections of spec i
On Tue, Aug 14, 2012 at 12:10 PM, Rene Gielen wrote:
> So far I fail to see where Struts 2 deviates from or violates the spec.
>
Agreed; I've now read the relevant sections of older and new specs, and
AFAICT it does not explicitly disallow serving resources.
Further, it is arguable that the phra
We currently seem to have some issues with the export from Confluence,
going to check this - thanks for the notice!
As a workaround, here is the direct link to the notes in Confluence:
https://cwiki.apache.org/confluence/display/WW/Version%20Notes%202.3.4.1
Thanks,
- René
Am 14.08.12 18:14, schr
So far I fail to see where Struts 2 deviates from or violates the spec.
The fact that _usually_ a front controller - a concept not to be found
at all in the servlet spec - is implemented as servlet does not mean
that it _has_ to be implemented that way, unless the spec says or
clearly implies other
> We've even been able to integrate JAXRS & Struts2 in a single web-app which
> serves both a REST service and an Application.
>
we did it also, both under same Services and Entity.
but we need direction for this.
F
> --joe
>
>
> Joseph Mocker | Velti | Senior Software Architect
> t +
I can't speak to Struts2 as REST but JAXRS/Jersey is a pretty straight forward
API for building RESTful services. It uses Annotations heavily. I don't know if
it has a configuration file similar to struts.xml but that could be handy for
more dynamic configuration of services.
We've even been ab
hi all
if we need to create full REST apps...
does S2 not a recommended one?
anyone can help?
should we use the JAXRS instead like RESTeasy
Frans
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional c
What people are missing here is that using filters and deviating from the spec
as front controller would cause quite a few issues when some applications
servers are used. I quite clearly remember that I went through hell to deploy
my applications on WebSphere applications with an Http server as
11 matches
Mail list logo
