Actually, I was confusing portlet support with the J4 backport
support. We've had portlet labeled experimental all along. Though,
based on the remarks in this thread, I do intend to patch the 2.0.4
notes to label the J4 backup experimental too.
If nothing else comes up tomorrow, I'll do that and
Follow-up for the described issues:
Annotation driven action configuration issue - WW-1695
PrincipalAware issue - WW-1696
Don Brown schrieb:
I believe we currently have portlet support as "experimental", so it
shouldn't affect the quality vote.
Regarding this along with Ted's remark to fix r
+1
Ted Husted wrote:
It is labeled as such now, in the 2.0.5 notes, but I didn't think to
do that before assembing the 2.0.4 distribution. If there are no
objections, I could patch the 2.0.4 release notes to include the same
remark as 2.0.5, and upload new signed copies 2.0.4-all.zip and
2.0.4-d
It is labeled as such now, in the 2.0.5 notes, but I didn't think to
do that before assembing the 2.0.4 distribution. If there are no
objections, I could patch the 2.0.4 release notes to include the same
remark as 2.0.5, and upload new signed copies 2.0.4-all.zip and
2.0.4-docs.zip, before announc
I'd really like the portlet url support to be transparent, i.e. no
separate tags. Therefore, we'd need to have the url builder stuff
refactored first, which should be ok since I'm not a _huge_ hurry to
split the portlet code off to a plugin.
Don
Nils-Helge Garli wrote:
Hi,
First of all, I
Hi,
First of all, I want to apologize to everybody for beeing away for so
long... I hope it has not caused too many problems. Hopefully, I can
still be of some help...
Don,
What's the remaining 10% you're having trouble with? We can move out
the URL and Form stuff, but it would require separate
I believe we currently have portlet support as "experimental", so it
shouldn't affect the quality vote.
Don
Rene Gielen wrote:
Hey guys,
a few minutes ago I came to the opinion that we have some major issues
with portlet integration, which imo should be fixed before rolling out
current buil
Hey guys,
a few minutes ago I came to the opinion that we have some major issues
with portlet integration, which imo should be fixed before rolling out
current build:
- Annotation based configuration for actions seems to fail at least in
my portlet environment (Liferay 4.2.1), resulting in i
I'd also like to try a full-fledged zero-config MailReader.
On 1/31/07, Don Brown <[EMAIL PROTECTED]> wrote:
I think we should use annotations where ever possible and the blank
archetype seems like a good place to start.
Don
+1!
Ian Roughley schrieb:
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of the
bootstap tutorial, I didn't see any explicit reference to needing to
move the files from the com/myComp/myApp directory into the mirrored
class
I think we should use annotations where ever possible and the blank
archetype seems like a good place to start.
Don
Ian Roughley wrote:
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of
the bootstap tutorial, I didn't see a
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of the
bootstap tutorial, I didn't see any explicit reference to needing to
move the files from the com/myComp/myApp directory into the mirrored
class directory, if you used the
Hey Patrick,
Haven't had time to look at this any further. Yes, I definitely would build
on top of the ActionMapper stuff--that's already abstracted out so nicely I
didn't even mention it. :) I might have some time this weekend to dig into
this further. (I was too busy releasing the first versi
Hello all - I'm new to Java Web development/Struts, and was wondering if
Struts provides its own persistence layerI see many people use Struts in
conjunction with Hibernate, I wasn't sure if this was necessary or simply
most convenient...
Thank you!
--
View this message in context:
http://w
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
The blank application contains the files from the bootstrap tutorial.
* http://struts.apache.org/2.x/docs/bootstrap.html
The tutorial files are put "out of the way" so that people don't need
to delete them just to get started. But, they are still there for
reference. So, no, don't make the same
I was going to run with this. Did you want me to make the same
deletions to the blank application? After all, since they are not in
the correct directory, the files are not being used.
/Ian
Ted Husted wrote:
Once things are sorted out, it would be nice to revert it to match the
Struts Blan
I'm not arguing against annotations, only saying that per-method
valdidations are supported.
One workaround would be to let the validation.xml include another
validation.xml. I haven't tried, but this might already be possible
using XML entities.
But, again, the annotation support would also be
Yes, but that requires seperate validations config per method - even if
they are identical.
Take a dumb example. . .suppose you have an action with simple methods:
load
create
update
delete
Perhaps you have the same validation on create and update, but do not
want them to execute on load and
Per-method validations are supported, using the convention
* ActionClass-actionMethod-validation.xml
This approach doesn't work with "dynamic method invocation" though
(the WW ! notation), because of the way DMI is implemented. Per method
validation does work with wildcards, though.
-Ted.
On 1
Once things are sorted out, it would be nice to revert it to match the
Struts Blank application, but for now, it seems like we should strip
it down.
On 1/30/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
I have been looking through the s2 maven archetypes, and would like to
propose that we don't in
That's would be really usefull...
I am waiting too, If I could heap in something...
Thank's,
André Faria
David H. DeWolf escreveu:
It's something I actually will be needing in the near future. If no
one beats me, I'll probably take a look at the patch (late?) next week.
David
Laurie Harper
+1
On 1/30/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
I have been looking through the s2 maven archetypes, and would like to
propose that we don't include resources that are at a package level
(i.e. validation and conversion). The reason being that maven2
currently does not support this featur
23 matches
Mail list logo