If that's the way they work, they won't work (from a user perspective), at
least not,
if you don't supply a user interface to do it.

I've been at a BEAcon Europe. Do you really think any of these IT bosses of
banks
and insurance companies would accept a thing like that?

(Say you have 200 sar's, do you say, you are going to maintain them
through ant scripts?)

What one would like to have is a management console like the Veritas Volume
Manager has
or the MS Windows management GUIs. EJX is dead, but no replacement planned
(you see the
posts on the forums, that sound: where's the management GUI, like ORION,
BEA, etc. have?).

My biggest concern is that this developer only perspective is going
to kill JBoss in the corporate IT space. Only eating away LAMP market share.

Lack of scalability from the administrator's perspective.
Isn't that exactly the problem that the JMX-MBean story should solve?

(OK. Just read marc's email on this. He simply says: it's a pain in the ass,
end of story. I like him.)

My $.02.

Georg

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David Jencks
Sent: Thursday, February 28, 2002 01:38
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] buried config in tomcat4-service.sar


On 2002.02.27 14:15:59 -0500 David Ward wrote:
> I like the .sar idea, but if I want to tweak a port in Tomcat (or
> uncomment the Ajp13 section) in JBoss-3.0.0beta_Tomcat-4.0.2, I have to
> extract the deploy/tomcat4-service.sar file, edit its
> META-INF/jboss-service.xml file, re-jar it, and drop it back into
> deploy.  It's easy, but a bit of a pain.  Is this how the .sar's in
> general are going to work if you want to tweak a config, or is there an
> easier way to do it?

Well, yes this is how they work.  If you are assembling the sar yourself
it's not so bad because you just built the thing with an ant script anyway.
 Marc is pushing for the standard contents of jboss to _not_ be packed in
sars for the very reason you are experiencing.  I agree that it is too
painful to have to do this to tweak the configuration of something you
didn't write like Tomcat, however I wish there was a way to keep the
indication of "these jars belong to this plugin, and so do these mbeans" so
you can add or remove the whole service easily.  (If anyone else thinks
this is a worthwhile goal) maybe we could package all the jars for a "unit"
like Tomcat in a sar with an empty jboss-service.xml, and have the
configuration in an external xml file or in the main jboss-service.xml.
Maybe it's just not that important.

david jencks
>
> (I know I'm just a whining user who hasn't contributed any code to date,
> but I AM grateful for everyone in the team's awesome work...)
>
> David
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to