The feature was included in 2.4.5, the patch status has simply not been
updated.
Sourceforge is the only way to submit patches.
public interface EmbeddedCatalinaServiceSXMBean extends
AbstractWebContainerMBean
{
...
/** Get the value to use for the catalina.base System
property. If not specified the catalina.home value will be used
*/
public String getCatalinaBase();
/** Set the value to use for the catalina.base
*/
public void setCatalinaBase(String catalinaBase);
}
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 10, 2002 2:50 PM
Subject: [JBoss-dev] Submitting patches
> Hi
>
> I submitted a patch to sourceforge a couple of weeks ago against the
> 2.4 head which I hoped was going to make it into 2.4.5 final. It didn't
> and that's ok, I have it locally on my copy of jboss. Is just submitting
> patches to sourceforge the right thing to do, or is there a process for
> people to find a developer with CVS access who will take on the
> responsibility of checking the code and committing it?
>
> I have a few more patches which I'm cooking on my own server to
> test now and want to ensure that putting them on sourceforge is the
> best way to get them into the codebase.
>
> Thanks
>
> Roland
>
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
