+1
Sent via BlackBerry.
-Original Message-
From: "Wes Wannemacher" <[EMAIL PROTECTED]>
Date: Thu, 27 Sep 2007 15:57:09
To:"Struts Developers List"
Subject: Adding OGNL section to FAQ
Would anyone be opposed to adding an OGNL section to the FAQ in the
main Wiki? There are always ques
Would anyone be opposed to adding an OGNL section to the FAQ in the
main Wiki? There are always questions on struts-user and there are
even one or two JIRAs.
-Wes
--
Wesley Wannemacher
President, Head Engineer/Consultant
WanTii, Inc.
http://www.wantii.com
---
Struts 2 link in :
http://struts.apache.org/javadoc.html
is broken, not sure what the fix is. There is a ticket for it:
https://issues.apache.org/struts/browse/WW-2172
musachy
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
-
Quoting Brian Pontarelli <[EMAIL PROTECTED]>:
I guess I'm missing the overall use case. Do you just want to get rid
of all your XML configuration and put everything inside Java code and
annotations? Or are you trying to solve a specific problem that is
currently unsolvable? It seems like it is
It's not unprecedented to put annotations on package-info.java.
Obviously the JDK supports it, and Hibernate allows you to use JPA
annotations at the package level. For instance, I've done that to
define at a more global level a default ID generator for my
persistent classes.
While packag
--- Eric D Nielsen <[EMAIL PROTECTED]> wrote:
> Seeing how package-info.java is used primarily for
> JavaDoc needs, I'm not sure how clean it is to start
> mixing in the configuration aspects.
I wouldn't say it's used *primarily* for JavaDoc
needs; it was introduced specifically for
package-leve
I guess I'm missing the overall use case. Do you just want to get rid of
all your XML configuration and put everything inside Java code and
annotations? Or are you trying to solve a specific problem that is
currently unsolvable? It seems like it is more of the former because
right now, with a
Quoting Brian Pontarelli <[EMAIL PROTECTED]>:
You actually can annotate packages. There is a special java file
called package-info.java that you place in a package and annotate
like this:
@ParentPackage("foo")
package com.example.actions;
Ahh, that's what I was referencing as a possible sol
Okay, I added this feature into the code and it should be ready for the
0.20 release. Does it make sense to also add the same handling for
Namespace? Seems like this would reduce duplicate annotations inside
classes... However, I'm not a big fan of using the namespace if it can
be avoided and
You actually can annotate packages. There is a special java file called
package-info.java that you place in a package and annotate like this:
@ParentPackage("foo")
package com.example.actions;
And in the actual @Interface definition, you just add the package target
like this:
@Target({Elemen
10 matches
Mail list logo
