it’s perfect indeed.
Thanks shane!
De: Ken Finnigan [mailto:ken@kenfinnigan.me]
Enviada em: quinta-feira, 3 de março de 2011 09:25
Para: Shane Bryzak
Cc: José Rodolfo Carrijo de Freitas; seam-dev(a)lists.jboss.org
Assunto: Re: [seam-dev] SEAMINTL-27
Genius Shane!
Was not aware of that annotation.
José, I think that is the best approach, marking joda-time classes with @Requires for
DateTimeZone. Then developer just needs to override optional dependency to activate it.
Ken
Sent from my iPhone
On Mar 3, 2011, at 7:05, Shane Bryzak <sbryzak(a)redhat.com> wrote:
Solder also has a @Requires annotation which you might find useful - it allows you to
specify a class name, and if that class is found on the classpath then that bean will be
installed.
On 03/03/11 22:00, José Rodolfo Carrijo de Freitas wrote:
Morning guys,
I’m working at the issue
https://issues.jboss.org/browse/SEAMINTL-27 and the problem here
is caused by an optional dependency.
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<optional>true</optional>
</dependency>
So, I was talking with ken, and there´re two suggested approaches:
1. Mark the implementation classes that use joda-time with @Veto and require the developer
to override that setting through XML Config if they want to use them
2. Mark the set of JDK dateTime and joda-time classes as two Alternative options and
require the developer to specify which one to use.
What option do you think is the better approach? Do you have any other idea?
Either way we require the developer to say what he wants to use, This could be useful in
some situations, but I guess that most of times, people just want to use the feature
regarding what seam uses in its back.
What do you think?
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev