DO NOT REPLY [Bug 43819] - Support latest JSR245 proposal to make EL self-contained

2007-11-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43819.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43819





--- Additional Comments From [EMAIL PROTECTED]  2007-11-09 01:29 ---
Created an attachment (id=21099)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=21099action=view)
new patch

Sorry... Updated the patch to be pure AL2.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: New Tomcat release? Out of the box bundle with Harmony?

2007-11-09 Thread Henri Gomez
  BTW, Harmony people, may I suggest you be to contact the JPackage team
  (www.jpackage.org).
 Thanks for pointing to this project, Henri.

No problem and happy to help.

I was involved in Jpackage some times ago (member and co-founder)

Cheers

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: New Tomcat release? Out of the box bundle with Harmony?

2007-11-09 Thread Johnny Kewl


---
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool pojo application server
---
- Original Message - 
From: Yoav Shapira [EMAIL PROTECTED]

To: Tomcat Developers List dev@tomcat.apache.org
Sent: Thursday, November 08, 2007 4:15 PM
Subject: Re: New Tomcat release? Out of the box bundle with Harmony?



Hey,

On Nov 8, 2007 9:10 AM, Alexey Petrenko [EMAIL PROTECTED] 
wrote:
I want to suggest you to create Tomcat out of the box bundle on top of 
Harmony.

I've created such a bundle with the previous Harmony milestone release
[2]. It works but has areas for improvements... For example it's
possible to remove debug info from Harmony which is not needed in such
a bundle.

What do you think? Is such bundle interesting for Tomcat?


Personally, I want to move the Tomcat downloads in a simpler
direction, removing options not adding them.  So I'm not in favor of
various bundles and combinations.


I agree, bundle TC as you will, but TC always needs to be independent.
I would like to see TC more modulerized, things like clustering been an 
optional add on.
Again there are bundles, but there is also a tiny downlaod that will run a 
servlet.

All optional technologies should be modulerized... I think.
Then in contrast to this... needed embedded technologies should be brought 
out through a TC specific API.
For example things like base64 parsing, JMX for the servlet, XMLParsing like 
that in the default servlet, should be an option in a users servlet. If its 
intrinsic technology, dont waste it, bring it out as well.

... I think



Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r593493 - /tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c

2007-11-09 Thread mturk
Author: mturk
Date: Fri Nov  9 03:20:13 2007
New Revision: 593493

URL: http://svn.apache.org/viewvc?rev=593493view=rev
Log:
Not sure why we set to NULL or zero something that was already set to zero

Modified:
tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c

Modified: tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c?rev=593493r1=593492r2=593493view=diff
==
--- tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c (original)
+++ tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c Fri Nov  9 03:20:13 
2007
@@ -2335,29 +2335,13 @@
 jk_server_conf_t *c =
 (jk_server_conf_t *) apr_pcalloc(p, sizeof(jk_server_conf_t));
 
-c-mount_file = NULL;
-c-log_file = NULL;
-c-log = NULL;
-c-alias_dir = NULL;
-c-stamp_format_string = NULL;
-c-format_string = NULL;
-c-format = NULL;
-c-exclude_options = 0;
 c-was_initialized = JK_FALSE;
 
 if (s-is_virtual) {
 c-mountcopy = JK_UNSET;
 c-mount_file_reload = JK_UNSET;
 c-log_level = JK_UNSET;
-c-options = 0;
-c-worker_indicator = NULL;
 c-ssl_enable = JK_UNSET;
-c-https_indicator = NULL;
-c-certs_indicator = NULL;
-c-cipher_indicator = NULL;
-c-certchain_prefix = NULL;
-c-session_indicator = NULL;
-c-key_size_indicator = NULL;
 c-strip_session = JK_UNSET;
 } else {
 c-mountcopy = JK_FALSE;
@@ -2382,14 +2366,7 @@
 c-key_size_indicator = JK_ENV_KEY_SIZE;
 c-strip_session = JK_FALSE;
 }
