[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: New Asynchronous Aspect .
Some documentation about AOP Asynchronous Method Invocation available on the WIKI. http://jboss.org/wiki/Wiki.jsp?page=AOPAsynchronousMethodInvocation Rgds,Claude View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831238#3831238 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831238 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: RT: Ideas to take from JAMES and Mail Scripting
As you said, JavaScript is probably adequate for the task and more admin friendly. It may be possible to support multiple scripting languages provided they support limiting their domain. Meaning I only want you to script what I expose to you nothing more. JavaScript (aka ECMA) is probably a must if we intend for admins/power-admins to be able to write things like matchers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831235#3831235 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831235 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: RT: Ideas to take from JAMES and Mail Scripting
"Until you get" -- and I thought you were planning to be one of us? Membership in the us is low, just send real good code :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831234#3831234 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831234 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/winxp/1.4.1_06) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Apr 18 02:13:48 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 02:13:47,796 WARN [NamingContext] Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to connect to server localhost:1099. Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099. Root exception is java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:434) at java.net.Socket.connect(Socket.java:384) at java.net.Socket.(Socket.java:291) at java.net.Socket.(Socket.java:199) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:185) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1182) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:513) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:506) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1195) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:513) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:506) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Exception in thread "main" JBOSS SHUTDOWN FAILED === Sun Apr 18 02:13:48 GMTDT 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.1_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01) Java HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode) --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: RT: Ideas to take from JAMES and Mail Scripting
I like the idea of a mail solutions framework. Until you get the Exchange functionality going that will probably be the bread and butter. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831222#3831222 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831222 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: RT: Ideas to take from JAMES and Mail Scripting
Have you heard of Groovy? Apparently it's a newer Java-based scripting language that doesn't have the funkiness of Jython syntax. Javascript would be adequate I think. Probably more "admin" friendly. WWMCSED? What would MCSEs do? ;-) Hit my blog here: Links for Andy's links all together in linkable form. Steve View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831221#3831221 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831221 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Fluid AOP
Pretty much the tcl is set whenever a call enters into a container, be it jmx, ejb, web. Its needed when transitioning from the microkernel into a deployment context that can introduce new classes or class versions due to a deployment. It would generally seem that the TCL is the more typical level at which you would want to associate aspects as at least the metadata is likely to be coming from the application context. I have been noticing some issues with using the TCL as a key due to the fact that we tend to have noop class loaders to differentiate deployment contexts, and it can be a little hard to control how certain searches for resources behave. Another thing that is difficult is cleaning up classes on redeployment. The java.lang.ClassLoader in at least sun's impl has a private array of the classes loaded that cannot be cleared by subclasses. What I'm seeing with extensive holders of the TCL is that its difficult to clear everything, and this can lead to the use of stale classes, and leaks when frameworks make use of caches keyed to class statics. Because there are a fair number of issues with the current class loading that cannot be changed, I'm thinking that we need to be looking at another thread context at the key rather than the thread context class loader. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831218#3831218 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831218 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Why the two jboss logging frameworks?
Ok, thanks. Scott Stark Chief Technology Officer JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Adrian Brock > Sent: Saturday, April 17, 2004 6:01 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Why the two jboss logging frameworks? > > I'll fix it in both 3.2 and head > My fault for not keeping head in line. > > Regards, > Adrian > --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: JBoss Deployment
Hi, Stan. Nothing special about this Fibo tutorial. I just followed the instructions step by step and it woked. I even changed the internal code from UTF-8 to Big5(Chinese, Taiwan) and it woked too. Can you tell me how to attach my files to this post or I just send an email attached with my files to you if you give me your email address. Then you can compare yours with mine. Because I am quite new to Eclipse, Jboss and Xdoclet, you have search any minor mistakes you might make. Good luck. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831216#3831216 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831216 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_10) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Apr 17 23:26:52 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:18: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:29: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerRegistry private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerRegistry.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:15: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:16: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:34: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanTransportPreference private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTransportPreference.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:24: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:25: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:52: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTracker private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTracker.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:11: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:12: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:35: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTrackerFilter private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTrackerFilter.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\JMXSubsystemInvocationHandler.java:35: cannot resolve symbol symbol : variable LoggerManager location: class org.jboss.mx.remoting.JMXSubsystemInvocationHandler private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(JMXSubsystemInvocationHandler.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanNotificationCache.java:34: cannot resolve symbol symbol : variable LoggerManager location: class org.jboss.mx.remoting.MBeanNotificationCache private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanNotificationCache.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:36: cannot resolve symbol symbol : variable LoggerM
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Apr 17 23:28:56 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === symbol : class Logger location: class org.jboss.mx.remoting.MBeanNotificationCache private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanNotificationCache.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:11: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:12: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:36: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerClientInvokerProxy private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerClientInvokerProxy.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:17: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:18: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:29: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerRegistry private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerRegistry.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:15: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:16: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:34: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanTransportPreference private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTransportPreference.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:24: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:25: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:52: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTracker private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTracker.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:11: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:12: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:35: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTrackerFilter private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTrackerFilter.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Apr 17 20:28:09 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === symbol : class Logger location: class org.jboss.mx.remoting.MBeanNotificationCache private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanNotificationCache.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:11: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:12: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:36: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerClientInvokerProxy private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerClientInvokerProxy.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:17: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:18: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:29: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerRegistry private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerRegistry.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:15: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:16: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:34: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanTransportPreference private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTransportPreference.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:24: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:25: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:52: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTracker private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTracker.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:11: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:12: package org.jboss.mx.logging does not exist import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:35: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTrackerFilter private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTrackerFilter.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_10) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Apr 17 20:26:00 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:18: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerRegistry.java:29: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanServerRegistry private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanServerRegistry.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:15: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:16: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanTransportPreference.java:34: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.MBeanTransportPreference private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTransportPreference.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:24: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:25: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTracker.java:52: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTracker private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTracker.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:11: cannot resolve symbol symbol : class Logger location: package logging import org.jboss.mx.logging.Logger; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:12: cannot resolve symbol symbol : class LoggerManager location: package logging import org.jboss.mx.logging.LoggerManager; ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\tracker\MBeanTrackerFilter.java:35: cannot resolve symbol symbol : class Logger location: class org.jboss.mx.remoting.tracker.MBeanTrackerFilter private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(MBeanTrackerFilter.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\JMXSubsystemInvocationHandler.java:35: cannot resolve symbol symbol : variable LoggerManager location: class org.jboss.mx.remoting.JMXSubsystemInvocationHandler private static final transient Logger log = LoggerManager.getLoggerManager().getLogger(JMXSubsystemInvocationHandler.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanNotificationCache.java:34: cannot resolve symbol symbol : variable LoggerManager location: class org.jboss.mx.remoting.MBeanNotificationCache private static final Logger log = LoggerManager.getLoggerManager().getLogger(MBeanNotificationCache.class.getName()); ^ D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\MBeanServerClientInvokerProxy.java:36: cannot resolve symbol symbol : variable LoggerM
[JBoss-dev] [ jboss-Bugs-877172 ] NullPointerException in LoadMgr3
Bugs item #877172, was opened at 2004-01-14 22:59 Message generated for change (Comment added) made by anders5737 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=877172&group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Tim McCune (javajedi) Assigned to: Scott M Stark (starksm) Summary: NullPointerException in LoadMgr3 Initial Comment: I get this error out of JBoss 3.2.2 on a fairly regular basis. I'm still not sure exactly how to reproduce it, but since it's an NPE, I'm hoping that someone can track down what would cause it to happen fairly easily. Once it occurs for a particular class, the only fix is to restart JBoss. I never had this problem on 3.2.0. java.lang.NullPointerException at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:119) at org.jboss.mx.loading.UnifiedClassLoader3.loadClassImpl(UnifiedClassLoader3.java:169) at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:123) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) Looking at the code, the UnifiedLoaderRepository3 that is passed into beginLoadTask as the 2nd parameter must be null. UnifiedClassLoader3, line 118 does a null check for repository just a few lines before calling loadClassImpl, so I'm assuming that this is a valid state for the class loader to be in. That would mean that beginLoadTask in LoadMgr3 needs to handle the situation where repository is null. -- Comment By: Anders Eriksson (anders5737) Date: 2004-04-17 21:14 Message: Logged In: YES user_id=295842 I can consistently repeat this problm. I get it upon when trying to display an error page in Tapestry 3.0 rc3. I can save a copy of my project for future reference. Caused by: java.lang.NullPointerException at org.jboss.mx.loading.LoadMgr3.beginLoadTask (LoadMgr3.java:119) at org.jboss.mx.loading.UnifiedClassLoader3.loadClassImpl (UnifiedClassLoader3.java:169) at org.jboss.mx.loading.UnifiedClassLoader3.loadClass (UnifiedClassLoader3.java:123) at java.lang.ClassLoader.loadClass (ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:302) at org.apache.oro.text.regex.Perl5Matcher.__setLastMatchResult (Unknown Source) at org.apache.oro.text.regex.Perl5Matcher.getMatch (Unknown Source) at org.apache.tapestry.parse.TemplateParser.processComponent Start(TemplateParser.java:1049) at org.apache.tapestry.parse.TemplateParser.startTag (TemplateParser.java:947) at org.apache.tapestry.parse.TemplateParser.parse (TemplateParser.java:591) at org.apache.tapestry.parse.TemplateParser.parse (TemplateParser.java:419) at org.apache.tapestry.engine.DefaultTemplateSource.construct TemplateInstance(DefaultTemplateSource.java:442) at org.apache.tapestry.engine.DefaultTemplateSource.parseTem plate(DefaultTemplateSource.java:416) at org.apache.tapestry.engine.DefaultTemplateSource.getOrPars eTemplate(DefaultTemplateSource.java:389) at org.apache.tapestry.engine.DefaultTemplateSource.findStanda rdTemplate(DefaultTemplateSource.java:366) at org.apache.tapestry.engine.DefaultTemplateSource.findTempla te(DefaultTemplateSource.java:269) at org.apache.tapestry.engine.DefaultTemplateSource.getTempla te(DefaultTemplateSource.java:181) at org.apache.tapestry.BaseComponent.readTemplate (BaseComponent.java:95) at org.apache.tapestry.BaseComponent.finishLoad (BaseComponent.java:135) at org.apache.tapestry.pageload.PageLoader.constructComponen t(PageLoader.java:520) -- Comment By: georke (jdwn) Date: 2004-03-08 17:06 Message: Logged In: YES user_id=993121 I'm getting the same error in JBoss 3.2.3 with WASP integration version 4.6.1. What I'm doing is the following: I start JBoss I redeploy my EJB I want to redeploy my webservice and then I get the Bug. Does somebody know when this bug will be solved? Thnx! -- Comment By: Scott M Stark (starksm) Date: 2004-01-30 19:51 Message: Logged In: YES user_id=175228 3.2.0 did not null the association between the UnifiedClassLoader and the UnifiedLoaderRepository, so you are likely using classes from the previous deployment. This can lead to ClassCastException, LinkageErrors and IllegalAccessErrors depending on the usage of classes. If you have an example that illustrates the problem attach it or send it to me. If the JCE layer is caching classes there may be a way to work around this. If its truly a bug I need an example. -- Comment By: Jas
[JBoss-dev] [Mail Services] - RT: Ideas to take from JAMES and Mail Scripting
Take a look at this: http://james.apache.org/provided_matchers_2_1.html, and this: http://james.apache.org/provided_mailets_2_1.html. James has an API called the "Mailet API". Its a great idea but kind of an abortive impelmentation: http://james.apache.org/mailet_api_2_1.html. " The Mailet API is currently in its second revision. Although, the Mailet API is expected to undergo substantial changes in the near future, it is our aim that existing Mailets that abided purely by the prior Mailet API interfaces will continue to run with the revised specification. " I don't want to hook into their Mailet API, but rather implement some of the concepts mixed with some of our own. Later I'll start pushing to come together and come up with a "standard" which implements some from both. I know there are a (primarily uninvolved in more than commenting) number of peace/love commentors, but the secret to good design is divergence and reconvergence. Its premature to cooperate. Go look at the best standards and worst. The worst were cooperative from the start, design by committee. The best were competitive and then agreements were met on which ideas had been the best. What I'd like to do is see us make a MailListenerChain interface which is itself a MailListener. The MailListener interface is ATM not supposed to pull mails off the stack. A ChainableMailListener would plug into the MailListenerChain and COULD pull messages off the stack. >From there we implement a concept like Matchers which can plug into a >ChainableMailListener. ChainableMailListeners should ALSO be MailListeners so they CAN operate in either mode. If they are not part of a chain, they do not consume messages from the stack. If they are part of the chain, they do consume messages from the stack where appropriate. Next, I'd like to do more than just statically compiled Java objects for mail processing. For what I'd like to see us do, you need to look at Cocoon's flowscript. Cocoon is a vernable hotbed of good ideas gone bad. Flow is one of them. http://cocoon.apache.org/2.1/userdocs/flow/api.html Cocoon uses a Mozilla project called Rhino: http://www.mozilla.org/rhino/. Rhino is a Java implementation of JavaScript (for all irony). There is also jyThon (http://www.ociweb.com/jnb/archive/jnbMar2001.html) but there are reasons that I favor JavaScript to python. The most important is that I see some admin types as writing these mail scripts. JavaScript is more well known than python and probably anyone even somewhat introduced to the technical field has had a basic introduction to it. I mean this is the first language of scripting. What the idea would be. Matchers could be implemented in JavaScript as well as Java. We'd supply an object model which protects you from doing anything other than matching mails. Secondly, a RhinoChainableMailListener could be used to do more advanced things with routed mails. You could implement a set of spam filters for instance. This has multiple implications. We could also provide a system for syndicating JavaScript matchers for Spam filtering. Basically an RSS feed from a server could be aggregated to provide an automatic method for syndicating filters for spam. Meaning if I trust jboss.org and JBoss.org adds a matcher to its spam filter for all mails containing "V|4GR4" then it would be added to my matcher. If your mail server trusted mine to provide this info, it would be automatically added to yours as well! So obviously I've left out some details and there are some rough spots to work out. In particular a potential impedence mismatch between MailListener, ChainableMailListener, matchers and mailets (part of the mail listeners). I don't think that many people will use Maillisteners, rather they'll favor ChainableMailListeners. However, SOME people will. Remember, we're a solution framework as much as a mail server and not a single solution to a single problem or simple mail server (there are plenty of those). I'd like to get the idea flow flowing. Lets hear them. Please feedback and help me work out the details of this idea, ask questions, fight with me, etc. Also post your own RTs for other ideas we might proceed. Remember to put on your aspetos suit. We're all friends here but its important to fight through the ideas. Thanks, -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831198#3831198 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831198 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMA
[JBoss-dev] jboss-head build.18 Build Successful
View results here -> http://tck2.jboss.com/cc/?log=log20040417134819Lbuild.18 BUILD COMPLETE - build.18Date of build: 04/17/2004 13:48:19Time to build: 18 minutes 29 secondsLast changed: 04/17/2004 13:35:15Last log entry: Use logging from the common module not jmx logging Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (45)modifiedejortjmx/src/main/org/jboss/mx/modelmbean/ModelMBeanInvoker.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/test/implementation/logging/support/LogObject.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/test/implementation/interceptor/SharedInterceptorTEST.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/server/registry/BasicMBeanRegistry.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/notification/AsynchNotificationBroadcasterSupport.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/javax/management/loading/MLet.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/test/implementation/interceptor/support/LogObject.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/util/MBeanInstaller.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/interceptor/AbstractInterceptor.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/interceptor/AbstractSharedInterceptor.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/org/jboss/mx/interceptor/Interceptor.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/test/implementation/logging/LogManagerTEST.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/test/implementation/logging/LoggingSUITE.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/javax/management/modelmbean/ModelMBeanAttributeInfo.javaUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/test/implementation/ImplementationSUITE.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/DefaultLoggerAdapter.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/DefaultLoggerAdapterFactory.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/DefaultLoggerContextSelector.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/Logger.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerAdapter.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerAdapterFactory.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerAdapterFactorySupport.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerAdapterSupport.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerContext.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerContextSelector.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerManager.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/LoggerPermission.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/NullLoggerAdapter.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/NullLoggerAdapterFactory.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/SystemLogger.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/package.htmlUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/file/FileLogger.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/file/FileLoggerFactory.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/logging/file/package.htmlUse logging from the common module not jmx loggingmodifiedejortjmx/src/main/javax/management/StandardMBean.javaUse logging from the common module not jmx loggingdeletedejortjmx/src/main/org/jboss/mx/loggin
[JBoss-dev] [Mail Services] - Pre-testing for M1RC1
I'm doing my pre-testing for M1RC1 and I have to say, I'm impressed. The TLS and SSL support is awesome. Also sending mail feels remarkably faster than JAMES (which I use presently) even using SSL!!! I feel really good about this release. Everyone especially: Eric, MikeA, MikeK and Kabir should feel really proud of themself. Eric got sucked into work but he wrote the first POP stuff and rounded out SMTP. May he rest in peace and enjoy his cubelife haha. :-) MikeK came in around that time but got I think got frustrated by how latent I got as I was traveling around. He came back later when I pinged him to finish the SSL stuff. Kabir and MikeA came in about the same time. Mike really got cracking on rounding a number of things out. He even went to JBoss Advanced with Bill to fascillitate his JBoss knowledge. I'm particularly glad he's taken up the test kit. Kabir came in did some stuff and then went on Vacation. However, when he came back he came back with a vengence. He fixed lots of bugs and implemented some things that lingered for way to long. Bounce messages and some message duplication come to mind the most. All of you are greatly valued and I look forward to working with you on making the imminent Release candidate into a release and working on the next one. You guys are top notch. Keep it up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831197#3831197 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831197 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: JBoss Deployment
Hi albertfang, Some of your message could not be seen. Can you tell me any trick to follow the Tutorial? What's wrong in our code? Thanks, -stan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831193#3831193 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831193 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Observable Pattern on the WIKI
this tx observable pattern is everywhere in Jboss View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831184#3831184 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831184 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: TODO: Script Runner
go ahead. See the TestServer and all for how I think we should set up. Just start the pieces we need inside of the unit tests. Later we'll have multinode tests. Right now we need basic tests like "if there is user XYZ in the respository and I send him a mail from himself, does it get delivered" and the such. End to end testing of the SMTP/POP stuff. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831183#3831183 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831183 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Observable Pattern on the WIKI
GOF does it my way. It would be trivial to write an alternate ObservableLight :-) Transaction synchronization would also help to avoid multiple fine grained fireChanged() events inside a transaction. Similar to JBossCacheAOP View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831182#3831182 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831182 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Fluid AOP
Blogged about this: http://jboss.org/jbossBlog/blog/bburke/?permalink=Fluid+AOP.html Thoughts anybody? I still need to understand when/how context classloader gets set in JBoss. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831181#3831181 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831181 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Observable Pattern on the WIKI
I'll have JDK 1.5 annotation support sometime next week in CVS. Doing another beta of JBoss AOP soon too. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831180#3831180 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831180 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Observable Pattern on the WIKI
I hear you on the usage of Subject. I saw it is the way the GOF named it. I still prefer "Observable". Getting at the state is done by passing the reference to the subject in your implementation. It makes for a great and simple implementation. If we could pass some metainformation as to what has changed (name of the field for example), it would make for more finegrained callbacks from the observer. What does GOF say? marcf View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831179#3831179 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831179 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Observable Pattern on the WIKI
this is great work adrian, Bill, I think what I hear you say is that we can now deploy a self contained aspect. The aspect knows where he wants to be bound. The aspect could export its pointcuts, he knows he wants to listen on set* etc. It will make for superior deployment formats for aspects. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831178#3831178 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831178 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-936962 ] XDoclet access to /resources/additional_values.xml
Bugs item #936962, was opened at 2004-04-17 15:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936962&group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ralf Folkerts (folkerts) Assigned to: Nobody/Anonymous (nobody) Summary: XDoclet access to /resources/additional_values.xml Initial Comment: Version: JBoss-IDE 1.2.230 on Eclipse 3.0M8 OS: Linux (Gentoo) JDK: 1.4.2_04 (Sun) When trying to refresh the XDoclet-Info (Window/Preferences/JBoss IDE/XDoclet/"Refresh XDolet Modules" & Code Assist/"Refresh XDoclet Data") the JBoss IDE tries to access a file "!SESSION Apr 17, 2004 15:49:11.935 - java.version=1.4.2_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE !ENTRY org.jboss.ide.eclipse.xdoclet.assist 4 0 Apr 17, 2004 15:49:11.936 !MESSAGE Internal Error !STACK 0 java.io.FileNotFoundException: /resources/additional_values.xml (Datei oder Verzeichnis nicht gefunden) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at java.io.FileReader.(FileReader.java:41) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLPersistenceManager(XDocletAssistPlugin.java:382) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLDocument(XDocletAssistPlugin.java:344) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLDocument(XDocletAssistPlugin.java:329) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.addValuesToDocletTree(XDocletAssistPlugin.java:139) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin$1.run(XDocletAssistPlugin.java:219) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) !ENTRY org.jboss.ide.eclipse.xdoclet.assist 4 0 Apr 17, 2004 15:49:12.38 !MESSAGE Internal Error !STACK 0 java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:283) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:400) at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getRefreshedDocletTree(XDocletAssistPlugin.java:228) at org.jboss.ide.eclipse.xdoclet.assist.ui.XDocletPreferencePage$1.widgetSelected(XDocletPreferencePage.java:65) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1953) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1726) at org.eclipse.jface.window.Window.runEventLoop(Window.java:670) at org.eclipse.jface.window.Window.open(Window.java:650) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:72) at org.eclipse.jface.action.Action.runWithEvent(Action.java:881) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:550) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:502) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:435) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:939) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1953) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1726) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1562) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1536) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:257) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:139) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:277) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:239) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:117) 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:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:267) at org.eclipse
[JBoss-dev] [ jboss-Bugs-936924 ] RFE: support mysql transactions retry
Bugs item #936924, was opened at 2004-04-17 17:20 Message generated for change (Comment added) made by eprst You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Konstantin Sobolev (eprst) Assigned to: Nobody/Anonymous (nobody) Summary: RFE: support mysql transactions retry Initial Comment: Hi Under heavy load Mysql/INNODB can at any moment throw SQL deadlock exception, even on a simple attempt to insert a single row, and they say that there's "nothing dangerous" and code must be ready to restart transaction at any moment: http://dev.mysql.com/doc/mysql/en/Innodb_deadlocks.html See example 4.1 (section 4.4) here: http://dev.mysql.com/doc/connector/j/en/index.html As far as I understand, container should take care of such situations and behave much like in case of retriable ADE. There's nothing CMT entity bean can do here itself except for constructing and throwing vendor-specific ADE. Thanks -- >Comment By: Konstantin Sobolev (eprst) Date: 2004-04-17 18:56 Message: Logged In: YES user_id=118051 I meant CMP entity bean. BMP can't do anything either. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: XDoclets in Version 1.2.230 does not work with eclipse 3
Hi, same here :-( I just started Eclipse from c/l and got: --- Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-ejb-module-1.2b3-dev.jar!/META-INF/xtags.xml | Exception while reading: ejb.home null Attention: Can't add org.jboss.ide.eclipse.xdoclet.assist.model.conditions.Or to Condition org.jboss.ide.eclipse.xdoclet.assist.model.conditions.IsClass | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-java-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-jboss-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-jmx-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-web-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-xdoclet-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-ejb-module-1.2b3-dev.jar!/META-INF/xtags.xml | Exception while reading: ejb.home null Attention: Can't add org.jboss.ide.eclipse.xdoclet.assist.model.conditions.Or to Condition org.jboss.ide.eclipse.xdoclet.assist.model.conditions.IsClass | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-java-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-jboss-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-jmx-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-web-module-1.2b3-dev.jar!/META-INF/xtags.xml | Process: jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-xdoclet-module-1.2b3-dev.jar!/META-INF/xtags.xml | Unhandled event loop exception | Reason: | java.lang.NullPointerException | P | --- The Log-File has: --- !SESSION Apr 17, 2004 15:49:11.935 - | java.version=1.4.2_04 | java.vendor=Sun Microsystems Inc. | BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE | !ENTRY org.jboss.ide.eclipse.xdoclet.assist 4 0 Apr 17, 2004 15:49:11.936 | !MESSAGE Internal Error | !STACK 0 | java.io.FileNotFoundException: /resources/additional_values.xml (Datei oder Verzeichnis nicht gefunden) | at java.io.FileInputStream.open(Native Method) | at java.io.FileInputStream.(FileInputStream.java:106) | at java.io.FileInputStream.(FileInputStream.java:66) | at java.io.FileReader.(FileReader.java:41) | at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLPersistenceManager(XDocletAssistPlugin.java:382) | at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLDocument(XDocletAssistPlugin.java:344) | at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.getXMLDocument(XDocletAssistPlugin.java:329) | at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin.addValuesToDocletTree(XDocletAssistPlugin.java:139) | at org.jboss.ide.eclipse.xdoclet.assist.XDocletAssistPlugin$1.run(XDocletAssistPlugin.java:219) | at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) | --- So it seems to be related to the mentioned "additional_values.xml" which is not found?! Does anyone have a solution? Regards, _ralf_ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831171#3831171 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831171 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why the two jboss logging frameworks?
Thomas or Tom, A lot of the JMX testsuite tests for JBossMX are failing. Either the tests should be fixed or the reason why they fail analysed. Last time I ran it, there were three "known issues" non of them important. Regards, Adrian On Sat, 2004-04-17 at 14:00, Adrian Brock wrote: > I'll fix it in both 3.2 and head > My fault for not keeping head in line. > > Regards, > Adrian > > On Sat, 2004-04-17 at 13:42, Adrian Brock wrote: > > The JMX logging framework was removed from 3.2.0 but never > > from head. When Tom backported jmx from head into 3.2.4RC1 > > he also copied the old jmx logging framework. > > > > Regards, > > Adrian > > > > On Sat, 2004-04-17 at 13:25, Scott M Stark wrote: > > > In trying to cleanup the logging for bug [ 936465 ] JCA layer has > > > invalid assumption about Log4jLoggerPlugin > > > https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i > > > d=22866&atid=376685 > > > > > > I see that we have two seperate frameworks: > > > jmx org.jboss.mx.logging > > > comon org.jboss.logging > > > > > > Is this a legacy issue from before jmx depending on the common module? > > > There can only > > > be one jboss logging abstraction. > > > > > > > > > Scott Stark > > > Chief Technology Officer > > > JBoss Group, LLC > > > > > > > > > > > > > > > > > > --- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > > > ___ > > > JBoss-Development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Adrian Brock Director of Support Back Office JBoss Inc. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-936924 ] RFE: support mysql transactions retry
Bugs item #936924, was opened at 2004-04-17 17:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Konstantin Sobolev (eprst) Assigned to: Nobody/Anonymous (nobody) Summary: RFE: support mysql transactions retry Initial Comment: Hi Under heavy load Mysql/INNODB can at any moment throw SQL deadlock exception, even on a simple attempt to insert a single row, and they say that there's "nothing dangerous" and code must be ready to restart transaction at any moment: http://dev.mysql.com/doc/mysql/en/Innodb_deadlocks.html See example 4.1 (section 4.4) here: http://dev.mysql.com/doc/connector/j/en/index.html As far as I understand, container should take care of such situations and behave much like in case of retriable ADE. There's nothing CMT entity bean can do here itself except for constructing and throwing vendor-specific ADE. Thanks -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why the two jboss logging frameworks?
I'll fix it in both 3.2 and head My fault for not keeping head in line. Regards, Adrian On Sat, 2004-04-17 at 13:42, Adrian Brock wrote: > The JMX logging framework was removed from 3.2.0 but never > from head. When Tom backported jmx from head into 3.2.4RC1 > he also copied the old jmx logging framework. > > Regards, > Adrian > > On Sat, 2004-04-17 at 13:25, Scott M Stark wrote: > > In trying to cleanup the logging for bug [ 936465 ] JCA layer has > > invalid assumption about Log4jLoggerPlugin > > https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i > > d=22866&atid=376685 > > > > I see that we have two seperate frameworks: > > jmx org.jboss.mx.logging > > comon org.jboss.logging > > > > Is this a legacy issue from before jmx depending on the common module? > > There can only > > be one jboss logging abstraction. > > > > > > Scott Stark > > Chief Technology Officer > > JBoss Group, LLC > > > > > > > > > > > > --- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > > ___ > > JBoss-Development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Adrian Brock Director of Support Back Office JBoss Inc. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: object pooling detrimental to performance
It wouldn't even be testing what I thought it'd be testing. I wonder what the real cutoff points are between 1. The VM developer 2. The Container developer 3. The container user (using JSP, other services on top of the container) Anyways, I'll be quiet about things now :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831170#3831170 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831170 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why the two jboss logging frameworks?
The JMX logging framework was removed from 3.2.0 but never from head. When Tom backported jmx from head into 3.2.4RC1 he also copied the old jmx logging framework. Regards, Adrian On Sat, 2004-04-17 at 13:25, Scott M Stark wrote: > In trying to cleanup the logging for bug [ 936465 ] JCA layer has > invalid assumption about Log4jLoggerPlugin > https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i > d=22866&atid=376685 > > I see that we have two seperate frameworks: > jmx org.jboss.mx.logging > comon org.jboss.logging > > Is this a legacy issue from before jmx depending on the common module? > There can only > be one jboss logging abstraction. > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > > > > --- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Adrian Brock Director of Support Back Office JBoss Inc. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMS on JBoss (JMS/JBoss)] - Re: ChangeNotes: 3.2.4
Bug Fix: Catch unchecked exceptions generated by the ping operations Catch unchecked exceptions from the user's ExceptionHandler Avoids uncaught Runtime exceptions killing the ping task/clock daemon View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831167#3831167 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831167 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: object pooling detrimental to performance
Okay. I'm glad the VM is good at that. Like your JCA FAQ says, "Are you *sure* you want JCA?" Steve View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831168#3831168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831168 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Why the two jboss logging frameworks?
In trying to cleanup the logging for bug [ 936465 ] JCA layer has invalid assumption about Log4jLoggerPlugin https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i d=22866&atid=376685 I see that we have two seperate frameworks: jmx org.jboss.mx.logging comon org.jboss.logging Is this a legacy issue from before jmx depending on the common module? There can only be one jboss logging abstraction. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: object pooling detrimental to performance
I don't like nifty or cool. It just over complicates things and makes things buggy. 10 is nothing like enought for a test. The JIT doesn't even kick in until you thousands of repetitions. JITs are bettter at this than you could ever be and will only get better over time. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831164#3831164 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831164 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMS on JBoss (JMS/JBoss)] - Re: Improving message selector performance
Supporting multiple selectors is too complicated for an initial version. Rebuilding the HashMap (don't use a hashtable or vector or any collection that does synchronization unless you are lazy - often you are already synchronized on some other object) should be optimized in conjunction with this work. http://www.jboss.org/index.html?module=bb&op=viewtopic&t=46186 where you would have to the optimized selector's value in a db column with an index over it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831163#3831163 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831163 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Mail Services] - Re: TODO: Script Runner
great news for M1RC1. i'm minimally tidying up/filling out some of the code (mainly script runner) and plan to commit shortly. but i noticed in another forum thread you mentioned not to commit till after RC1, and i wasn't sure that would apply here. (just let me know if so and i'll postpone). with regard to ports and external jboss-mail servers etc, the junit tests which run these scripts fail with explanatory failure messages, so if someone runs the tests without running against a full mail server the failure messages will indicate the scripts couldn't connect. i think this behaviour should hold us over till we figure out the best way to set the script runner up. mike View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831162#3831162 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831162 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMX on JBoss (JBoss/JMX)] - Re: Providing metadata, services to pojo resources
"[EMAIL PROTECTED]" wrote : Generically it is a callback interface like
MBeanRegistration
| for services that want to know about their container and their configuration
|
|
| | public interface ContainerRegistration
| | {
| |void setContainer(Container container);
| |void setMetaData(MetaData metaData);
| | }
| |
I would generalize it a tad further, following the per invocation EJB context model we
have in EJB containers:
| public interface ContainerRegisration
| {
| void setInvocationContext(Context ctx);
| }
|
where we give, per invocation, access to the component to the metadata via an
invocation API, this gives the same per invocation granularity we have today in EJBs
for caller principal metadata, for example (for per container, or VM or cluster
metadata you just keep passing the same metadata references for all invocations, this
should not cause additional overhead).
My .02
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831159#3831159
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831159
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: JBoss Deployment
Mine is working smoothly. Unfortunately, I don't know how to attach my files to this post. Maybe Ｉ ｃａｎ ｅ－ｍａｉ ｙｏｕ ｉｆ ｙｏｕ ｇｉｖｅ ｍｅ ｙｏｕｒ ｅｍａｉｌ ａｄｄｒｅｓｓ． View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831158#3831158 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831158 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMS on JBoss (JMS/JBoss)] - Re: Improving message selector performance
Genman, With regard to your proposal, what's happenning on server's restart? Is the hashtable rebuilt at startup? Regards, Stephane View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831154#3831154 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831154 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
