You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Serge Knystautas <se...@lokitech.com> on 2001/09/27 23:26:14 UTC
Nearly ready for release
I got the outstanding patches applied, changelog done, and removed the last
of the Town code.
Outstanding things I have left to do before release...
1. The listserv classes
I want to simplify these by just having a single GenericListserv class
rather than this overly complicated listserv and listserv manager class (and
CommandForListserv and other funny matchers). Also I want to rewrite the
database implementation since I just deleted the town implementation this
afternoon (as it was the only thing stopping me from deleting town.jar).
2. Add Regex matchers
I've changed my mind about how to do these cleanly. :) I may still stick
them in a different package to keep the directory listings smaller, but my
planned convention is "HostIs" is the standard matcher, and "HostRegex" is
the regular expression matcher. Got some matchers Oki sent me, plus some of
my own I'll add.
3. User documentation
We really should write something up at some point. At least a bunch of
simple howto's. ideas to do...
a. how to setup user accounts for pop3
b. how to setup a database for message storage
c. how to setup a database for user accounts
d. how to write a mailet
etc...
4. Log files getting wiped
This seems like a "feature" of the new Avalon, but every time you start
James, all the log files are wiped. If anybody knows more about this,
that'd be great, otherwise I'll start digging in shortly.
I think that's about it... I'll start some testing soon and then update the
website for the 2.0a1 release. I figure we'll the user/dev listserv know
about this, find the problems we forgot to patch, and then maybe for the a2
or b1 release announce to the rest of the world. If anybody else sees a
patch that wasn't applied or spots another bug, please let me know. Thanks!
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Serge Knystautas <se...@lokitech.com>.
Hmmm... I think a separate conf file would create problems since we're
making a lot of small changes to the conf file that might get lost across
multiple copies. I think a howto might work better, and include steps in
that to modify the conf file (since there are other things you have to do as
well).
Looking forward to getting the MySQL stuff sorted out... seems like it's by
far our biggest database market.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Danny Angus" <da...@thought.co.uk>
To: <ja...@jakarta.apache.org>
Sent: Friday, September 28, 2001 7:47 AM
Subject: RE: Nearly ready for release
> I've got some changes for build.xml and james-config.xml which make Mysql
> connections work with less re-writing of the conf file.
>
> Which I'll commit as soon as I'm 100% sure they really are OK ;)
>
> However, I also wondered if config examples for instance; mysql-config.xml
&
> file-config.xml, would help to reduce the number of requests for help with
> JDBC configuation when the release is made, I'd be happy to add
> mysql-config.xml written so that the only changes needed, above DNS server
> and root, would be db name, IP address, u/name & p/word.
>
> d.
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
RE: Nearly ready for release
Posted by Danny Angus <da...@thought.co.uk>.
I've got some changes for build.xml and james-config.xml which make Mysql
connections work with less re-writing of the conf file.
Which I'll commit as soon as I'm 100% sure they really are OK ;)
However, I also wondered if config examples for instance; mysql-config.xml &
file-config.xml, would help to reduce the number of requests for help with
JDBC configuation when the release is made, I'd be happy to add
mysql-config.xml written so that the only changes needed, above DNS server
and root, would be db name, IP address, u/name & p/word.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Serge Knystautas <se...@lokitech.com>.
I agree on alpha vs beta version compatibility. This will definitely be an
alpha, even though I think the code is pretty stable at this point.
And you're right... the things I list are all non-critical, but I have some
time and am planning to do the release work this weekend, so if I can get it
squeezed in, so much the better. :)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Darrell DeBoer" <li...@bigdaz.com>
To: <ja...@jakarta.apache.org>
Sent: Thursday, September 27, 2001 11:05 PM
Subject: Re: Nearly ready for release
> G'day
>
> Great work, Serge (and everyone who helped out). Sorry I haven't been of
> much help - just about through my current work bottleneck, and I should
find
> some more time...
>
> I would suggest releasing alpha1 as is, and leaving these mods for alpha2.
> IMHO, we could benefit from having several alphas prior to bringing out a
> beta release. This would give us a chance to work on some useability
issues
> and doco, while (hopefully) adding a few more users who in turn will
report
> more bugs.
>
> A question: What's the story with version compatibility between alpha
> releases (and the subsequent betas)? Will it be OK to change the config
file
> format (eg to simplify switching POP/SMTP/IMAP on/off) between alpha
> releases, even if this means more work to upgrade from one alpha to the
> next? My assumption was that alpha releases could break compatibility,
> whereas making upgrade automatic was more important between beta releases.
>
> ciao
> Daz
>
> ----- Original Message -----
> From: "Serge Knystautas" <se...@lokitech.com>
> To: <ja...@jakarta.apache.org>
> Sent: Friday, September 28, 2001 7:26 AM
> Subject: Nearly ready for release
>
>
> > I got the outstanding patches applied, changelog done, and removed the
> last
> > of the Town code.
> >
> > Outstanding things I have left to do before release...
> > 1. The listserv classes
> > I want to simplify these by just having a single GenericListserv class
> > rather than this overly complicated listserv and listserv manager class
> (and
> > CommandForListserv and other funny matchers). Also I want to rewrite
the
> > database implementation since I just deleted the town implementation
this
> > afternoon (as it was the only thing stopping me from deleting town.jar).
> >
> > 2. Add Regex matchers
> > I've changed my mind about how to do these cleanly. :) I may still
stick
> > them in a different package to keep the directory listings smaller, but
my
> > planned convention is "HostIs" is the standard matcher, and "HostRegex"
is
> > the regular expression matcher. Got some matchers Oki sent me, plus
some
> of
> > my own I'll add.
> >
> > 3. User documentation
> > We really should write something up at some point. At least a bunch of
> > simple howto's. ideas to do...
> > a. how to setup user accounts for pop3
> > b. how to setup a database for message storage
> > c. how to setup a database for user accounts
> > d. how to write a mailet
> > etc...
> >
> > 4. Log files getting wiped
> > This seems like a "feature" of the new Avalon, but every time you start
> > James, all the log files are wiped. If anybody knows more about this,
> > that'd be great, otherwise I'll start digging in shortly.
> >
> > I think that's about it... I'll start some testing soon and then update
> the
> > website for the 2.0a1 release. I figure we'll the user/dev listserv
know
> > about this, find the problems we forgot to patch, and then maybe for the
> a2
> > or b1 release announce to the rest of the world. If anybody else sees a
> > patch that wasn't applied or spots another bug, please let me know.
> Thanks!
> >
> > Serge Knystautas
> > Loki Technologies
> > http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Darrell DeBoer <li...@bigdaz.com>.
G'day
Great work, Serge (and everyone who helped out). Sorry I haven't been of
much help - just about through my current work bottleneck, and I should find
some more time...
I would suggest releasing alpha1 as is, and leaving these mods for alpha2.
IMHO, we could benefit from having several alphas prior to bringing out a
beta release. This would give us a chance to work on some useability issues
and doco, while (hopefully) adding a few more users who in turn will report
more bugs.
A question: What's the story with version compatibility between alpha
releases (and the subsequent betas)? Will it be OK to change the config file
format (eg to simplify switching POP/SMTP/IMAP on/off) between alpha
releases, even if this means more work to upgrade from one alpha to the
next? My assumption was that alpha releases could break compatibility,
whereas making upgrade automatic was more important between beta releases.
ciao
Daz
----- Original Message -----
From: "Serge Knystautas" <se...@lokitech.com>
To: <ja...@jakarta.apache.org>
Sent: Friday, September 28, 2001 7:26 AM
Subject: Nearly ready for release
> I got the outstanding patches applied, changelog done, and removed the
last
> of the Town code.
>
> Outstanding things I have left to do before release...
> 1. The listserv classes
> I want to simplify these by just having a single GenericListserv class
> rather than this overly complicated listserv and listserv manager class
(and
> CommandForListserv and other funny matchers). Also I want to rewrite the
> database implementation since I just deleted the town implementation this
> afternoon (as it was the only thing stopping me from deleting town.jar).
>
> 2. Add Regex matchers
> I've changed my mind about how to do these cleanly. :) I may still stick
> them in a different package to keep the directory listings smaller, but my
> planned convention is "HostIs" is the standard matcher, and "HostRegex" is
> the regular expression matcher. Got some matchers Oki sent me, plus some
of
> my own I'll add.
>
> 3. User documentation
> We really should write something up at some point. At least a bunch of
> simple howto's. ideas to do...
> a. how to setup user accounts for pop3
> b. how to setup a database for message storage
> c. how to setup a database for user accounts
> d. how to write a mailet
> etc...
>
> 4. Log files getting wiped
> This seems like a "feature" of the new Avalon, but every time you start
> James, all the log files are wiped. If anybody knows more about this,
> that'd be great, otherwise I'll start digging in shortly.
>
> I think that's about it... I'll start some testing soon and then update
the
> website for the 2.0a1 release. I figure we'll the user/dev listserv know
> about this, find the problems we forgot to patch, and then maybe for the
a2
> or b1 release announce to the rest of the world. If anybody else sees a
> patch that wasn't applied or spots another bug, please let me know.
Thanks!
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
RE: patch - james-config.xml
Posted by Danny Angus <da...@thought.co.uk>.
got CVS working and commited it m'self. :)
> -----Original Message-----
> From: Danny Angus [mailto:danny@thought.co.uk]
> Sent: Friday, September 28, 2001 5:08 PM
> To: james-dev@jakarta.apache.org
> Subject: patch - james-config.xml
>
>
> serge - (look no PGP!)
> the changes you made to JDBCMailRepository.java
> need to be matched with changes to james-config.xml
> heres the diff, I have "Insuffucient Karma" apparently, for the
> time being.
>
> cvs -z9 diff -u james-config.xml
> Index: james-config.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-james/src/conf/james-config.xml,v
> retrieving revision 1.14
> diff -u -r1.14 james-config.xml
> --- james-config.xml 2001/09/27 21:11:40 1.14
> +++ james-config.xml 2001/09/28 16:01:56
> @@ -459,7 +459,7 @@
> <type>MAIL</type>
> </types>
> <config>
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </config>
> </repository>
> <repository
> @@ -471,7 +471,7 @@
> <type>SPOOL</type>
> </types>
> <config>
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </config>
> </repository>
> <!-- These repositories store message delivery and headers in the
> DB, and the body to the filesystem -->
> @@ -484,7 +484,7 @@
> <type>MAIL</type>
> </types>
> <config>
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> <filestore>file://var/dbmail</filestore>
> </config>
> </repository>
> @@ -497,7 +497,7 @@
> <type>SPOOL</type>
> </types>
> <config>
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> <filestore>file://var/dbmail</filestore>
> </config>
> </repository>
> @@ -568,14 +568,14 @@
> <!-- <repository name="LocalUsers"
>
> class="org.apache.james.userrepository.JamesUsersJdbcRepository"
> destinationURL="db://maildb/users">
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </repository>
> -->
> <!-- The list used by the default ListServ mailet -->
> <!-- <repository name="list-james"
>
> class="org.apache.james.userrepository.ListUsersJdbcRepository"
> destinationURL="db://maildb/lists/list-james">
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </repository>
> -->
>
> @@ -585,7 +585,7 @@
> <!-- <repository name="list-test"
>
> class="org.apache.james.userrepository.ListUsersJdbcRepository"
> destinationURL="db://maildb/lists">
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </repository>
> -->
> <!-- An example UserRepository for DefaultUser implementations. -->
> @@ -593,7 +593,7 @@
> <!-- <repository name="default-users"
>
> class="org.apache.james.userrepository.DefaultUsersJdbcRepository"
> destinationURL="db://maildb/DefaultUsers">
> - <sqlFile>dist/conf/sqlResources.xml</sqlFile>
> + <sqlFile>file://conf/sqlResources.xml</sqlFile>
> </repository>
> -->
> </users-store>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
patch - james-config.xml
Posted by Danny Angus <da...@thought.co.uk>.
serge - (look no PGP!)
the changes you made to JDBCMailRepository.java
need to be matched with changes to james-config.xml
heres the diff, I have "Insuffucient Karma" apparently, for the time being.
cvs -z9 diff -u james-config.xml
Index: james-config.xml
===================================================================
RCS file: /home/cvspublic/jakarta-james/src/conf/james-config.xml,v
retrieving revision 1.14
diff -u -r1.14 james-config.xml
--- james-config.xml 2001/09/27 21:11:40 1.14
+++ james-config.xml 2001/09/28 16:01:56
@@ -459,7 +459,7 @@
<type>MAIL</type>
</types>
<config>
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<repository
@@ -471,7 +471,7 @@
<type>SPOOL</type>
</types>
<config>
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<!-- These repositories store message delivery and headers in the
DB, and the body to the filesystem -->
@@ -484,7 +484,7 @@
<type>MAIL</type>
</types>
<config>
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</config>
</repository>
@@ -497,7 +497,7 @@
<type>SPOOL</type>
</types>
<config>
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</config>
</repository>
@@ -568,14 +568,14 @@
<!-- <repository name="LocalUsers"
class="org.apache.james.userrepository.JamesUsersJdbcRepository"
destinationURL="db://maildb/users">
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
-->
<!-- The list used by the default ListServ mailet -->
<!-- <repository name="list-james"
class="org.apache.james.userrepository.ListUsersJdbcRepository"
destinationURL="db://maildb/lists/list-james">
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
-->
@@ -585,7 +585,7 @@
<!-- <repository name="list-test"
class="org.apache.james.userrepository.ListUsersJdbcRepository"
destinationURL="db://maildb/lists">
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
-->
<!-- An example UserRepository for DefaultUser implementations. -->
@@ -593,7 +593,7 @@
<!-- <repository name="default-users"
class="org.apache.james.userrepository.DefaultUsersJdbcRepository"
destinationURL="db://maildb/DefaultUsers">
- <sqlFile>dist/conf/sqlResources.xml</sqlFile>
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
-->
</users-store>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Serge Knystautas <se...@lokitech.com>.
I assume this is true, but do I have to do create new category and factory
instances for each channel I have, right?
There are about a dozen channels in James, and since this approach is much
more verbose, it's going to make that conf file much larger (which is ok...
just wanted to make sure that's what's necessary before I write all that.)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Eung-ju Park" <co...@isoft.co.kr>
To: <ja...@jakarta.apache.org>
Sent: Thursday, September 27, 2001 9:26 PM
Subject: Re: Nearly ready for release
> Here is my logs configuration. Finding Giacomo's original description in
> bunch of mail is difficult. ;-)
>
> <logs version="1.1">
> <factories>
> <factory type="block"
>
class="org.apache.avalon.excalibur.logger.factory.FileTargetFactory"/>
> </factories>
>
> <categories>
> <category name="objectstorage" log-level="DEBUG">
> <log-target id-ref="objectstorage"/>
> </category>
> <category name="" log-level="DEBUG">
> <log-target id-ref="default"/>
> </category>
> </categories>
>
> <targets>
> <block id="objectstorage">
> <filename>${app.home}/logs/objectstorage.log</filename>
> <format type="pattern"><![CDATA[ %{time} [%7.7{priority}]
> <<%{category}>> (%{context}): %{message}\n%{throwable}]]></format>
> <append>false</append>
> </block>
> <block id="default">
> <filename>${app.home}/logs/overlord.log</filename>
> <append>false</append>
> <format type="pattern"><![CDATA[ %{time} [%7.7{priority}]
> <<%{category}>> (%{context}): %{message}\n%{throwable}]]></format>
> </block>
> </targets>
> </logs>
>
> ----- Original Message -----
> From: "Serge Knystautas" <se...@lokitech.com>
> To: <ja...@jakarta.apache.org>
> Sent: Friday, September 28, 2001 10:07 AM
> Subject: Re: Nearly ready for release
>
>
> > Great Pete! Thanks for the info...I'll give that 1.1 trick a try.
> >
> > Serge Knystautas
> > Loki Technologies
> > http://www.lokitech.com/
> > ----- Original Message -----
> > From: "Peter Donald" <do...@apache.org>
> > To: <ja...@jakarta.apache.org>
> > Sent: Thursday, September 27, 2001 8:39 PM
> > Subject: Re: Nearly ready for release
> >
> >
> > > On Fri, 28 Sep 2001 07:26, Serge Knystautas wrote:
> > > > 4. Log files getting wiped
> > > > This seems like a "feature" of the new Avalon, but every time you
> start
> > > > James, all the log files are wiped. If anybody knows more about
this,
> > > > that'd be great, otherwise I'll start digging in shortly.
> > >
> > > This is a "feature" with the logging system James uses atm. You can
> > upgrade
> > > to a newer system by placing the version="1.1" attribute in logs
element
> > like
> > >
> > > <logs version="1.1">
> > > ....
> > > </logs>
> > >
> > > Unfortunately I haven't used the new format so can't describe it.
> However
> > it
> > > was originally proposed by Giacomo on 21st of August and he includes a
> > sample
> > > config file. The rest of the documentation is in the excalibur project
> in
> > the
> > > javadocs of org.apache.avalon.excalibur.logger.*
> > >
> > > With that you should be able to log to
> files/database/jms/syslog/whatever
> > > relatively easy.
> > >
> > > --
> > > Cheers,
> > >
> > > Pete
> > >
> > > *-------------------------------------*
> > > | Does the name `Pavlov' ring a bell? |
> > > *-------------------------------------*
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Eung-ju Park <co...@isoft.co.kr>.
Here is my logs configuration. Finding Giacomo's original description in
bunch of mail is difficult. ;-)
<logs version="1.1">
<factories>
<factory type="block"
class="org.apache.avalon.excalibur.logger.factory.FileTargetFactory"/>
</factories>
<categories>
<category name="objectstorage" log-level="DEBUG">
<log-target id-ref="objectstorage"/>
</category>
<category name="" log-level="DEBUG">
<log-target id-ref="default"/>
</category>
</categories>
<targets>
<block id="objectstorage">
<filename>${app.home}/logs/objectstorage.log</filename>
<format type="pattern"><![CDATA[ %{time} [%7.7{priority}]
<<%{category}>> (%{context}): %{message}\n%{throwable}]]></format>
<append>false</append>
</block>
<block id="default">
<filename>${app.home}/logs/overlord.log</filename>
<append>false</append>
<format type="pattern"><![CDATA[ %{time} [%7.7{priority}]
<<%{category}>> (%{context}): %{message}\n%{throwable}]]></format>
</block>
</targets>
</logs>
----- Original Message -----
From: "Serge Knystautas" <se...@lokitech.com>
To: <ja...@jakarta.apache.org>
Sent: Friday, September 28, 2001 10:07 AM
Subject: Re: Nearly ready for release
> Great Pete! Thanks for the info...I'll give that 1.1 trick a try.
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
> ----- Original Message -----
> From: "Peter Donald" <do...@apache.org>
> To: <ja...@jakarta.apache.org>
> Sent: Thursday, September 27, 2001 8:39 PM
> Subject: Re: Nearly ready for release
>
>
> > On Fri, 28 Sep 2001 07:26, Serge Knystautas wrote:
> > > 4. Log files getting wiped
> > > This seems like a "feature" of the new Avalon, but every time you
start
> > > James, all the log files are wiped. If anybody knows more about this,
> > > that'd be great, otherwise I'll start digging in shortly.
> >
> > This is a "feature" with the logging system James uses atm. You can
> upgrade
> > to a newer system by placing the version="1.1" attribute in logs element
> like
> >
> > <logs version="1.1">
> > ....
> > </logs>
> >
> > Unfortunately I haven't used the new format so can't describe it.
However
> it
> > was originally proposed by Giacomo on 21st of August and he includes a
> sample
> > config file. The rest of the documentation is in the excalibur project
in
> the
> > javadocs of org.apache.avalon.excalibur.logger.*
> >
> > With that you should be able to log to
files/database/jms/syslog/whatever
> > relatively easy.
> >
> > --
> > Cheers,
> >
> > Pete
> >
> > *-------------------------------------*
> > | Does the name `Pavlov' ring a bell? |
> > *-------------------------------------*
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Serge Knystautas <se...@lokitech.com>.
Great Pete! Thanks for the info...I'll give that 1.1 trick a try.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Peter Donald" <do...@apache.org>
To: <ja...@jakarta.apache.org>
Sent: Thursday, September 27, 2001 8:39 PM
Subject: Re: Nearly ready for release
> On Fri, 28 Sep 2001 07:26, Serge Knystautas wrote:
> > 4. Log files getting wiped
> > This seems like a "feature" of the new Avalon, but every time you start
> > James, all the log files are wiped. If anybody knows more about this,
> > that'd be great, otherwise I'll start digging in shortly.
>
> This is a "feature" with the logging system James uses atm. You can
upgrade
> to a newer system by placing the version="1.1" attribute in logs element
like
>
> <logs version="1.1">
> ....
> </logs>
>
> Unfortunately I haven't used the new format so can't describe it. However
it
> was originally proposed by Giacomo on 21st of August and he includes a
sample
> config file. The rest of the documentation is in the excalibur project in
the
> javadocs of org.apache.avalon.excalibur.logger.*
>
> With that you should be able to log to files/database/jms/syslog/whatever
> relatively easy.
>
> --
> Cheers,
>
> Pete
>
> *-------------------------------------*
> | Does the name `Pavlov' ring a bell? |
> *-------------------------------------*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: Nearly ready for release
Posted by Peter Donald <do...@apache.org>.
On Fri, 28 Sep 2001 07:26, Serge Knystautas wrote:
> 4. Log files getting wiped
> This seems like a "feature" of the new Avalon, but every time you start
> James, all the log files are wiped. If anybody knows more about this,
> that'd be great, otherwise I'll start digging in shortly.
This is a "feature" with the logging system James uses atm. You can upgrade
to a newer system by placing the version="1.1" attribute in logs element like
<logs version="1.1">
...
</logs>
Unfortunately I haven't used the new format so can't describe it. However it
was originally proposed by Giacomo on 21st of August and he includes a sample
config file. The rest of the documentation is in the excalibur project in the
javadocs of org.apache.avalon.excalibur.logger.*
With that you should be able to log to files/database/jms/syslog/whatever
relatively easy.
--
Cheers,
Pete
*-------------------------------------*
| Does the name `Pavlov' ring a bell? |
*-------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org