Re: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Seems like a rather independent feature that can't cause any harm. 3.2 is fine as is 3.0 as long as there truly are no backward compatibility issues with existing services. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Sacha Labourey [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED]; Adam Heath [EMAIL PROTECTED]; Jboss-Dev [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 11:48 PM Subject: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD Scott, Do you accept the beanshell sub-deployer in pre-HEAD branches? 3.2? 3.0? Cheers, Sacha --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
OK, I will backport it to 3.2 (not sure about doing it for 3.0) -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Scott M Stark Envoyé : jeudi, 9 janvier 2003 09:23 À : [EMAIL PROTECTED] Objet : Re: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD Seems like a rather independent feature that can't cause any harm. 3.2 is fine as is 3.0 as long as there truly are no backward compatibility issues with existing services. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Sacha Labourey [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED]; Adam Heath [EMAIL PROTECTED]; Jboss-Dev [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 11:48 PM Subject: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD Scott, Do you accept the beanshell sub-deployer in pre-HEAD branches? 3.2? 3.0? Cheers, Sacha --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Just get it into the 3.0 build and provide a commented out setup of the deployer. That way people can use if they want, but its not enabled by default until it sees some action. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Sacha Labourey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 09, 2003 1:04 AM Subject: RE: Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD OK, I will backport it to 3.2 (not sure about doing it for 3.0) --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
On Tue, 7 Jan 2003, Sacha Labourey wrote: Hello, Yesterday I commited a BeanShell (BSH, www.beanshell.org) sub-deployer in HEAD. It is in module varia and you can find its lib in varia/output/lib/bsh-deployer.sar. It allows you to hot-deploy *.bsh files in /deploy. [snip] /me goes looking for a towel, as his monitor just got all sticky. This is EXTREMELY cool. We can now support upgrades of whatever, which means fixing databases(adding/remove fields, fixing data), and various other things. If something like this could also be added to J2EE deployments(in META-INF dirs), then I'd be even more excited. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
I wonder if it would be possible to put the .bsh in a .sar in your .ear? Not sure, haven't tried it.. And agreed, this bsh support really is interesting.. -Original Message- From: Adam Heath [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 11:52 AM To: Jboss-Dev Cc: jBoss-User Mailing List; [EMAIL PROTECTED] Subject: Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD On Tue, 7 Jan 2003, Sacha Labourey wrote: Hello, Yesterday I commited a BeanShell (BSH, www.beanshell.org) sub-deployer in HEAD. It is in module varia and you can find its lib in varia/output/lib/bsh-deployer.sar. It allows you to hot-deploy *.bsh files in /deploy. [snip] /me goes looking for a towel, as his monitor just got all sticky. This is EXTREMELY cool. We can now support upgrades of whatever, which means fixing databases(adding/remove fields, fixing data), and various other things. If something like this could also be added to J2EE deployments(in META-INF dirs), then I'd be even more excited. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
If something like this could also be added to J2EE deployments(in META-INF dirs), then I'd be even more excited. Well, have you simply tried to put a xxx.bsh file inside your JAR, SAR or EAR (not war though): it should deploy thanks to the russian dolls packaging feature. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [Beanshell-users] RE: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
James Higginbotham writes: I wonder if it would be possible to put the .bsh in a .sar in your .ear? Sounds excruciating :-). Won't it tickle? --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
OK, I've just tested and the russian doll feature wasn't working with .bsh files. It is now fixed. Furthermore, I just tested this case: I added a xxx.bsh file inside a ejb.jar file. Result: the deployment process respect the create/start/stop/destroy steps i.e. you have this sequence: - create bsh script - create ejbs - start bsh script - start ejbs - ... and so on. So it works. Cheers, sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Adam Heath Envoye : mercredi, 8 janvier 2003 19:47 A : Jboss-Dev Cc : jBoss-User Mailing List; [EMAIL PROTECTED] Objet : [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD On Wed, 8 Jan 2003, Sacha Labourey wrote: If something like this could also be added to J2EE deployments(in META-INF dirs), then I'd be even more excited. Well, have you simply tried to put a xxx.bsh file inside your JAR, SAR or EAR (not war though): it should deploy thanks to the russian dolls packaging feature. Oh, hmm, forgot about that. Yeah, that would work, but is not what I want. I'd like a way to have some bit of code called for the start/stop/init/destroy methods, in parallel to the ear service methods. So, when ear.init() is called, my own code is also called. What you suggest would be a separate deployment underneath the ear. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Scott? RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Scott, Do you accept the beanshell sub-deployer in pre-HEAD branches? 3.2? 3.0? Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Adam Heath Envoye : jeudi, 9 janvier 2003 06:47 A : Jboss-Dev Cc : [EMAIL PROTECTED]; [EMAIL PROTECTED] Objet : RE: [JBoss-user] RE: [Beanshell-users] Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD On Wed, 8 Jan 2003, Sacha Labourey wrote: OK, I've just tested and the russian doll feature wasn't working with .bsh files. It is now fixed. Furthermore, I just tested this case: I added a xxx.bsh file inside a ejb.jar file. Result: the deployment process respect the create/start/stop/destroy steps i.e. you have this sequence: - create bsh script - create ejbs - start bsh script - start ejbs - ... and so on. So it works. Hmm. Most excellent. I really wish the J2EE spec had features that allowed for some kind of user-supplied code to be ran when items were deployed. Having this feature in JBoss is going to rock. Is it possible to have this back-ported to 3.0? My gut instinct says this wouldn't require modifications to the jboss code itself, but I may be wrong. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Beanshell-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/beanshell-users --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Do you want this feature on 3.2? Very much! Cheers --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Hello,
Yesterday I commited a BeanShell (BSH, www.beanshell.org) sub-deployer in
HEAD. It is in module varia and you can find its lib in
varia/output/lib/bsh-deployer.sar.
It allows you to hot-deploy *.bsh files in /deploy.
SIMPLE USAGE: client-only
=
In its simple usage, the script will act as a simple client-script making
invocations on other objects. Each script can follow the
org.jboss.system.Service interface i.e. the create, start, stop and destroy
calls. You can implement only a subset of those. Thus, a very simply
one-line script can be: Simple.bsh:
void start() { System.out.println (I'm called!); }
that's it.
ADVANCED USAGE: server script!
==
But it is almost as easy to make your script a JBoss service fully
invocable/administrable through JMX! For this, your script can implement any
of the methods of the following interface:
public interface ScriptService
extends org.jboss.system.Service
{
public String objectName ();
public String[] dependsOn ();
public Class[] getInterfaces ();
public void setCtx (ServiceMBeanSupport wrapper);
}
You can implement the objectName method to choose your own MBean ObjectName.
You can implement the dependsOn method to return a set of JMX MBean
ObjectName (as string) on which you depends (for service lifecyle).
You can implement the getInterfaces method to return the set of interfaces
that you *say* your script do implement. Your wrapper will analyse these
interfaces and fully generate the associated JMX MBeanInfo (the script
wrapper is a Dynamic MBean).
Example, let's say you have this interface:
public interface MyIntf
{
public void doThat();
public String getRWString ();
public void setRWString (String val);
public String getROString ();
}
You could then provide this script:
String name = bla;
String objectName () { return jboss.scripts:service=myService; }
Class[] getInterfaces () { return new Class[] {MyIntf.class}; }
void create () { System.out.println (Create called on me); }
void doThat () { System.out.println (doThat called); }
String getRWString() { return super.name; }
void setRWString(String bla) { super.name = bla; }
String getROString() { return I am read-only!; }
Then, not only can you invoke methods and get/set attributes on your script
using JMX, you can also browse your scripts using the
http://localhost:8080/jmx-console/ and see all available methods/attributes
(MBeanInfo is generated by the DynamicMBean script wrapper)
Infos on BeanShell are available here: www.beanshell.org
Do you want this feature on 3.2?
Cheers,
Sacha
P.S.: This e-mail is cross-posted to the beanshell-users ML.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Sounds very interesting.. I wonder how it might help to integrate Jboss
and Emacs/JDEE, since they use the bsh to perform Lisp-Java
integration..
James
-Original Message-
From: Sacha Labourey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 3:57 AM
To: Jboss-Dev
Cc: jBoss-User Mailing List; [EMAIL PROTECTED]
Subject: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Hello,
Yesterday I commited a BeanShell (BSH, www.beanshell.org)
sub-deployer in HEAD. It is in module varia and you can find
its lib in varia/output/lib/bsh-deployer.sar.
It allows you to hot-deploy *.bsh files in /deploy.
SIMPLE USAGE: client-only
=
In its simple usage, the script will act as a simple
client-script making invocations on other objects. Each
script can follow the org.jboss.system.Service interface i.e.
the create, start, stop and destroy calls. You can implement
only a subset of those. Thus, a very simply one-line script
can be: Simple.bsh:
void start() { System.out.println (I'm called!); }
that's it.
ADVANCED USAGE: server script!
==
But it is almost as easy to make your script a JBoss service
fully invocable/administrable through JMX! For this, your
script can implement any of the methods of the following interface:
public interface ScriptService
extends org.jboss.system.Service
{
public String objectName ();
public String[] dependsOn ();
public Class[] getInterfaces ();
public void setCtx (ServiceMBeanSupport wrapper);
}
You can implement the objectName method to choose your own
MBean ObjectName. You can implement the dependsOn method to
return a set of JMX MBean ObjectName (as string) on which you
depends (for service lifecyle). You can implement the
getInterfaces method to return the set of interfaces that you
*say* your script do implement. Your wrapper will analyse
these interfaces and fully generate the associated JMX
MBeanInfo (the script wrapper is a Dynamic MBean).
Example, let's say you have this interface:
public interface MyIntf
{
public void doThat();
public String getRWString ();
public void setRWString (String val);
public String getROString ();
}
You could then provide this script:
String name = bla;
String objectName () { return jboss.scripts:service=myService; }
Class[] getInterfaces () { return new Class[] {MyIntf.class}; }
void create () { System.out.println (Create called on me); }
void doThat () { System.out.println (doThat called); }
String getRWString() { return super.name; }
void setRWString(String bla) { super.name = bla; }
String getROString() { return I am read-only!; }
Then, not only can you invoke methods and get/set attributes
on your script using JMX, you can also browse your scripts
using the http://localhost:8080/jmx-console/ and see all
available methods/attributes (MBeanInfo is generated by the
DynamicMBean script wrapper)
Infos on BeanShell are available here: www.beanshell.org
Do you want this feature on 3.2?
Cheers,
Sacha
P.S.: This e-mail is cross-posted to the beanshell-users ML.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something
2 See! http://www.vasoftware.com
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
