You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: <mat...@jb...> - 2005-06-21 18:02:29
|
Thomas, this will be a welcome change from the potpourri of descriptors we must manage today. Looking forward to seeing your design. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882284#3882284 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882284 |
From: chiba <nu...@jb...> - 2005-06-21 17:46:49
|
Sorry. I faild to copy&paste. The reason of your problem is maybe because you attempted to reload a class. Reloading a class is prohibited by the JVM. If you really want to reload a class, please check javassist.tool.HotSwapper available from CVS HEAD (that will be included in Javassist 3.1) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882282#3882282 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882282 |
From: chiba <nu...@jb...> - 2005-06-21 17:44:03
|
Note: this setting of a field before calling super is similar to how instance inner (nested) classes work, they set the field that points to their outer class before calling their own super constructor. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882280#3882280 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882280 |
From: Scott M S. <sco...@jb...> - 2005-06-21 17:01:34
|
I'm not seeing dev forum postings show up. Is this list address responsive today? =20 xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx=20 =20 =20 |
From: <sco...@jb...> - 2005-06-21 16:47:32
|
One ease of use issue I mentioned on the dev list is having to know how to obtain the xsd file for a given namespace's schema using the current schema driven binding api. The current testscases start with at least the mapping of the root namespace schema using something like: | String url = getResource("xml/mbeanserver/mbean-service_1_0.xsd"); | SchemaBinding schemaBinding = XsdBinder.bind(url); | Another example of a document that incorporates 3 namespaces with associated schemas is: | String url = getResource("xml/mbeanserver/mbean-service_1_0.xsd"); | SchemaBinding schemaBinding = XsdBinder.bind(url); | schemaBinding.setSchemaResolver(new SchemaBindingResolver(){ | public SchemaBinding resolve(String nsUri, String localName) | { | if("urn:jboss:login-config2".equals(nsUri)) | { | String url = getResource("xml/mbeanserver/login-config2.xsd"); | return XsdBinder.bind(url); | } | else if("urn:jboss:user-roles".equals(nsUri)) | { | String url = getResource("xml/mbeanserver/user-roles.xsd"); | return XsdBinder.bind(url); | } | else | { | throw new JBossXBRuntimeException("Unrecognized namespace: " + nsUri); | } | } | }); | Ideally this is information that the jbossxb user should not have to supply as it could be obtained from the schemaLocation attribute, or a more generic namespace to xsd mapping catalog. The latter is needed for all of the standard jboss schemas and corresponds to how we handle j2ee dtds, xsds and jboss dtds. Can the existing org.jboss.util.xml.JBossEntityResolver be used/updated for this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882272#3882272 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882272 |
From: <sco...@jb...> - 2005-06-21 16:43:18
|
Without javadoc annotations (which are scheduled for java6), I don't see how this can be done in general as we have no requirement for source code creation. I don't see that the current jaxb2.0 spec (Early Draft 2 Tuesday, March 15, 2005) has any annotation for this purpose either. Perhaps that is something that could be suggested via an email to spe...@js... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882274#3882274 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882274 |
From: ${bb.Guest} <nu...@jb...> - 2005-06-21 09:31:13
|
Hi, I want generate the jboss-portlet.xml , porlet.xml ect by using the portal xdoclet generation exactly like we generate using ejb and web modules. presently i am able to define xdoclet using the eclipse ide. but when i am running the the xdoclet i am getting the following error. BUILD FAILED E:\JbossEclipse\eclipse\workspace\HelloWorld\xdoclet-build.xml:138: taskdef class xdoclet.modules.portlet.PortletDocletTask cannot be found can any body help me? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882234#3882234 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882234 |
From: <aco...@jb...> - 2005-06-21 00:56:53
|
I've been trying to say basically about the same thing, but the site upgrade has hosed me for the last week or so. The Alias thing is a cool "feature" but verify-identiy only needs to assure that us...@fo... - matches the "user" that authenticated and that foo.com matches a domain in the local domain-list. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882215#3882215 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882215 |
From: <sco...@jb...> - 2005-06-21 00:23:05
|
I don't see why session replication and farming should be combined in the same interface. They should be two seperately configured aspects of clustering. We have not done any work to run the JBossJTA service outside of 4.0.x. A minimal 5.x microcontainer should allow for use of the jta service, but nothing to test this has been done as yet so far as I know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882213#3882213 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882213 |
From: oberon777 <nu...@jb...> - 2005-06-20 23:27:01
|
Has anybody seen this exception? Does it have anything to do with a protection domain error people reported a while back (http://jira.jboss.com/jira/browse/JBAOP-126). | [error] failed to transform: org.eclipse.osgi.framework.internal.core.BundleContextImpl.. Do verbose mode if you want full stack trace. | error getting:org.eclipse.osgi.framework.eventmgr.EventListeners. 'addListener' | javassist.CannotCompileException: org/jboss/aop/instrument/Untransformable | at org.jboss.aop.standalone.StandaloneClassPool.toClass(StandaloneClassPool.java:62) | at javassist.CtClass.toClass(CtClass.java:962) | at org.jboss.aop.instrument.TransformerCommon.compileOrLoadClass(TransformerCommon.java:119) | at org.jboss.aop.instrument.CallerTransformer$CallerExprEditor.createOptimizedMethodCalledByMethodInvocationClass(CallerTransformer.java:913) | at org.jboss.aop.instrument.CallerTransformer$CallerExprEditor.modifyMethod(CallerTransformer.java:309) | at org.jboss.aop.instrument.CallerTransformer$CallerExprEditor.edit(CallerTransformer.java:233) | at javassist.expr.ExprEditor.doit(ExprEditor.java:118) | at javassist.CtBehavior.instrument(CtBehavior.java:362) | at org.jboss.aop.instrument.CallerTransformer.applyCallerPointcuts(CallerTransformer.java:69) | at org.jboss.aop.instrument.Instrumentor.applyCallerPointcuts(Instrumentor.java:492) | at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:572) | at org.jboss.aop.AspectManager.translate(AspectManager.java:572) | at org.jboss.aop.AspectManager.transform(AspectManager.java:490) | at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:59) | at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:51) | at sun.instrument.TransformerManager.transform(TransformerManager.java:122) | at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155) | at java.lang.ClassLoader.defineClass1(Native Method) | at java.lang.ClassLoader.defineClass(ClassLoader.java:620) | at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) | at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) | at java.net.URLClassLoader.access$100(URLClassLoader.java:56) | at java.net.URLClassLoader$1.run(URLClassLoader.java:195) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at org.eclipse.osgi.framework.internal.core.Framework.initialize(Framework.java:137) | at org.eclipse.osgi.framework.internal.core.Framework.<init>(Framework.java:95) | at org.eclipse.osgi.framework.internal.core.OSGi.createFramework(OSGi.java:90) | at org.eclipse.osgi.framework.internal.core.OSGi.<init>(OSGi.java:31) | at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:215) | at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:127) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.eclipse.core.launcher.Main.basicRun(Main.java:185) | at org.eclipse.core.launcher.Main.run(Main.java:704) | at org.eclipse.core.launcher.Main.main(Main.java:688) | I would really appreciate any help in solving this problem. My command line looks as follows: | java -mx1024m \ | -Djboss.aop.path="./META-INF/jboss-aop.xml" \ | -javaagent:jboss-aop-jdk50.jar \ | -Djboss.aop.verbose=false \ | -classpath ".:./startup.jar:../lib-50/concurrent.jar:../lib-50/javassist.jar:../lib-50/jboss-aop-jdk50.jar:../lib-50/jboss-common.jar:../lib-50/trove.jar" \ | org.eclipse.core.launcher.Main -install /home/livshits/mining/eclipse -os linux -ws gtk -arch x86 | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882207#3882207 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882207 |
From: <rl...@jb...> - 2005-06-20 21:52:10
|
I've created a new task which will generate a libraries.ent file based on the components contained in the graph which includes the correct version numbers in the classpath. A new target has been created in the secondary-dependency-test.xml file to support this. <target name="generate-lib-file" depends="synchronize"> | <gen-lib-file filename="versionedLibraries.ent" path="../tools/etc/buildmagic/" /> | </target> The target accepts 2 attributes, file name, and the path to where the file should be written. If these are not included, a default filename and path are used. The general premise is that for each component in the graph which the visitor encounters the following will be written to the file: 1) An identifier comment 2) A root property name 3) A library property name (now with version number included in the path) 4) A list of path elements (the jar files) The values used are currently (this may need to be adjusted) based off of the component id as shown below for component "antlr". <!-- antlr --> | <property name="antlr.antlr.root" value="${project.thirdparty}/antlr"/> | <property name="antlr.antlr.lib" value="${antlr.antlr.root}/2.7.5H3/lib/" | <path id="antlr.antlr.classpath"> | <pathelement path="${antlr.antlr.lib}/antlr.jar"/> | </path> For some entries in the existing libraries.ent file, various naming schemes were used for the property name. Finding a common method to faithfully reproduce them programatically may be troublesome, but I think we can get close. To see this in action execute the following commands: mkdir test cd test cvs checkout jbossas cvs checkout tools cd jbossas ant -f secondary-dependency-test.xml generate-lib-file cd ../tools/etc/buildmagic emacs versionedLibraries.ent Ruel Loehr JBoss QA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882195#3882195 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882195 |
From: oberon777 <nu...@jb...> - 2005-06-20 20:40:12
|
I should mention that this in the context of applying some aspects to Eclipse. It is possible that Eclipse has its own highly hacked classloader and the two don't interact properly? I am relly quite puzzled by not getting pointcut matches. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882188#3882188 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882188 |
From: <ad...@jb...> - 2005-06-20 20:29:21
|
This is the design forums. If you want to ask for help, use the user forums!!!! If you want to know what is in a release, use the release notes. The JBoss forums are not a mechanism whereby you can get every frivilous question answered without doing some research for yourself. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882186#3882186 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882186 |
From: iwadasn <nu...@jb...> - 2005-06-20 20:17:45
|
Was this ever put in? Does it exist in 4.0.2? If so, how do you turn this on. I would like to see the standard java JMX beans in the jmx-console. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882184#3882184 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882184 |
From: oberon777 <nu...@jb...> - 2005-06-20 17:25:57
|
When using load-time loading, is it necessary to specify the class path where all the files to be instrumented can be located? Or is the class loader going to take care of that as long as the application runs? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882165#3882165 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882165 |
From: <ad...@jb...> - 2005-06-20 16:30:21
|
For future information it is 11 paces. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882146#3882146 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882146 |
From: <roy...@jb...> - 2005-06-20 16:24:10
|
Julien pointed me to this thing a while ago: http://www.portletbridge.org/ I haven't looked deeper in to it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882142#3882142 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882142 |
From: <roy...@jb...> - 2005-06-20 16:20:20
|
Am I the only one confused by this post? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882141#3882141 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882141 |
From: <roy...@jb...> - 2005-06-20 16:18:46
|
The site is still running on Nukes CMS. This is the Portal dev list. So... stand up, walk 20 paces over to Sohil on your way to smoke, and tell him what you found. He has the source for the site. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882140#3882140 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882140 |
From: <ad...@jb...> - 2005-06-20 16:08:15
|
The forums are corrupted (at least for me). The problem is caused by the -- in the comment for forum page name, since when I make it one - it works. | <tr> | <td class="row1" align="center" valign="middle" height="50"><img src="modules/bb/templates/subSilver/images/folder_new_big.gif" width="46" height="25" alt="New posts" title="New posts" /></td> | <td class="row1" width="100%" height="50"><span class="forumlink"> <a href="index.html?module=bb&op=viewforum&f=92" class="forumlink">TODO -- DEVELOPMENT</a><br /> | <!-- forum title hack --> | <!-- jbosspagename=[TODO -- DEVELOPMENT] --> | <!-- forum title hack --> | </span> <span class="genmed">Wanna help? Start here. <br /> | </span><span class="gensmall">  </span></td> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882139#3882139 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882139 |
From: bstansberry <nu...@jb...> - 2005-06-20 14:30:23
|
Cluster Configuration To deploy a JBossCacheCluster, the user would add an element like the following to the Host section of TC's server.xml file, replacing the standard Cluster element: | <Cluster | className="org.jboss.web.tomcat.tc5.JBossCacheCluster" | cacheObjectName="jboss.cache:service=TomcatClusteringCache" | clusterName="Tomcat-Cluster" | clusterProperties="conf/jgroups-default.xml" | isolationLevel="REPEATABLE_READ" | cacheMode="REPL_ASYNC" | lockAcquisitionTimeout="15000" | snapshotMode="instant" | snapshotInterval="2000" | useJK="false" | defaultReplicationTrigger="SET_AND_NON_PRIMITIVE_GET" | defaultReplicationGranularity="attribute" | useLocalCache="true"\ | transactionManagerLookupClass="org.jboss.cache.UserTransactionTransactionManagerLookup" | /> | Most of the attributes have the exact same function as the equivalent attributes in the JBoss -service.xml files. I'll provide reasonable defaults for them, so most could be ignored. A few deserve comment: 1) clusterProperties This attribute controls configuration of the underlying JGroups channel. The problem here is the most effective way to configure this is with an embedded XML element (the way its handled in the JBoss MBean deployment descriptors). But, as far as I can tell the Commons Digester library that TC uses to parse server.xml does not support parsing text as an Element and passing the resulting Element to an object as a property value. (Someone please tell me if I'm wrong). This makes configuring JGroups more difficult, and probably the easiest way to do it is with an external config file. The clusterProperties attribute can take one of three kinds of values: a) A relative path to a JGroups config file located under $CATALINA_BASE. If such a file can be found, JBossCacheCluster will convert it to a file URL and pass it to JGroups, which parses it. b) A URL pointing to a JGroups config file. c) An old-style JGroups configuration string. 2) cacheObjectName Object name under which the TreeCache is to be registered. This serves two purposes: a) Before instantiating a TreeCache, JBossCacheCluster looks to see if a cache is already registered under the given cacheObjectName. If one is, that cache is used (and any other cache configuration attributes are ignored). b) If no cache is already registered under cacheObjectName, JBossCacheCluster creates the TreeCache and registers it under that name. This approach gives users the flexibility to configure different caches under different Host elements, but also to have separate Cluster elements under different Hosts share a TreeCache. Currently Tomcat only supports nesting a Cluster element under a Host element. It seems logical to me that this element also be allowed under the Engine element. I'll take this up on the Tomcat dev list. (I got this working with no trouble using JBossCacheCluster; haven't had a chance to see if SimpleTcpCluster will work as a child of Engine). 3) transactionManagerLookupClass Has the same function as it does in the standard TreeCache deployment descriptors. The tricky thing here is the user will need to configure a TransactionManger and have Tomcat register it in JNDI. I've done this using the GlobalJndiResources element in server.xml, which I believe is the standard way. For my dev work I've used JOTM as my transaction manager. Will JBossJTA run outside of JBoss? I've written a new implementation of TransactionManagerLookup that looks for a transaction manager in JNDI under "java:/UserTransaction". With JOTM, a single class implements both UserTransaction and TransactionManager, so typically a user registering JOTM would register it under java:/UserTransaction so webapps could conveniently get a UserTransaction. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882113#3882113 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882113 |
From: zoid <nu...@jb...> - 2005-06-20 12:45:50
|
Turns out the problem was on my end... But IMO, it should have worked anyway. It turns out, foo() was defined one level higher, in X, the superclass of A. So, even though B is an instance of A (and of X), since the method foo() is defined in X, it looks as though, I must use $instanceof(x.y.z.X) to match executions of foo(). So what I have is class X that defines foo() and class A that extends X. Both in a jar, under lib. Then I deploy a class B that extends A and does not override foo(). In that case: execution(public boolean $instanceof(x.y.z.X)->foo()) WORKS execution(public boolean $instanceof(x.y.z.A)->foo()) does NOT work I haven't looked at the code but I'm guessing JBossAOP implements the latter pointcut by transforming only class A. So that the execution of foo() within class X isn't "seen". Is that right? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882095#3882095 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882095 |
From: legolas <nu...@jb...> - 2005-06-20 08:13:20
|
It is not necessarily restricted to portlets in the same app, but The spec (PLT.15.3) describes it as anonymous wrote : Any object stored in the session using the APPLICATION_SCOPE is available to any other portlet that belongs to the same portlet application and that handles a request identified as being a part of the same session. This means that anything stored on the session with APPLICATION_SCOPE must be visible to other portlets in the same application, but can be visible to other portlets outside the same application, depending on the container implementation. Hope this helps... Marcel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882067#3882067 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882067 |
From: bstansberry <nu...@jb...> - 2005-06-20 06:41:12
|
Farmed Deployment and the Tomcat Cluster interface To do the JBCACHE-13 work we are creating a new implementation of Tomcat's Cluster interface. Tomcat's existing Cluster implementation not only provides session replication but also supports farmed deployments of webapps. The primary issue of this post is to discussion whether an/or how we want to support farm deployments. Tomcat's existing implementation of its Cluster interface is the class org.apache.catalina.cluster.SimpleTcpCluster. This class actually provides two main services -- HttpSession replication across the cluster and a form of farm deployment of webapps across the cluster. The Cluster interface itself clearly specifies the requirements for session replication. It also includes some methods related to farm deployments, but these methods are all deprecated and are actually only implemented as no-ops by SimpleTcpCluster. SimpleTcpCluster actually implements farm deployment using a separate subinterface, CatalinaCluster. We need to decide whether we want to support a farm deployment capability in the new Cluster implementation. The methods related to farm deployment are deprecated in the interface and are not really implemented by the existing implementation. But, the existing implementation does support farm deployments, so not doing it in the new implementation would represent a loss of functionality. IF we choose to provide farmed deployment support, there are a number of approaches to getting it done: 1) Have the new JBossCacheCluster class subclass SimpleTcpCluster and inherit its farm deployment functionality. The concern I have with this approach is it's really bolting one semi-complex class on top of another complex class, with the two classes being maintained by separate, unrelated people. 2) Have JBossCacheCluster itself instantiate and deploy an instance of SimpleTcpCluster and delegate farm deployment work to it. This would be similar to what it already does with its TreeCache instance. This would loosen the coupling with the SimpleTcpCluster code, but there would still be the danger of incompatible changes being made in SimpleTcpCluster. I need to look further to see if this is even feasible. 3) Basically reimplement SimpleTcpCluster's farm deployment functionality inside JBossCacheCluster. An issue here is SimpleTcpCluster uses TC's own cluster messaging code (they can't use JGroups 'cause of LGPL). It seems odd for a JBoss project to not use JGroups. 4) Come up with a new farm deployment implementation using JGroups and/or JBossCache. This would be a big increase in the scope of the project. Any thoughts on this would be most appreciated :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882060#3882060 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882060 |
From: bstansberry <nu...@jb...> - 2005-06-20 06:01:45
|
For the last few weeks I've been working on getting JBossCache-based session replication to work in standalone Tomcat 5.5. I've gotten a pretty reasonable version working, and want to post what I doing on this thread so others can be informed and provide any inputs they would like. (I've been discussing things with Ben Wang and earlier with Remy Maucherant). Basically this task breaks down into two main elements -- getting a TreeCache deployed when Tomcat starts and getting JBossCacheManager instances deployed when distributable webapps are deployed. To do this, I've: 1) Created a new implementation of the TC Cluster interface, JBossCacheCluster. It's role is basically to: a) Interact with the TC deployment system -- get config attributes from server.xml, implement the TC Lifecycle interface. b) Instantiate a TreeCache and register it in JMX. c) Instantiate and configure JBossCacheManager instances when requested by the Tomcat deployer. 2) Created new class StandaloneJBossCacheManager, subclass of JBossCacheManager. I expect that with a bit of refactoring this subclass' functionality can be merged back into JBossCacheManager. Instances of this class can be created by JBossCacheCluster, or directly by TC's webapp deployer code. The latter happens if the user specifies a element in the context.xml the describes their webapp. This latter approach allows a user to set the replicationGranularity and replicationTrigger atttributes to something other than the cluster-wide defaults. In embedded JBoss/Tomcat these two attributes are set via jboss-web.xml. Added functionality in StandaloneJBossCacheManager is basically: a) Exposes a few property attributes so JBossCacheCluster or the TC deployer can set them without using the WebMetaData object used with embedded JBoss/Tomcat. b) Handles the start()/stop() process differently, to account for the fact that it can't count on being configured by JBoss' TomcatDeployer. Key things it must do: -- Detect if it was instantiated by the TC deployer rather than JBossCacheCluster. If it was, it finds the JBossCacheCluster and passes itself to it so the cluster can set cluster-wide properties (e.g. snapshot mode, useJK, etc). -- Instantiate and install its ClusteredSessionValve. I'll discuss some of the issues related to the above in separate posts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882057#3882057 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882057 |