Re: Old activemq and activecluster
Jules Gosnell wrote: > (2) The reason for the large number of dependencies is WADI's > pluggability. The dependency tree pulls in all of the s/w with which > WADI integrates, including AC/AMQ. However, the Geronimo integration > will only require a small subset of these deps to run. You'll need to > check with Gianny, but I believe that AC/AMQ is one of the dependencies > that can be pruned in this way... - If you are pulling all this together > via maven2, then you will want a large element in your WADI > . Jules, Why don't you make your pom register most of the dependencies as optional, so it's up to the end user what they want pulled in? Jeff
Re: Old activemq and activecluster
nager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [115,40] cannot resolve symbol symbol : class DistributableValueFactory location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [116,20] cannot resolve symbol symbol : class StandardSessionWrapperFactory location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [120,20] cannot resolve symbol symbol : class DummyRouter location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [128,20] cannot resolve symbol symbol : class DummyPartitionManager location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [172,26] cannot access org.codehaus.wadi.InvocationContext file org/codehaus/wadi/InvocationContext.class not found contextualiser.contextualise(context, beanId, null, null, false); /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [180,42] create(org.codehaus.wadi.Invocation) in org.codehaus.wadi.impl.StandardManager cannot be applied to () /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [182,27] cannot resolve symbol symbol : method getId () location: interface org.codehaus.wadi.Session /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [214,19] org.apache.openejb.cluster.server.DefaultEJBClusterManager.OpenEJBManage rConfig is not abstract and does not override abstract method callback (org.codehaus.wadi.Manager) in org.codehaus.wadi.ManagerConfig --jason On Oct 26, 2006, at 12:59 AM, Jules Gosnell wrote: Jason Dillon wrote: And it looks like the upgrade from wadi 2.0m1 to 2.0m2-SNAPSHOT is non-trivial. I see a ton of "org.codehaus.wadi.gridstate" related symbols missing and a bunch of things like missing "ProxiedLocation" and "InvocationContext". I think someone who knows all this wadi muck is going to need to look at this. muck ! :-) Jason, Gianny will know about the finer points of this. I think that you are probably seeing the fallout of (1) refactoring between m1 and m2 and (2) the large WADI dependency tree... (1) provided that external interfaces (or those used by gbean/ spring assemblies), internal api changes should not affect you. I'm not sure of the details of Gianny's integration, but if these changes have impacted it, then he will need to update it. (2) The reason for the large number of dependencies is WADI's pluggability. The dependency tree pulls in all of the s/w with which WADI integrates, including AC/AMQ. However, the Geronimo integration will only require a small subset of these deps to run. You'll need to check with Gianny, but I believe that AC/AMQ is one of the dependencies that can be pruned in this way... - If you are pulling all this together via maven2, then you will want a large element in your WADI . I hope this helps and does not muddy the water too much. If you need more specifics, like which deps are actually required, Gianny and I could put you together a list... just shout. Jules We need to get this resolved so we don't ship different versions of activemq/activeio/activecluster junk with G. --jason On Oct 25, 2006, at 6:11 PM, Jason Dillon wrote: Blah... wadi needs to be upgraded as well :-( --jason On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote: Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
Jason Dillon wrote: And it looks like the upgrade from wadi 2.0m1 to 2.0m2-SNAPSHOT is non-trivial. I see a ton of "org.codehaus.wadi.gridstate" related symbols missing and a bunch of things like missing "ProxiedLocation" and "InvocationContext". I think someone who knows all this wadi muck is going to need to look at this. muck ! :-) Jason, Gianny will know about the finer points of this. I think that you are probably seeing the fallout of (1) refactoring between m1 and m2 and (2) the large WADI dependency tree... (1) provided that external interfaces (or those used by gbean/spring assemblies), internal api changes should not affect you. I'm not sure of the details of Gianny's integration, but if these changes have impacted it, then he will need to update it. (2) The reason for the large number of dependencies is WADI's pluggability. The dependency tree pulls in all of the s/w with which WADI integrates, including AC/AMQ. However, the Geronimo integration will only require a small subset of these deps to run. You'll need to check with Gianny, but I believe that AC/AMQ is one of the dependencies that can be pruned in this way... - If you are pulling all this together via maven2, then you will want a large element in your WADI . I hope this helps and does not muddy the water too much. If you need more specifics, like which deps are actually required, Gianny and I could put you together a list... just shout. Jules We need to get this resolved so we don't ship different versions of activemq/activeio/activecluster junk with G. --jason On Oct 25, 2006, at 6:11 PM, Jason Dillon wrote: Blah... wadi needs to be upgraded as well :-( --jason On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote: Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
ctory location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [116,20] cannot resolve symbol symbol : class StandardSessionWrapperFactory location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [120,20] cannot resolve symbol symbol : class DummyRouter location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [128,20] cannot resolve symbol symbol : class DummyPartitionManager location: class org.apache.openejb.cluster.server.DefaultEJBClusterManager /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [172,26] cannot access org.codehaus.wadi.InvocationContext file org/codehaus/wadi/InvocationContext.class not found contextualiser.contextualise(context, beanId, null, null, false); /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [180,42] create(org.codehaus.wadi.Invocation) in org.codehaus.wadi.impl.StandardManager cannot be applied to () /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [182,27] cannot resolve symbol symbol : method getId () location: interface org.codehaus.wadi.Session /Users/jason/ws/geronimo/openejb2/modules/openejb-core/src/main/java/ org/apache/openejb/cluster/server/DefaultEJBClusterManager.java: [214,19] org.apache.openejb.cluster.server.DefaultEJBClusterManager.OpenEJBManage rConfig is not abstract and does not override abstract method callback (org.codehaus.wadi.Manager) in org.codehaus.wadi.ManagerConfig --jason On Oct 26, 2006, at 12:59 AM, Jules Gosnell wrote: Jason Dillon wrote: And it looks like the upgrade from wadi 2.0m1 to 2.0m2-SNAPSHOT is non-trivial. I see a ton of "org.codehaus.wadi.gridstate" related symbols missing and a bunch of things like missing "ProxiedLocation" and "InvocationContext". I think someone who knows all this wadi muck is going to need to look at this. muck ! :-) Jason, Gianny will know about the finer points of this. I think that you are probably seeing the fallout of (1) refactoring between m1 and m2 and (2) the large WADI dependency tree... (1) provided that external interfaces (or those used by gbean/ spring assemblies), internal api changes should not affect you. I'm not sure of the details of Gianny's integration, but if these changes have impacted it, then he will need to update it. (2) The reason for the large number of dependencies is WADI's pluggability. The dependency tree pulls in all of the s/w with which WADI integrates, including AC/AMQ. However, the Geronimo integration will only require a small subset of these deps to run. You'll need to check with Gianny, but I believe that AC/AMQ is one of the dependencies that can be pruned in this way... - If you are pulling all this together via maven2, then you will want a large element in your WADI . I hope this helps and does not muddy the water too much. If you need more specifics, like which deps are actually required, Gianny and I could put you together a list... just shout. Jules We need to get this resolved so we don't ship different versions of activemq/activeio/activecluster junk with G. --jason On Oct 25, 2006, at 6:11 PM, Jason Dillon wrote: Blah... wadi needs to be upgraded as well :-( --jason On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote: Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
And it looks like the upgrade from wadi 2.0m1 to 2.0m2-SNAPSHOT is non-trivial. I see a ton of "org.codehaus.wadi.gridstate" related symbols missing and a bunch of things like missing "ProxiedLocation" and "InvocationContext". I think someone who knows all this wadi muck is going to need to look at this. We need to get this resolved so we don't ship different versions of activemq/activeio/activecluster junk with G. --jason On Oct 25, 2006, at 6:11 PM, Jason Dillon wrote: Blah... wadi needs to be upgraded as well :-( --jason On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote: Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
Blah... wadi needs to be upgraded as well :-( --jason On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote: Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
Submit a patch. -dain On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote: Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Re: Old activemq and activecluster
Looks like openejb2 is still using old ActiveMQ jars. Can we get those deps upgraded plz? --jason On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote: Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
Old activemq and activecluster
Anyone know why we are still seeing old activemq and activecluster bits? [WARNING] POM for 'activecluster:activecluster:pom:1.1- SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. --jason
