12:44 a.m.
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: JBossAS-5.0.0.Beta1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
tc6-cluster.aop. We need to sync up. We want to maintain support for the old
Tomcat-specific interface markers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:23 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3858) Update tc6-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=comments#action_12347064 ]
Ben Wang commented on JBAS-3858:
--------------------------------
OK, couple things need to happen here:
1. We should deprecate the org.jboss.web.tc5.session.AopMarker (and InstanceOfAopMarker).
They are there for JDK1.4 annotation and annoc. And PojOCache 2.0 don't support JDK1.4
anymore.
2. Now that we use JDK5.0, I'd also propose we just use the annotations in PojoCache,
e.g., org.jboss.cache.pojo.PojoCacheable (but please also be aware of that I may need to
change the annotation name before this Friday, see
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986033#...).
3. Originally, we need Oberserver and Obervable pattern to subscribe to POJO field change
event. We won't need that anymore since now PojoCache 2.0 provides PojoCacheListener
event that can emit field changes. tc6 can subscribe to the event directly.
4. As a result, we would need tc6-cluster.aop to only consist of jboss-aop.xml. That
jboss-aop.xml will be a copy of pojocache-aop.xml in the distro (similar to *-service.xml
convention).
Another question will then be how can a user run "aopc" to pre-process the POJO?
He will need:
1. put the classes under all/lib in the classpath. Or maybe just jboss-cache.jar,
pojocache.jar, and jboss-aop-jdk50.jar is enough, I haven't verified.
2. put tc6-cluster.aop (or equivalently, pojocache-aop.xml) in the classpath
3. User class lib (can also include additional 3rd party one as well)
to generate the byte code weaving. Maybe we can provide a script to do that.
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: JBossAS-5.0.0.Beta1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
tc6-cluster.aop. We need to sync up. We want to maintain support for the old
Tomcat-specific interface markers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:18 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update tc6-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Dimitris Andreadis updated JBAS-3858:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: JBossAS-5.0.0.Beta2
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
tc6-cluster.aop. We need to sync up. We want to maintain support for the old
Tomcat-specific interface markers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:11 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update tc6-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Ben Wang updated JBAS-3858:
---------------------------
Assignee: Jason T. Greene (was: Ben Wang)
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Jason T. Greene
Fix For: JBossAS-5.0.0.Beta3
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
tc6-cluster.aop. We need to sync up. We want to maintain support for the old
Tomcat-specific interface markers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:34 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-3858) Update tc6-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Brian Stansberry reassigned JBAS-3858:
--------------------------------------
Assignee: Brian Stansberry (was: Jason T. Greene)
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta3
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
tc6-cluster.aop. We need to sync up. We want to maintain support for the old
Tomcat-specific interface markers as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Brian Stansberry updated JBAS-3858:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta3)
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Brian Stansberry updated JBAS-3858:
-----------------------------------
Summary: Update jbossweb-cluster.aop to match the current configuration (was:
Update tc6-cluster.aop to match the current configuration)
Description: The pojocache-aop.xml used in JBC 2.0 is quite different from what we
have in jbossweb-cluster.aop. We need to sync up. (was: The pojocache-aop.xml used in
JBC 2.0 is quite different from what we have in tc6-cluster.aop. We need to sync up. We
want to maintain support for the old Tomcat-specific interface markers as well.)
When JBAS-4639 is completed there will no longer be any reason for a difference between
the AS version of the file and the PojoCache version.
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:45 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Brian Stansberry updated JBAS-3858:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta4)
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:11 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Dimitris Andreadis updated JBAS-3858:
-------------------------------------
Component/s: Clustering
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=all ]
Brian Stansberry updated JBAS-3858:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
(was: JBossAS-5.0.0.CR1)
PojoCache 2.2.0 will also include some new elements related to array interception.
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR2
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[ http://jira.jboss.com/jira/browse/JBAS-3858?page=comments#action_12416602 ]
Brian Stansberry commented on JBAS-3858:
----------------------------------------
For CR1 the file now matches the core PojoCache pojocache-aop.xml file, excluding
unrelated stuff that drives PC internals. I'm keeping this open as I'll update it
again to sync up when we move to PC 2.2.0.GA.
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR2
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[
https://jira.jboss.org/jira/browse/JBAS-3858?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-3858:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.GA
(was: JBossAS-5.0.0.CR2)
Moving to 5.0.0.GA as that is when we will integrate PojoCache 2.2.0.GA. I really
don't expect any further changes to this file though.
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: https://jira.jboss.org/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.0.0.GA
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-3858) Update jbossweb-cluster.aop to match the current configuration
[
https://jira.jboss.org/jira/browse/JBAS-3858?page=com.atlassian.jira.plug...
]
Brian Stansberry closed JBAS-3858.
----------------------------------
Resolution: Done
Update jbossweb-cluster.aop to match the current configuration
--------------------------------------------------------------
Key: JBAS-3858
URL: https://jira.jboss.org/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.0.0.GA
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in
jbossweb-cluster.aop. We need to sync up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5922
days inactive
6630
days old
12 comments
6 participants
participants (6)
-
Ben Wang (JIRA) -
Ben Wang (JIRA) -
Brian Stansberry (JIRA)
-
Brian Stansberry (JIRA)
-
Dimitris Andreadis (JIRA)
-
Dimitris Andreadis (JIRA)