|How I think it should be done is...
|
|1) Forget about dealing with dependencies in the ServiceDeployer, this
|should be done by the AutoDeployer because that way we can specify
|dependencies between all deployable files i.e. between ear's and sar's and
|jar's and rar's etc.
good point
|2) Sars should contain jars, a jboss-service.xml and a directory structure.
yes
|3) The directory structure thing is kinda curly because some services (like
|a db) would want the directory structure to be set up the first time it was
|deployed but NOT over-written on subsequent deployements (because it
|contains persistent data). Other files, like config files, you would
|probably want to be copied over to import a new configuration from the sar.
I see... you are correct.
though the config files should really be in jmx lingo.
Somewhat related, we should specify many directories (could write in same
structure) but specify whether it is "removed on undeployment".
I say this because I see a part of our deployer that is really an installer
and clearly the directory structure should be removed in some cases (say
your service is temporary), and not in other (you want it the first time you
install). As such it appears clearly as a management operation. Jason,
pay attention man, here is how you see "NEEDED" management operations, let
them scream "fixme" all by themselves. You don't hear this feature
screaming "fixme"? then don't ;-)
|That's my two cents, I have been thinking about writing some code
please! go ahead!
|and trying
|it out but I suddenly got real busy at work and haven't had time.
you guys still don't get it?
THIS is *real* work...
the rest is work for companies that dissapear overnight in a global economy
that is sinking.
This is the REAL work, and latch onto it my friends, cause the future is
ours.
Turn on that third eye, let the noise and agitation around you vanish
see through the code
code!
marcf
PS: sure I understand the need to pay the bills, believe me
|
|Cheers,
|David
|
|> -----Original Message-----
|> From: marc fleury [mailto:[EMAIL PROTECTED]]
|> Sent: Friday, September 21, 2001 8:57 AM
|> To: [EMAIL PROTECTED]
|> Subject: RE: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
|>
|>
|> |Hot-deploying the Jetty service works fine.
|>
|> What happened to the idea of creating your own directory
|> layout space upon
|> deployment from the JSR I thought that was very useful...
|>
|> do you still require this? it would be very useful for me to
|> work with a
|> specific case
|>
|> marcf
|>
|> |
|> |Hot-undeploying generates the following exception :
|> |
|> |
|> |[AutoDeployer] Auto undeploy of
|> |file:/mnt/megalodon/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0
|> |.0alpha/deploy/jetty-service.xml
|> |
|> |[JettyService] Stopping
|> |[Jetty] Stopped SocketListener on 0.0.0.0:8080
|> |[JettyService] Stopped
|> |[JettyService] Destroying
|> |[Jetty] Destroy SocketListener on 0.0.0.0:8080
|> |[Jetty] Deregister Jetty:Jetty=0,SocketListener=0
|> |[JettyService] Destroyed
|> |[ServiceDeployer] Mbean exception while executing undeploy on
|> |[Ljava.lang.Object;@333a0e
|> |javax.management.InstanceNotFoundException: :service=Jetty
|> | at
|> |com.sun.management.jmx.MBeanServerImpl.unregisterMBean(MBeanServerI
|> |mpl.java:945)
|> |
|> | at
|> |org.jboss.system.ServiceController.undeploy(ServiceController
|> .java:248)
|> | at java.lang.reflect.Method.invoke(Native Method)
|> | at
|> |com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
|> .java:1628)
|> |
|> | at
|> |com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
|> .java:1523)
|> |
|> | at
|> |org.jboss.deployment.ServiceDeployer.invoke(ServiceDeployer.java:949)
|> | at
|> |org.jboss.deployment.ServiceDeployer.undeploy(ServiceDeployer
|> .java:681)
|> | at java.lang.reflect.Method.invoke(Native Method)
|> | at
|> |com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
|> .java:1628)
|> |
|> | at
|> |com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
|> .java:1523)
|> |
|> | at org.jboss.deployment.AutoDeployer.undeploy(AutoDeployer.java:664)
|> | at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:270)
|> | at java.lang.Thread.run(Thread.java:484)
|> |
|> |It looks like the service was located and successfully shut down and
|> |destroyed. Then something went wrong.
|> |
|> |Is this a known problem in undeployment, or something peculiar to the
|> |Jetty service.
|> |
|> |Perhaps Jetty's own MBeans are confusing the issue - I'll run some
|> |tests...
|> |
|> |
|> |I would like to get it fixed, as it will speed my development cycle
|> |substantially if I can bounce just the Jetty service, and
|> not the whole
|> |server, each time I recompile my stuff.
|> |
|> |
|> |Thanks, Guys,
|> |
|> |
|> |
|> |Jules
|> |
|> |
|> |
|> |
|> |_________________________________________________________
|> |Do You Yahoo!?
|> |Get your free @yahoo.com address at http://mail.yahoo.com
|> |
|> |
|> |_______________________________________________
|> |Jboss-development mailing list
|> |[EMAIL PROTECTED]
|> |https://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> https://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
