I am not a big fan a lots of little jar files.
So am I. we already have lots of jars in various projects.
What is the driving motivation for this? Does it solve a
problem users are having?
Apparently, the motivation is from Sun's JWSDP (1.3). When I first saw
their (too) fine-grained jar
Ias wrote:
avoiding duplication. For example, if you use Axis, jUDDI and even JaxMe
toghether, you have three QName classes in your classpath. It may be OK,
however, is not a recommended situation.
If they all would be sharing classes, that would definitely be a source for
classloader
I requested to step down in favor of someone else from XML-RPC quite some time
ago due to time constraints (pmc@ list, I think), but there was no response
and I didn't go looking for a replacement. Ryan, I'd be happy to step down in
your favor.
- Dan
Ryan Hoegg wrote:
Whoops!
I just looked
acutright2004/01/20 09:57:11
Modified:targets/juddi lists.html lists.pdf
Log:
Revision ChangesPath
1.4 +61 -0 ws-site/targets/juddi/lists.html
Index: lists.html
===
RCS file:
I am not a big fan a lots of little jar files.
So am I. we already have lots of jars in various projects.
Sorry for my mistake. I mean Neither am I. :-)
Do you still have the same scheduling problems as you did then? I have
some time to offer ws.apache.org, but see no reason for you to step down
in order for me to step up.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Daniel L. Rall wrote:
I requested to step down in favor of
