Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-17 Thread Benson Margulies
Everyone seems to like this. I see no reason for a formal vote.

If people would be so kind to update or create confluence content,
when we have a critical mass I can organize the switcheroo.

On Sat, Oct 16, 2010 at 7:45 AM, Colm O hEigeartaigh
cohei...@apache.org wrote:
 Another +1 from me. What about the webpages of the constituent
 projects? For example, WSS4J has its own Forrest generated webpage.
 Maybe this should be merged with the new WS confluence page as well?

 Colm.

 On Fri, Oct 15, 2010 at 8:25 PM, Andreas Veithen
 andreas.veit...@gmail.com wrote:
 +1 for Confluence.

 I know more or less how the Confluence auto-export stuff works, but
 there are two technical questions that are not clear to me:

 1. Where and how are the export templates maintained?
 2. How is the exported content (https://cwiki.apache.org/WS) going to
 be published to http://ws.apache.org and how will we manage the fact
 that some subprojects continue to use generated (Maven) sites?

 Andreas

 On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:

 I'm definitely +1.   Forrest sucks.   :-)

 On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
 We've got 1.5 web sites here.

 There's

 http://ws.apache.org

 which is very stale, and 'maintained' using Apache Forrest, which
 isn't, well, maintained, and has no release that works with Java 1.6.

 Then we've got:

 https://cwiki.apache.org/confluence/display/WS/Index

 which is more up to date, but needs to be exported (in place of the
 above) to be useful.

 Well, it's already being exported:

 https://cwiki.apache.org/WS

 but the template definitely needs a lot of work. As does the content.    But
 the content needs work in the forest site as well and I think editing the
 Confluence content is much easier.

 Dan



 I'll give this idea a day or two for discussion, and, barring giant
 problems, put it to a vote.

 --
 Daniel Kulp
 dk...@apache.org
 http://dankulp.com/blog





Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-16 Thread Andreas Veithen
Nadir,

There is also a user who would like to submit updates for the
Axis1/Java site (which as you pointed out is intertwined with
Axis/C++) and who is struggling with the Forrest stuff [1]. Maybe you
can join that discussion to see what can be done for the old Axis1
site.

Andreas

[1] http://markmail.org/thread/w335pq7dgoyeq3bz

On Sat, Oct 16, 2010 at 02:12, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
 Hi Nadir,

 There are some discussions on java-dev list about axis site redesign
 [1]  that also based on Confluence. Chanaka Jayasena already making
 some progress on this and you may join with him or you can take your
 own path. The best place to have your discussion is either axis
 java-dev list or this Jira ticket [2].


 [1] - http://osdir.com/ml/java-dev/2010-10/msg00034.html
 [2] - https://issues.apache.org/jira/browse/AXIS2-4773

 Thanks !

 On Fri, Oct 15, 2010 at 7:03 PM, Benson Margulies bimargul...@gmail.com 
 wrote:
 Nadir,

 Axis is its own TLP. It left its web content behind at
 people.apache.org:/www/ws.apache.org/

  axis
  axis2
  axis-c


 They should be making themselves a new web site under axis.apache.org,
 instead of what there is so far, a single HTML page under
 axis.apache.org pointing back into ws.apache.org.



 You are listed as a PMC member of the new Axis TLP, perhaps you could
 lead the charge there?

 --benson


 On Fri, Oct 15, 2010 at 6:56 PM, Nadir Amra a...@us.ibm.com wrote:
 Benson,

 Yes, Axis C++ and Axis are intertwined.

 So where is the content and are there any pointers to how to perform the
 updates? I can read about Confluence some more, but where exactly is the
 content for Axis?

 Nadir Amra
 Integrated Web Services for IBM i Operating System
 Internet: a...@us.ibm.com

 Benson Margulies bimargul...@gmail.com wrote on 10/15/2010 05:38:06 PM:

 From: Benson Margulies bimargul...@gmail.com
 To: general@ws.apache.org
 Date: 10/15/2010 05:38 PM
 Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
 of exporting the confluence site

 I'm confused. Didn't Axis C++ travel with the rest of Axis? Obviously
 I wasn't paying enough attention.

 Anyway, people can start improving the Confluence content starting
 Right Now, and when we like it I can perform the switcharoo.

 On Fri, Oct 15, 2010 at 6:21 PM, Nadir Amra a...@us.ibm.com wrote:
  +1 for Confluence.
 
  I want to be also involved in updating the Axis C++ content just to
  make
  you all aware.  There is a lot of stuff that needs to be cleaned up.
 
  Nadir Amra
  Integrated Web Services for IBM i Operating System
  IBM Rochester, MN,  (Tel. 507-253-0645, t/l 553-0645)
  Internet: a...@us.ibm.com
 
  Andreas Veithen andreas.veit...@gmail.com wrote on 10/15/2010 02:25:37
  PM:
 
  From: Andreas Veithen andreas.veit...@gmail.com
  To: general@ws.apache.org
  Cc: Benson Margulies bimargul...@gmail.com
  Date: 10/15/2010 02:26 PM
  Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
  of exporting the confluence site
 
  +1 for Confluence.
 
  I know more or less how the Confluence auto-export stuff works, but
  there are two technical questions that are not clear to me:
 
  1. Where and how are the export templates maintained?
  2. How is the exported content (https://cwiki.apache.org/WS) going to
  be published to http://ws.apache.org and how will we manage the fact
  that some subprojects continue to use generated (Maven) sites?
 
  Andreas
 
  On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:
  
   I'm definitely +1.   Forrest sucks.   :-)
  
   On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
   We've got 1.5 web sites here.
  
   There's
  
   http://ws.apache.org
  
   which is very stale, and 'maintained' using Apache Forrest, which
   isn't, well, maintained, and has no release that works with Java
   1.6.
  
   Then we've got:
  
   https://cwiki.apache.org/confluence/display/WS/Index
  
   which is more up to date, but needs to be exported (in place of the
   above) to be useful.
  
   Well, it's already being exported:
  
   https://cwiki.apache.org/WS
  
   but the template definitely needs a lot of work. As does the content.
    But
   the content needs work in the forest site as well and I think editing
   the
   Confluence content is much easier.
  
   Dan
  
  
  
   I'll give this idea a day or two for discussion, and, barring giant
   problems, put it to a vote.
  
   --
   Daniel Kulp
   dk...@apache.org
   http://dankulp.com/blog
  
 





 --
 Sagara Gunathunga

 Blog - http://ssagara.blogspot.com
 Web - http://people.apache.org/~sagara/



Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-16 Thread Colm O hEigeartaigh
Another +1 from me. What about the webpages of the constituent
projects? For example, WSS4J has its own Forrest generated webpage.
Maybe this should be merged with the new WS confluence page as well?

Colm.

On Fri, Oct 15, 2010 at 8:25 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
 +1 for Confluence.

 I know more or less how the Confluence auto-export stuff works, but
 there are two technical questions that are not clear to me:

 1. Where and how are the export templates maintained?
 2. How is the exported content (https://cwiki.apache.org/WS) going to
 be published to http://ws.apache.org and how will we manage the fact
 that some subprojects continue to use generated (Maven) sites?

 Andreas

 On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:

 I'm definitely +1.   Forrest sucks.   :-)

 On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
 We've got 1.5 web sites here.

 There's

 http://ws.apache.org

 which is very stale, and 'maintained' using Apache Forrest, which
 isn't, well, maintained, and has no release that works with Java 1.6.

 Then we've got:

 https://cwiki.apache.org/confluence/display/WS/Index

 which is more up to date, but needs to be exported (in place of the
 above) to be useful.

 Well, it's already being exported:

 https://cwiki.apache.org/WS

 but the template definitely needs a lot of work. As does the content.    But
 the content needs work in the forest site as well and I think editing the
 Confluence content is much easier.

 Dan



 I'll give this idea a day or two for discussion, and, barring giant
 problems, put it to a vote.

 --
 Daniel Kulp
 dk...@apache.org
 http://dankulp.com/blog




Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Sagara Gunathunga
+1 for Confluence .

Ideally pages like this [1] should be updated with noticeable events
of sub projects and I also believe it's  much more easy to maintains
Confluence than Forrest.

[1] - http://ws.apache.org/news.html

Thanks !

On Fri, Oct 15, 2010 at 11:03 AM, Daniel Kulp dk...@apache.org wrote:

 I'm definitely +1.   Forrest sucks.   :-)

 On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
 We've got 1.5 web sites here.

 There's

 http://ws.apache.org

 which is very stale, and 'maintained' using Apache Forrest, which
 isn't, well, maintained, and has no release that works with Java 1.6.

 Then we've got:

 https://cwiki.apache.org/confluence/display/WS/Index

 which is more up to date, but needs to be exported (in place of the
 above) to be useful.

 Well, it's already being exported:

 https://cwiki.apache.org/WS

 but the template definitely needs a lot of work. As does the content.    But
 the content needs work in the forest site as well and I think editing the
 Confluence content is much easier.

 Dan



 I'll give this idea a day or two for discussion, and, barring giant
 problems, put it to a vote.

 --
 Daniel Kulp
 dk...@apache.org
 http://dankulp.com/blog




-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/


Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Andreas Veithen
+1 for Confluence.

I know more or less how the Confluence auto-export stuff works, but
there are two technical questions that are not clear to me:

1. Where and how are the export templates maintained?
2. How is the exported content (https://cwiki.apache.org/WS) going to
be published to http://ws.apache.org and how will we manage the fact
that some subprojects continue to use generated (Maven) sites?

Andreas

On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:

 I'm definitely +1.   Forrest sucks.   :-)

 On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
 We've got 1.5 web sites here.

 There's

 http://ws.apache.org

 which is very stale, and 'maintained' using Apache Forrest, which
 isn't, well, maintained, and has no release that works with Java 1.6.

 Then we've got:

 https://cwiki.apache.org/confluence/display/WS/Index

 which is more up to date, but needs to be exported (in place of the
 above) to be useful.

 Well, it's already being exported:

 https://cwiki.apache.org/WS

 but the template definitely needs a lot of work. As does the content.    But
 the content needs work in the forest site as well and I think editing the
 Confluence content is much easier.

 Dan



 I'll give this idea a day or two for discussion, and, barring giant
 problems, put it to a vote.

 --
 Daniel Kulp
 dk...@apache.org
 http://dankulp.com/blog



Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Daniel Kulp
On Friday 15 October 2010 3:25:37 pm Andreas Veithen wrote:
 +1 for Confluence.
 
 I know more or less how the Confluence auto-export stuff works, but
 there are two technical questions that are not clear to me:
 
 1. Where and how are the export templates maintained?

This is the big negative.   You need admin access to confluence to edit those.  
However, admin access is generally given out like candy if needed for this 
purpose.   There is an AutoExport tab on the Admin page where the capability 
to edit the template and re-export the entire space it found.


 2. How is the exported content (https://cwiki.apache.org/WS) going to
 be published to http://ws.apache.org and how will we manage the fact
 that some subprojects continue to use generated (Maven) sites?

Every hour, the confluence stuff is rsynced over to people.apache.org: 
/www/confluence-exports.   Thus, what is needed is for someone to create a 
crontab that each hour, rsyncs stuff from there over to the /www/ws.apache.org 
directory.   

The maven projects just dump stuff there as well.  Thus, as long as the rsync 
doesn't delete anything it shouldn't, all is well.

Dan



 
 Andreas
 
 On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:
  I'm definitely +1.   Forrest sucks.   :-)
  
  On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
  We've got 1.5 web sites here.
  
  There's
  
  http://ws.apache.org
  
  which is very stale, and 'maintained' using Apache Forrest, which
  isn't, well, maintained, and has no release that works with Java 1.6.
  
  Then we've got:
  
  https://cwiki.apache.org/confluence/display/WS/Index
  
  which is more up to date, but needs to be exported (in place of the
  above) to be useful.
  
  Well, it's already being exported:
  
  https://cwiki.apache.org/WS
  
  but the template definitely needs a lot of work. As does the content.  
   But the content needs work in the forest site as well and I think
  editing the Confluence content is much easier.
  
  Dan
  
  I'll give this idea a day or two for discussion, and, barring giant
  problems, put it to a vote.
  
  --
  Daniel Kulp
  dk...@apache.org
  http://dankulp.com/blog

-- 
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog


Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Benson Margulies
I'm confused. Didn't Axis C++ travel with the rest of Axis? Obviously
I wasn't paying enough attention.

Anyway, people can start improving the Confluence content starting
Right Now, and when we like it I can perform the switcharoo.

On Fri, Oct 15, 2010 at 6:21 PM, Nadir Amra a...@us.ibm.com wrote:
 +1 for Confluence.

 I want to be also involved in updating the Axis C++ content just to make
 you all aware.  There is a lot of stuff that needs to be cleaned up.

 Nadir Amra
 Integrated Web Services for IBM i Operating System
 IBM Rochester, MN,  (Tel. 507-253-0645, t/l 553-0645)
 Internet: a...@us.ibm.com

 Andreas Veithen andreas.veit...@gmail.com wrote on 10/15/2010 02:25:37 PM:

 From: Andreas Veithen andreas.veit...@gmail.com
 To: general@ws.apache.org
 Cc: Benson Margulies bimargul...@gmail.com
 Date: 10/15/2010 02:26 PM
 Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
 of exporting the confluence site

 +1 for Confluence.

 I know more or less how the Confluence auto-export stuff works, but
 there are two technical questions that are not clear to me:

 1. Where and how are the export templates maintained?
 2. How is the exported content (https://cwiki.apache.org/WS) going to
 be published to http://ws.apache.org and how will we manage the fact
 that some subprojects continue to use generated (Maven) sites?

 Andreas

 On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:
 
  I'm definitely +1.   Forrest sucks.   :-)
 
  On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
  We've got 1.5 web sites here.
 
  There's
 
  http://ws.apache.org
 
  which is very stale, and 'maintained' using Apache Forrest, which
  isn't, well, maintained, and has no release that works with Java 1.6.
 
  Then we've got:
 
  https://cwiki.apache.org/confluence/display/WS/Index
 
  which is more up to date, but needs to be exported (in place of the
  above) to be useful.
 
  Well, it's already being exported:
 
  https://cwiki.apache.org/WS
 
  but the template definitely needs a lot of work. As does the content.
   But
  the content needs work in the forest site as well and I think editing
  the
  Confluence content is much easier.
 
  Dan
 
 
 
  I'll give this idea a day or two for discussion, and, barring giant
  problems, put it to a vote.
 
  --
  Daniel Kulp
  dk...@apache.org
  http://dankulp.com/blog
 



Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Benson Margulies
Nadir,

Axis is its own TLP. It left its web content behind at
people.apache.org:/www/ws.apache.org/

  axis
  axis2
  axis-c


They should be making themselves a new web site under axis.apache.org,
instead of what there is so far, a single HTML page under
axis.apache.org pointing back into ws.apache.org.



You are listed as a PMC member of the new Axis TLP, perhaps you could
lead the charge there?

--benson


On Fri, Oct 15, 2010 at 6:56 PM, Nadir Amra a...@us.ibm.com wrote:
 Benson,

 Yes, Axis C++ and Axis are intertwined.

 So where is the content and are there any pointers to how to perform the
 updates? I can read about Confluence some more, but where exactly is the
 content for Axis?

 Nadir Amra
 Integrated Web Services for IBM i Operating System
 Internet: a...@us.ibm.com

 Benson Margulies bimargul...@gmail.com wrote on 10/15/2010 05:38:06 PM:

 From: Benson Margulies bimargul...@gmail.com
 To: general@ws.apache.org
 Date: 10/15/2010 05:38 PM
 Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
 of exporting the confluence site

 I'm confused. Didn't Axis C++ travel with the rest of Axis? Obviously
 I wasn't paying enough attention.

 Anyway, people can start improving the Confluence content starting
 Right Now, and when we like it I can perform the switcharoo.

 On Fri, Oct 15, 2010 at 6:21 PM, Nadir Amra a...@us.ibm.com wrote:
  +1 for Confluence.
 
  I want to be also involved in updating the Axis C++ content just to
  make
  you all aware.  There is a lot of stuff that needs to be cleaned up.
 
  Nadir Amra
  Integrated Web Services for IBM i Operating System
  IBM Rochester, MN,  (Tel. 507-253-0645, t/l 553-0645)
  Internet: a...@us.ibm.com
 
  Andreas Veithen andreas.veit...@gmail.com wrote on 10/15/2010 02:25:37
  PM:
 
  From: Andreas Veithen andreas.veit...@gmail.com
  To: general@ws.apache.org
  Cc: Benson Margulies bimargul...@gmail.com
  Date: 10/15/2010 02:26 PM
  Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
  of exporting the confluence site
 
  +1 for Confluence.
 
  I know more or less how the Confluence auto-export stuff works, but
  there are two technical questions that are not clear to me:
 
  1. Where and how are the export templates maintained?
  2. How is the exported content (https://cwiki.apache.org/WS) going to
  be published to http://ws.apache.org and how will we manage the fact
  that some subprojects continue to use generated (Maven) sites?
 
  Andreas
 
  On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:
  
   I'm definitely +1.   Forrest sucks.   :-)
  
   On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
   We've got 1.5 web sites here.
  
   There's
  
   http://ws.apache.org
  
   which is very stale, and 'maintained' using Apache Forrest, which
   isn't, well, maintained, and has no release that works with Java
   1.6.
  
   Then we've got:
  
   https://cwiki.apache.org/confluence/display/WS/Index
  
   which is more up to date, but needs to be exported (in place of the
   above) to be useful.
  
   Well, it's already being exported:
  
   https://cwiki.apache.org/WS
  
   but the template definitely needs a lot of work. As does the content.
    But
   the content needs work in the forest site as well and I think editing
   the
   Confluence content is much easier.
  
   Dan
  
  
  
   I'll give this idea a day or two for discussion, and, barring giant
   problems, put it to a vote.
  
   --
   Daniel Kulp
   dk...@apache.org
   http://dankulp.com/blog
  
 



Re: [PROPOSAL]: throw away the 'forrest' web site in favor of exporting the confluence site

2010-10-15 Thread Sagara Gunathunga
Hi Nadir,

There are some discussions on java-dev list about axis site redesign
[1]  that also based on Confluence. Chanaka Jayasena already making
some progress on this and you may join with him or you can take your
own path. The best place to have your discussion is either axis
java-dev list or this Jira ticket [2].


[1] - http://osdir.com/ml/java-dev/2010-10/msg00034.html
[2] - https://issues.apache.org/jira/browse/AXIS2-4773

Thanks !

On Fri, Oct 15, 2010 at 7:03 PM, Benson Margulies bimargul...@gmail.com wrote:
 Nadir,

 Axis is its own TLP. It left its web content behind at
 people.apache.org:/www/ws.apache.org/

  axis
  axis2
  axis-c


 They should be making themselves a new web site under axis.apache.org,
 instead of what there is so far, a single HTML page under
 axis.apache.org pointing back into ws.apache.org.



 You are listed as a PMC member of the new Axis TLP, perhaps you could
 lead the charge there?

 --benson


 On Fri, Oct 15, 2010 at 6:56 PM, Nadir Amra a...@us.ibm.com wrote:
 Benson,

 Yes, Axis C++ and Axis are intertwined.

 So where is the content and are there any pointers to how to perform the
 updates? I can read about Confluence some more, but where exactly is the
 content for Axis?

 Nadir Amra
 Integrated Web Services for IBM i Operating System
 Internet: a...@us.ibm.com

 Benson Margulies bimargul...@gmail.com wrote on 10/15/2010 05:38:06 PM:

 From: Benson Margulies bimargul...@gmail.com
 To: general@ws.apache.org
 Date: 10/15/2010 05:38 PM
 Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
 of exporting the confluence site

 I'm confused. Didn't Axis C++ travel with the rest of Axis? Obviously
 I wasn't paying enough attention.

 Anyway, people can start improving the Confluence content starting
 Right Now, and when we like it I can perform the switcharoo.

 On Fri, Oct 15, 2010 at 6:21 PM, Nadir Amra a...@us.ibm.com wrote:
  +1 for Confluence.
 
  I want to be also involved in updating the Axis C++ content just to
  make
  you all aware.  There is a lot of stuff that needs to be cleaned up.
 
  Nadir Amra
  Integrated Web Services for IBM i Operating System
  IBM Rochester, MN,  (Tel. 507-253-0645, t/l 553-0645)
  Internet: a...@us.ibm.com
 
  Andreas Veithen andreas.veit...@gmail.com wrote on 10/15/2010 02:25:37
  PM:
 
  From: Andreas Veithen andreas.veit...@gmail.com
  To: general@ws.apache.org
  Cc: Benson Margulies bimargul...@gmail.com
  Date: 10/15/2010 02:26 PM
  Subject: Re: [PROPOSAL]: throw away the 'forrest' web site in favor
  of exporting the confluence site
 
  +1 for Confluence.
 
  I know more or less how the Confluence auto-export stuff works, but
  there are two technical questions that are not clear to me:
 
  1. Where and how are the export templates maintained?
  2. How is the exported content (https://cwiki.apache.org/WS) going to
  be published to http://ws.apache.org and how will we manage the fact
  that some subprojects continue to use generated (Maven) sites?
 
  Andreas
 
  On Fri, Oct 15, 2010 at 17:03, Daniel Kulp dk...@apache.org wrote:
  
   I'm definitely +1.   Forrest sucks.   :-)
  
   On Friday 15 October 2010 11:00:32 am Benson Margulies wrote:
   We've got 1.5 web sites here.
  
   There's
  
   http://ws.apache.org
  
   which is very stale, and 'maintained' using Apache Forrest, which
   isn't, well, maintained, and has no release that works with Java
   1.6.
  
   Then we've got:
  
   https://cwiki.apache.org/confluence/display/WS/Index
  
   which is more up to date, but needs to be exported (in place of the
   above) to be useful.
  
   Well, it's already being exported:
  
   https://cwiki.apache.org/WS
  
   but the template definitely needs a lot of work. As does the content.
    But
   the content needs work in the forest site as well and I think editing
   the
   Confluence content is much easier.
  
   Dan
  
  
  
   I'll give this idea a day or two for discussion, and, barring giant
   problems, put it to a vote.
  
   --
   Daniel Kulp
   dk...@apache.org
   http://dankulp.com/blog
  
 





-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/