-
-c-uri_to_context = NULL;
-c-uw_map = NULL;
-
 c-envvars_in_use = JK_FALSE;
-c-envvars = NULL;
-c-envvars_def = NULL;
-c-envvar_items = NULL;
 
 c-s = s;
 apr_pool_cleanup_register(p, s, jk_apr_pool_cleanup, jk_apr_pool_cleanup);



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r593497 - /tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c

2007-11-09 Thread mturk
Author: mturk
Date: Fri Nov  9 03:45:14 2007
New Revision: 593497

URL: http://svn.apache.org/viewvc?rev=593497view=rev
Log:
Log missing uri maps

Modified:
tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c

Modified: tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c?rev=593497r1=593496r2=593497view=diff
==
--- tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c (original)
+++ tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c Fri Nov  9 03:45:14 
2007
@@ -19,7 +19,7 @@
  * Description: Apache 2 plugin for Tomcat *
  * Author:  Gal Shachor [EMAIL PROTECTED]   *
  *  Henri Gomez [EMAIL PROTECTED]*
- * Version: $Revision$  *
+ * Version: $Revision$*
  ***/
 
 /*
@@ -2930,9 +2930,9 @@
 if (!conf-uw_map) {
 if (JK_IS_DEBUG_LEVEL(conf-log))
 jk_log(conf-log, JK_LOG_DEBUG,
-   Into translate empty uri map for uri=%s,
+   missing uri map for %s:%s,
+   conf-s-server_hostname ? conf-s-server_hostname 
: _default_,
r-uri);
-
 return DECLINED;
 }
 else
@@ -3041,6 +3041,12 @@
 }
 }
 }
+else {
+if (JK_IS_DEBUG_LEVEL(conf-log))
+jk_log(conf-log, JK_LOG_DEBUG,
+   no match for %s found,
+   r-uri);
+}
 }
 }
 
@@ -3081,9 +3087,9 @@
 if (!conf-uw_map) {
 if (JK_IS_DEBUG_LEVEL(conf-log))
 jk_log(conf-log, JK_LOG_DEBUG,
-   Into map_to_storage empty uri map for uri=%s,
+   missing uri map for %s:%s,
+   conf-s-server_hostname ? conf-s-server_hostname 
: _default_,
r-uri);
-
 return DECLINED;
 }
 else
@@ -3117,6 +3123,12 @@
 *jsessionid = '\0';
 }
 return DECLINED;
+}
+else {
+if (JK_IS_DEBUG_LEVEL(conf-log))
+jk_log(conf-log, JK_LOG_DEBUG,
+   no match for %s found,
+   r-uri);
 }
 }
 }



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Remy Maucherat
On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:
 The candidates binaries are available here:
 http://people.apache.org/~remm/tomcat-6/v6.0.15/
 
 According to the release process, the 6.0.15 tag is:
 [ ] Broken
 [ ] Alpha
 [ ] Beta
 [ ] Stable

I am undecided about how to proceed with the release. The issues,
although visible, do not sound very serious in the real world, so it
would seem to be possible to release as stable.

Rémy



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Yoav Shapira
Hey,

On Nov 9, 2007 11:09 AM, Remy Maucherat [EMAIL PROTECTED] wrote:
 On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:
  The candidates binaries are available here:
  http://people.apache.org/~remm/tomcat-6/v6.0.15/
 
  According to the release process, the 6.0.15 tag is:
  [ ] Broken
  [ ] Alpha
  [ ] Beta
  [ ] Stable

 I am undecided about how to proceed with the release. The issues,
 although visible, do not sound very serious in the real world, so it
 would seem to be possible to release as stable.

We can also release 6.0.15-beta and put a note in the Release Notes
saying why it's not stable.  There's nothing wrong with having beta
releases ;)

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Filip Hanik - Dev Lists

Remy Maucherat wrote:

On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:
  

The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.15/

According to the release process, the 6.0.15 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[ ] Stable



I am undecided about how to proceed with the release. The issues,
although visible, do not sound very serious in the real world, so it
would seem to be possible to release as stable.
  
I'd push for stable, I'm gonna spend today on the escaping/parsing 
mechanism, to make sure.

Filip

Rémy



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Paul McMahan

Didn't someone say earlier that there was a TCK issue?

Best wishes,
Paul


On Nov 9, 2007, at 11:09 AM, Remy Maucherat wrote:


On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:

The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.15/

According to the release process, the 6.0.15 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[ ] Stable


I am undecided about how to proceed with the release. The issues,
although visible, do not sound very serious in the real world, so it
would seem to be possible to release as stable.

Rémy



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Mark Thomas
Remy Maucherat wrote:
 On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:
 The candidates binaries are available here:
 http://people.apache.org/~remm/tomcat-6/v6.0.15/

 According to the release process, the 6.0.15 tag is:
 [X] Broken
 [ ] Alpha
 [ ] Beta
 [ ] Stable
 
 I am undecided about how to proceed with the release. The issues,
 although visible, do not sound very serious in the real world, so it
 would seem to be possible to release as stable.

Just checking through the release, we still have a licensing issue so I
don't believe we can proceed with the tag as is. See
http://marc.info/?l=tomcat-devm=119170137616267w=2 for details.

Remy - you commmitted the files originally so you are the only one who can
answer the question about their provenance. If the source was such that the
Sun license can be removed, great. If not, we can use the CDDL ones. I am
happy to make the changes myself but I need to know which way to go.

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r593648 - in /tomcat/site/trunk: docs/svn.html xdocs/svn.xml

2007-11-09 Thread markt
Author: markt
Date: Fri Nov  9 12:56:09 2007
New Revision: 593648

URL: http://svn.apache.org/viewvc?rev=593648view=rev
Log:
Make changes to web pages ready for creation of tomcat/trunk. I'll 'svn up' the 
web site as soon as I have created trunk.

Modified:
tomcat/site/trunk/docs/svn.html
tomcat/site/trunk/xdocs/svn.xml

Modified: tomcat/site/trunk/docs/svn.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/svn.html?rev=593648r1=593647r2=593648view=diff
==
--- tomcat/site/trunk/docs/svn.html (original)
+++ tomcat/site/trunk/docs/svn.html Fri Nov  9 12:56:09 2007
@@ -303,7 +303,18 @@
 code/tc6.0.x//code
 /a
 /td
-tdAll modules for Tomcat 6.0.x in a single unified tree/td
+tdThe stable 6.0.x release branch, with all modules in a single
+unified tree/td
+  /tr
+  tr
+td
+a href=http://svn.apache.org/repos/asf/tomcat/trunk;
+code/trunk//code
+/a
+/td
+tdThe primary development branch. Patches are committed here 
+using Commit-then-Review and then voted on for porting to the
+release branches using Review-then-Commit./td
   /tr
   tr
 td
@@ -361,6 +372,10 @@
 thURL/th
   /tr
   tr
+tdCurrent development/td
+tdhttp://svn.apache.org/repos/asf/tomcat/trunk/td
+  /tr
+  tr
 td6.0.x/td
 tdhttp://svn.apache.org/repos/asf/tomcat/tc6.0.x/td
   /tr
@@ -538,22 +553,19 @@
   codetomcat/code directory./li
   liModules no longer used (eg tools service) should be clearly marked as
   archived./li
-  liThe codetrunk/code for each module should be the the development
-  branch of the latest Apache Tomcat version. Since there are always
+  liThe codetrunk/code for each module should be the the branch of the
+  latest Apache Tomcat version that uses that module. Since there are 
always
   several active versions at any one time, rather than be called
-  codetrunk
-/code this directory should be named using the Apache Tomcat
+  codetrunk/code this directory should be named using the Apache Tomcat
   version it represents, eg codetc5.5.x/code./li
-  liThe development branches for the other Apache Tomcat versions
-  will be placed in the codebranches/code directory for each
-  component./li
+  liThe branches for the other Apache Tomcat versions that use that module
+  will be placed in the codebranches/code directory for each component.
+  /li
   liOther (non-development) branches will be placed in the
   codebranches/other/code directory in sub-directories that group the
-  other branches by the
- Apache Tomcat version from which they were
+  other branches by the Apache Tomcat version from which they were
   created./li
   liTags will be treated in exactly the same way as branches./li 
-
 /ul
 
 /blockquote

Modified: tomcat/site/trunk/xdocs/svn.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/svn.xml?rev=593648r1=593647r2=593648view=diff
==
--- tomcat/site/trunk/xdocs/svn.xml (original)
+++ tomcat/site/trunk/xdocs/svn.xml Fri Nov  9 12:56:09 2007
@@ -74,7 +74,15 @@
   tr
 tda href=http://svn.apache.org/repos/asf/tomcat/tc6.0.x;
 code/tc6.0.x//code/a/td
-tdAll modules for Tomcat 6.0.x in a single unified tree/td
+tdThe stable 6.0.x release branch, with all modules in a single
+unified tree/td
+  /tr
+  tr
+tda href=http://svn.apache.org/repos/asf/tomcat/trunk;
+code/trunk//code/a/td
+tdThe primary development branch. Patches are committed here 
+using Commit-then-Review and then voted on for porting to the
+release branches using Review-then-Commit./td
   /tr
   tr
 tda href=http://svn.apache.org/repos/asf/tomcat/watchdog;
@@ -107,6 +115,10 @@
 thApache Tomcat Version/ththURL/th
   /tr
   tr
+tdCurrent development/td
+tdhttp://svn.apache.org/repos/asf/tomcat/trunk/td
+  /tr
+  tr
 td6.0.x/td
 tdhttp://svn.apache.org/repos/asf/tomcat/tc6.0.x/td
   /tr
@@ -200,22 +212,19 @@
   codetomcat/code directory./li
   liModules no longer used (eg tools service) should be clearly marked as
   archived./li
-  liThe codetrunk/code for each module should be the the development
-  branch of the latest Apache Tomcat version. Since there are always
+  liThe codetrunk/code for each module should be the the branch of the
+  latest Apache Tomcat version that uses that module. Since there are 
always
   several active versions at any one time, rather than be called
-  codetrunk
-/code this directory should be named using the Apache Tomcat
+  codetrunk/code this directory should be named using the Apache Tomcat
   version it represents, eg codetc5.5.x/code./li
-  liThe development branches for the other Apache Tomcat versions
-  will be placed in the codebranches/code directory for each
-  component./li
+  

svn commit: r593649 - /tomcat/trunk/

2007-11-09 Thread markt
Author: markt
Date: Fri Nov  9 13:00:38 2007
New Revision: 593649

URL: http://svn.apache.org/viewvc?rev=593649view=rev
Log:
Create C-T-R development branch

Added:
tomcat/trunk/
  - copied from r593648, tomcat/tc6.0.x/trunk/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Time to organise svn - Take 4

2007-11-09 Thread Mark Thomas
Mark Thomas wrote:
 Rémy Maucherat wrote:
 On Sun, 2007-11-04 at 16:10 +, Mark Thomas wrote:
 Do the (unless there is a pressing need - eg a major security issue) final
 stable release of 6.0.x.
 Freeze development of the 6.0.x branch.
 -1. Branches should continue to be open as long as committers want to
 propose patches and make releases.
 
 I see where you are coming from. I still don't think there will be much (or
 indeed any) work on 6.0.x once 6.2.x is stable but you are right, we don't
  need to freeze 6.0.x and we will see what happens.
 
 In the absence of any other comments, I intend to implement Stage 1 (with
 appropriate updates to the svn page on the web site) some time tomorrow
 evening GMT.

Sorry - got delayed build Ikea furniture last night. Working on this now -
should be done shortly.

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread Mark Thomas
Remy Maucherat wrote:
 On Fri, 2007-11-09 at 20:16 +, Mark Thomas wrote:
 Remy Maucherat wrote:
 On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:
 The candidates binaries are available here:
 http://people.apache.org/~remm/tomcat-6/v6.0.15/

 According to the release process, the 6.0.15 tag is:
 [X] Broken
 [ ] Alpha
 [ ] Beta
 [ ] Stable
 I am undecided about how to proceed with the release. The issues,
 although visible, do not sound very serious in the real world, so it
 would seem to be possible to release as stable.
 Just checking through the release, we still have a licensing issue so
 I
 don't believe we can proceed with the tag as is. See
 http://marc.info/?l=tomcat-devm=119170137616267w=2 for details.

 Remy - you commmitted the files originally so you are the only one who
 can
 answer the question about their provenance. If the source was such
 that the
 Sun license can be removed, great. If not, we can use the CDDL ones. I
 am
 happy to make the changes myself but I need to know which way to go.
 
 These sources can be found in the specification documents.
That doesn't mean we can just copy them.

 Geronimo
 should also have the same files somewhere.

I believe they use the CDDL ones but I'll check. I'll prepare a patch for
6.0.16 that uses whatever they use.

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-11-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |




--- Additional Comments From [EMAIL PROTECTED]  2007-11-09 15:21 ---
Some new information on this issue, so I reopened it.  

The problem seems to relate to parsing the body content when the **Transfer-
Encoding: chunked** header is present.  It appears that the chunk length gets
corrupted under load and the client is unable to parse the chunk out of the 
response body.

When the NIO connector parameter **socket.appWriteBufSize** is set to a value 
larger than the total response body, the error condition does not occur.

One might succesfully argue that this is proper performance tuning.  The Tomcat 
documents point out that to scale a large number of long held connections, the 
buffer sizes may need to be less than the response body (the memory footprint 
would be quite large otherwise).

Could there be a race condition involving the response buffering code?  

I have confirmed this behavior on both JDKs 1.5 and 1.6 on both Windows 2003 
and Linux.




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release build 6.0.15

2007-11-09 Thread David Jencks


On Nov 9, 2007, at 2:23 PM, Mark Thomas wrote:


Remy Maucherat wrote:

On Fri, 2007-11-09 at 20:16 +, Mark Thomas wrote:

Remy Maucherat wrote:

On Mon, 2007-11-05 at 15:17 +0100, Rémy Maucherat wrote:

The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.15/

According to the release process, the 6.0.15 tag is:
[X] Broken
[ ] Alpha
[ ] Beta
[ ] Stable

I am undecided about how to proceed with the release. The issues,
although visible, do not sound very serious in the real world,  
so it

would seem to be possible to release as stable.
Just checking through the release, we still have a licensing  
issue so

I
don't believe we can proceed with the tag as is. See
http://marc.info/?l=tomcat-devm=119170137616267w=2 for details.

Remy - you commmitted the files originally so you are the only  
one who

can
answer the question about their provenance. If the source was such
that the
Sun license can be removed, great. If not, we can use the CDDL  
ones. I

am
happy to make the changes myself but I need to know which way to go.


These sources can be found in the specification documents.

That doesn't mean we can just copy them.


Geronimo
should also have the same files somewhere.


I believe they use the CDDL ones but I'll check. I'll prepare a  
patch for

6.0.16 that uses whatever they use.


Geronimo has gone to a lot of trouble and subjected our users to  
noticeable inconvenience to NOT ship any of the sun licensed xsds.   
We have not found any authority or reasoning that would let us do  
so.  I believe the apache policy now allows us to put small numbers  
of CDDL schemas in apache svn and ship them but AFAIK we have not yet  
done so.


thanks
david jencks



Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]