2:23 p.m.
I see that in 1.4.x, we have this lovely situation:
jboss-cache.jar includes the o.j.c.aop.(InstanceOf)AopMarker marker
interfaces.
jboss-cache-jdk5.jar also includes the
o.j.c.aop.annotation.(InstanceOf)AopMarker annotations, but does not
include the marker interfaces.
Thus, in AS 4.2, if I want to support both annotation styles for FIELD
granularity replication, there is no JBC jar that I can integrate to
allow it. I'd like to support both, since it seems user friendly to
support the different methods the PojoCache examples use. (Note: we're
deprecating the redundant o.j.web.tomcat.tc5.session.AopMarker marker
interfaces, so good support of the standard PojoCache markers is even
more important.)
If 1.4.1.SP1 isn't in QA yet (I saw another fix this AM) can we fix
this? I see no reason not to include the marker interfaces in the
jboss-cache-jdk5.jar. It's not like they don't work in JDK 5 or
something.
This isn't critical, but this whole area is really user unfriendly
(don't get me started on the atrocious aopc) and doing what we can to
make it easier is a good thing.
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
2:54 p.m.
At the AOP-level, the flavour of JBoss AOP deployed determines if we look
for annotationc'ed interfaces (jdk 1.4), or real annotations (jdk 5), so
there is not a lot that can be done in this regard at present...
If you have some suggestions for aopc, please send them my way :-) I've been
thinking of tidying it up before we get AOP 2.0.0.GA out
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org
[mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of
Brian Stansberry
Sent: 02 February 2007 20:24
To: jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] PojoCache annotations and marker interfaces
I see that in 1.4.x, we have this lovely situation:
jboss-cache.jar includes the o.j.c.aop.(InstanceOf)AopMarker
marker interfaces.
jboss-cache-jdk5.jar also includes the
o.j.c.aop.annotation.(InstanceOf)AopMarker annotations, but
does not include the marker interfaces.
Thus, in AS 4.2, if I want to support both annotation styles
for FIELD granularity replication, there is no JBC jar that I
can integrate to allow it. I'd like to support both, since it
seems user friendly to support the different methods the
PojoCache examples use. (Note: we're deprecating the
redundant o.j.web.tomcat.tc5.session.AopMarker marker
interfaces, so good support of the standard PojoCache markers
is even more important.)
If 1.4.1.SP1 isn't in QA yet (I saw another fix this AM) can
we fix this? I see no reason not to include the marker
interfaces in the jboss-cache-jdk5.jar. It's not like they
don't work in JDK 5 or something.
This isn't critical, but this whole area is really user
unfriendly (don't get me started on the atrocious aopc) and
doing what we can to make it easier is a good thing.
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
5:34 a.m.
On 2 Feb 2007, at 20:23, Brian Stansberry wrote:
I see that in 1.4.x, we have this lovely situation:
jboss-cache.jar includes the o.j.c.aop.(InstanceOf)AopMarker marker
interfaces.
jboss-cache-jdk5.jar also includes the
o.j.c.aop.annotation.(InstanceOf)AopMarker annotations, but does not
include the marker interfaces.
Thus, in AS 4.2, if I want to support both annotation styles for FIELD
granularity replication, there is no JBC jar that I can integrate to
allow it. I'd like to support both, since it seems user friendly to
support the different methods the PojoCache examples use. (Note: we're
deprecating the redundant o.j.web.tomcat.tc5.session.AopMarker marker
interfaces, so good support of the standard PojoCache markers is even
more important.)
If 1.4.1.SP1 isn't in QA yet (I saw another fix this AM) can we fix
this? I see no reason not to include the marker interfaces in the
jboss-cache-jdk5.jar. It's not like they don't work in JDK 5 or
something.
I believe QA on this HAS started. The task's been assigned to
Rajesh, although I don't think he's started on the release process
yet. If you think this fix is important enough and quick/easy enough
to get in before Monday AM, go ahead and do it and move the tag for
the affected files. Just remember to ping Rajesh and tell him, in
case he's checked out the srcs already.
This isn't critical, but this whole area is really user
unfriendly
(don't get me started on the atrocious aopc) and doing what we can to
make it easier is a good thing.
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
6506
days inactive
6507
days old
jbosscache-dev@lists.jboss.org
2 comments
3 participants
participants (3)
-
Brian Stansberry -
Kabir Khan -
Manik Surtani