1:05 p.m.
Hi all
The Java EE spec leads would like feedback on how often stereotypes are
"dynamic" vs "static".
A static stereotype is one that is defined in Java code, compiled, and then deployed
without modification from a container extension.
A dynamic stereotype is one that defined in Java code, compiled, and then modified by an
extension.
Another way of putting it is:
* Are there any extensions which modify stereotypes?
* Is this something that is common or not?
This relates to David's metatype proposal.
Pete
1:54 p.m.
I have not seen those dynamic stereotypes in free nature yet.
Actually I'm not using Stereotypes that much at all. Mainly because their usage is
limited by the Java Annotation boundaries.
Imagine the following Stereotype for my Services (I spare out the standard stuff)
@StereoType
@Secured
@Transactional
@ApplicationScoped
public @interface @Service {}
The problem here is that there is no way to 'propagate' any rolesAllowed from
@Service to @Secured, etc.
What I'd like to have is something like
...
public @interface @Service {
String[] rolesAllowed();
TransactionAttributeType transactionType();
}
where the rolesAllowed() would get propagated to the @Secured meta-annotation and
transactionType() to the @Transactional
With such an annotation I could use:
@Service(rolesAllowed={"admin", "editor"}, transactionType =
REQUIRES_NEW)
public String doSomething() {...
But that's not possible with Java Annotations. Or do you have any ideas how to do
that? (without having to manually propagate this in each and every interceptor).
LieGrue,
strub
----- Original Message -----
From: Pete Muir <pmuir(a)redhat.com>
To: cdi-dev(a)lists.jboss.org; deltaspike-dev(a)incubator.apache.org; David Blevins
<david.blevins(a)gmail.com>
Cc:
Sent: Wednesday, May 2, 2012 1:05 PM
Subject: [cdi-dev] Dynamic stereotypes
Hi all
The Java EE spec leads would like feedback on how often stereotypes are
"dynamic" vs "static".
A static stereotype is one that is defined in Java code, compiled, and then
deployed without modification from a container extension.
A dynamic stereotype is one that defined in Java code, compiled, and then
modified by an extension.
Another way of putting it is:
* Are there any extensions which modify stereotypes?
* Is this something that is common or not?
This relates to David's metatype proposal.
Pete
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
2:22 p.m.
Seam JMS supported this functionality (dynamic steroetypes) for a short
period of time. When we saw the behavior inconsistent w/ OWB it was
dropped. It was originally meant to emulate JNDI lookups in an SE
environment.
John
On Wed, May 2, 2012 at 7:54 AM, Mark Struberg <struberg(a)yahoo.de> wrote:
I have not seen those dynamic stereotypes in free nature yet.
Actually I'm not using Stereotypes that much at all. Mainly because their
usage is limited by the Java Annotation boundaries.
Imagine the following Stereotype for my Services (I spare out the standard
stuff)
@StereoType
@Secured
@Transactional
@ApplicationScoped
public @interface @Service {}
The problem here is that there is no way to 'propagate' any rolesAllowed
from @Service to @Secured, etc.
What I'd like to have is something like
...
public @interface @Service {
String[] rolesAllowed();
TransactionAttributeType transactionType();
}
where the rolesAllowed() would get propagated to the @Secured
meta-annotation and transactionType() to the @Transactional
With such an annotation I could use:
@Service(rolesAllowed={"admin", "editor"}, transactionType =
REQUIRES_NEW)
public String doSomething() {...
But that's not possible with Java Annotations. Or do you have any ideas
how to do that? (without having to manually propagate this in each and
every interceptor).
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pmuir(a)redhat.com>
> To: cdi-dev(a)lists.jboss.org; deltaspike-dev(a)incubator.apache.org; David
Blevins <david.blevins(a)gmail.com>
> Cc:
> Sent: Wednesday, May 2, 2012 1:05 PM
> Subject: [cdi-dev] Dynamic stereotypes
>
> Hi all
>
> The Java EE spec leads would like feedback on how often stereotypes are
> "dynamic" vs "static".
>
> A static stereotype is one that is defined in Java code, compiled, and
then
> deployed without modification from a container extension.
>
> A dynamic stereotype is one that defined in Java code, compiled, and then
> modified by an extension.
>
> Another way of putting it is:
>
> * Are there any extensions which modify stereotypes?
> * Is this something that is common or not?
>
> This relates to David's metatype proposal.
>
> Pete
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
2:42 p.m.
It's weird to see the word dynamic next to the word stereotype.
Same as Mark here. We defined one or two @Stereotype's ever since we
started using CDI. We play much more with qualifiers and annotation
litterals.
I don't know if any extentions programatically manipulate them, but I'm
sure it's not common.
For instance, a quick look at seam-solder and seam-faces shows only one
stereotype is defined, and there's no tweaking with it.
fm.
On Wed, May 2, 2012 at 1:54 PM, Mark Struberg <struberg(a)yahoo.de> wrote:
I have not seen those dynamic stereotypes in free nature yet.
Actually I'm not using Stereotypes that much at all. Mainly because their
usage is limited by the Java Annotation boundaries.
Imagine the following Stereotype for my Services (I spare out the standard
stuff)
@StereoType
@Secured
@Transactional
@ApplicationScoped
public @interface @Service {}
The problem here is that there is no way to 'propagate' any rolesAllowed
from @Service to @Secured, etc.
What I'd like to have is something like
...
public @interface @Service {
String[] rolesAllowed();
TransactionAttributeType transactionType();
}
where the rolesAllowed() would get propagated to the @Secured
meta-annotation and transactionType() to the @Transactional
With such an annotation I could use:
@Service(rolesAllowed={"admin", "editor"}, transactionType =
REQUIRES_NEW)
public String doSomething() {...
But that's not possible with Java Annotations. Or do you have any ideas
how to do that? (without having to manually propagate this in each and
every interceptor).
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pmuir(a)redhat.com>
> To: cdi-dev(a)lists.jboss.org; deltaspike-dev(a)incubator.apache.org; David
Blevins <david.blevins(a)gmail.com>
> Cc:
> Sent: Wednesday, May 2, 2012 1:05 PM
> Subject: [cdi-dev] Dynamic stereotypes
>
> Hi all
>
> The Java EE spec leads would like feedback on how often stereotypes are
> "dynamic" vs "static".
>
> A static stereotype is one that is defined in Java code, compiled, and
then
> deployed without modification from a container extension.
>
> A dynamic stereotype is one that defined in Java code, compiled, and then
> modified by an extension.
>
> Another way of putting it is:
>
> * Are there any extensions which modify stereotypes?
> * Is this something that is common or not?
>
> This relates to David's metatype proposal.
>
> Pete
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
--
http://www.suntriprecords.com
4630
days inactive
4630
days old
3 comments
4 participants
participants (4)
-
Fabien Marsaud -
John D. Ament -
Mark Struberg -
Pete Muir