You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Wolfgang Hoschek <wo...@cern.ch> on 2001/09/09 12:51:42 UTC
[TC4] Which classloader loads SSLServerSocketFactory?
It itches that a standard JDK needs to modified to get SSL working. I'm
trying to use bootclasspaths, etc. to pick up jsse from a dir outside the
JDK. So far no luck (worked fine with TC 3.2.x).
Can anyone tell me which classloader loads
org.apache.catalina.net.SSLServerSocketFactory
plus, which TC dir would be best suited to stuff jsse jars into?
Thanks,
Wolfgang.
Re: Bug reports
Posted by Remy Maucherat <re...@apache.org>.
> I think that new bug reports should go to the tomcat-dev mailing list. Not
> to individuals.
We have a weekly report + anyone can browse the bugs. If you really want to
flood tomcat-dev, maybe we could also CC: tomcat-dev on each bug report ;-)
> Edit component ... Initial owner
> Catalina remm@apache.org
> Connectors pier@betaversion.org
> Jasper Justyna.Horwat@sun.com
> Tester craig.mcclanahan@sun.com
> Unknown craig.mcclanahan@sun.com
> Webapps craig.mcclanahan@sun.com
Remy
Re: Bug reports
Posted by Christopher Cain <cc...@mhsoftware.com>.
Quoting Jon Stevens <jo...@latchkey.com>:
> on 9/9/01 9:17 PM, "Christopher Cain" <cc...@mhsoftware.com> wrote:
>
> > If people can't abide by majority votes and want to bitch and moan
> after the
> > fact, then you have my permission to bitchslap them ;-)
>
> I agree, but I don't remember seeing a vote on this list about it. If
> there
> had been, all one needs to do is tell me to read the archives and find
> it.
> However, I read most of the messages on this list and I don't remember
> a
> vote.
I dunno about previously, I was only referring to the impending vote. We can
both appreciate Pier's irritation at being pestered ex post facto, so I was
just telling him not to take any guff after the upcoming vote. =)
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 9:17 PM, "Christopher Cain" <cc...@mhsoftware.com> wrote:
> I honestly didn't intend to piss you off or start an argument. I just thought
> I'd make my own personal preference known, but it's not really an issue I'd
> argue about =)
+1
> If people can't abide by majority votes and want to bitch and moan after the
> fact, then you have my permission to bitchslap them ;-)
I agree, but I don't remember seeing a vote on this list about it. If there
had been, all one needs to do is tell me to read the archives and find it.
However, I read most of the messages on this list and I don't remember a
vote.
-jon
Re: Bug reports
Posted by Christopher Cain <cc...@mhsoftware.com>.
I'm sorry buddy ;-)
I don't feel terribly strongly about it, that's just my own personal take. I'm
really the new kid on the block, so I'll go along with whatever most people
want to do.
I honestly didn't intend to piss you off or start an argument. I just thought
I'd make my own personal preference known, but it's not really an issue I'd
argue about =)
If people can't abide by majority votes and want to bitch and moan after the
fact, then you have my permission to bitchslap them ;-)
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Quoting Pier Fumagalli <pi...@betaversion.org>:
> "Christopher Cain" <cc...@mhsoftware.com> wrote:
>
> > I, personally, would like to see the full bug report e-mails when they
> are
> > filed, like in the old days.
>
> And I was flamed for setting it up that way when I installed BugZilla
> on
> Nagoya... Now I'm flamed because of the opposite...
>
> I'm fucking damn tired to be flamed for everything I do to help out...
> I
> should learn to let everything screw up and "not care" about a damn
> thing.
>
> Or maybe I'd better fork off and take care of my own stuff...
>
> Pier (really upset)
>
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
> on 9/9/01 8:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
>
>> And I was flamed for setting it up that way when I installed BugZilla on
>> Nagoya...
>
> When was the decision made to change it? Was it done on this list (or
> general@jakarta) or was it done privately behind Sun's walls?
Here
Re: Bug reports
Posted by Christopher Cain <cc...@mhsoftware.com>.
Quoting Jon Stevens <jo...@latchkey.com>:
> on 9/9/01 10:48 PM, "Craig R. McClanahan" <cr...@apache.org> wrote:
>
> > Whining about practices that have been consistent (on Tomcat at least)
> for
> > a couple of years is a waste of everybody's time :-).
>
> Of course. However, I'm going on Pier's information to the contrary.
Tomcat-Dev did get bugzilla notifications when I first joined up ... I remember
them. Surely it wasn't more than a year ago that they stopped coming, was it?
If so, wow ... tempus fugit =)
In any case, I always thought it was pretty convenient. In fact, I originally
started looking into bugs because I would just happen to see something that I
knew about. At the time, I doubt I would have actively hit bugzilla looking for
stuff to fix. IMHO ... a) it means more eyeballs seeing the bug reports, b) it
doesn't add a remarkable amount of traffic to the list, and c) people can
always filter it out if they like. Since at least a few other people liked
having them as well, I'll go ahead and call the vote (as suggested).
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 10:48 PM, "Craig R. McClanahan" <cr...@apache.org> wrote:
> It's never been "changed" ... even in the previous installation of
> Bugzilla (that led to the first hack on Apache's web site), there were
> individual names attached to Tomcat components.
Not according to Pier's posting:
> And I was flamed for setting it up that way when I installed BugZilla on
> Nagoya... Now I'm flamed because of the opposite...
> A vote to change current practice is (of course) relevant at any time.
Which is why I brought it up.
> Whining about practices that have been consistent (on Tomcat at least) for
> a couple of years is a waste of everybody's time :-).
Of course. However, I'm going on Pier's information to the contrary.
-jon
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Craig R. McClanahan" <cr...@apache.org> wrote:
> It's never been "changed" ... even in the previous installation of
> Bugzilla (that led to the first hack on Apache's web site), there were
> individual names attached to Tomcat components.
On the very first installation, the one on Daedalus, I remember that for the
first probably 2 or 3 days we had it set up as bugrat (which sent messages
to the ML), and people complained...
Pier
Re: Bug reports
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Sun, 9 Sep 2001, Jon Stevens wrote:
> Date: Sun, 09 Sep 2001 21:55:42 -0700
> From: Jon Stevens <jo...@latchkey.com>
> Reply-To: tomcat-dev@jakarta.apache.org
> To: tomcat-dev <to...@jakarta.apache.org>
> Subject: Re: Bug reports
>
> on 9/9/01 8:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
>
> > And I was flamed for setting it up that way when I installed BugZilla on
> > Nagoya...
>
> When was the decision made to change it? Was it done on this list (or
> general@jakarta) or was it done privately behind Sun's walls?
>
> :-)
>
It's never been "changed" ... even in the previous installation of
Bugzilla (that led to the first hack on Apache's web site), there were
individual names attached to Tomcat components.
A vote to change current practice is (of course) relevant at any time.
Whining about practices that have been consistent (on Tomcat at least) for
a couple of years is a waste of everybody's time :-).
> -jon
>
>
Craig
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
> on 9/9/01 9:55 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
>
>> When was the decision made to change it? Was it done on this list (or
>> general@jakarta) or was it done privately behind Sun's walls?
>>
>> :-)
>>
>> -jon
>
> Let me also point out that all of the people who are "responsible" for the
> bug reports are Sun employees.
Jon, in all the time we've known each other, I _believe_ you knew me and
WHAT are my principles... Apparently you don't... WHAT-EVER!
Pier
> Things that make you go hmmmm....
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 9:55 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
> When was the decision made to change it? Was it done on this list (or
> general@jakarta) or was it done privately behind Sun's walls?
>
> :-)
>
> -jon
Let me also point out that all of the people who are "responsible" for the
bug reports are Sun employees.
Things that make you go hmmmm....
-jon
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 8:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> And I was flamed for setting it up that way when I installed BugZilla on
> Nagoya...
When was the decision made to change it? Was it done on this list (or
general@jakarta) or was it done privately behind Sun's walls?
:-)
-jon
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Christopher Cain" <cc...@mhsoftware.com> wrote:
> I, personally, would like to see the full bug report e-mails when they are
> filed, like in the old days.
And I was flamed for setting it up that way when I installed BugZilla on
Nagoya... Now I'm flamed because of the opposite...
I'm fucking damn tired to be flamed for everything I do to help out... I
should learn to let everything screw up and "not care" about a damn thing.
Or maybe I'd better fork off and take care of my own stuff...
Pier (really upset)
Re: Bug reports
Posted by Christopher Cain <cc...@mhsoftware.com>.
I, personally, would like to see the full bug report e-mails when they are
filed, like in the old days. It can be cumbersome to hit nagoya and query for
bugs every few days just to stay current. I think that the weekly summaries are
an excellent tool and should continue coming, as it's a nice status report of
how well we are staying on top of bugzilla in general, but seeing the full
descriptions in real-time would also be a nice convenience. I agree with Jon
that it encourages participation by non-committers, but beyond that it also
helps out committers like me who aren't directly notified on any particular
category.
As far as how to handle the notifications, I don't really have a preference.
Send them all to the dev list, send them to their current "owners" and just CC
the list, set up a new list for bugs ... as long as I can get them to hit my
inbox, I'm not too particular ;-)
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Quoting Jon Stevens <jo...@latchkey.com>:
> on 9/9/01 6:49 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
>
> > Ok, I agree with you, maybe "responsible" is the wrong word... I have
> no
> > problems in moving all emails to the list (as I get a copy of each
> single
> > mail bugzilla sends). Sending mails to individuals IMO is better
> because the
> > people listed there are the ones who can see "on the spot" if a bug is
> valid
> > or not, who can take immediate action, or not...
> >
> > If this list wants to be cluttered with mails about bugs, let's just
> do the
> > change (but I remember that when I set up bugzilla, most didn't want
> to see
> > them, and that's why we changed)...
>
> This is a DEVELOPERS list. The people on this list are the ones who can
> fix
> the bugs and by having the bug reports go here, people can volunteer
> more
> easily to fix bugs they are interested in.
>
> Unless the developer goes to the website to read the full description of
> the
> bug report, then they can't easily fix the bug.
>
> It is nice being able to see a full bug report *when it comes in* so
> that it
> can be quickly dealt with or someone can quickly volunteer to fix it
> without
> having to go to the website.
>
> Your weekly report email is a good summary device, but it isn't an
> adequate*
> solution (IMHO) towards encouraging random developers to jump in and
> fix
> those outstanding bugs (which is what we want IMHO).
>
> My opinion is that if people on this list don't care about bugs, then
> they
> can either join the USERS list or filter them out with their email
> client.
>
> Here is another point: What if one of you goes on vacation and forgets
> to
> make the switch to assign it to someone else? The *only* thing that
> will
> notify the list of the bug is the weekly email. What if it is a
> security
> hole bug report and the weekly email isn't set to go out for another 6
> days?
> I understand that you get a copy of all of the emails, but that is still
> a
> single point of failure if you get behind a couple days on your own
> emails
> (or don't read one of them closely enough).
>
> > How isn't it adequate? (Sometimes I wish not to do shit, like the
> scripts to
> > send automatic email about bugs, so that people will not start
> complaining)
>
> See above *.
>
> p.s. I would be interested to see over time after sending the emails to
> this
> list when they get submitted, if random developers volunteer to fix
> bugs
> that come in.
>
> p.p.s. Paulo's suggestion still defeats the point I'm trying to get
> across.
> For example, I have always preferred CVS commit emails going to the
> -dev
> list because it causes more people to look at the commits and comment
> on
> them (peer review is one of our selling points, lets capitalize on
> that). If
> bugs go to their own list, then chances are most people aren't going to
> see
> them because they either don't know about the bugs list or are to lazy
> to
> subscribe.
>
> -jon
>
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
>> Nope... Because I check the web...
>
> Pier, you missed the point. I'm trying to say that you and the person
> assigned to the emails are potential central points of failures.
Just because you don't want to click thru a couple of pages? Make me laugh
c'mon...
>> Ok, propose a vote, then...
>
> Isn't that what I'm doing?
Nope... Until now you just complained :)
>> And again, so many projects have a separate -cvs mailing list... Not all
>> project are "Jon-ized", if you want to change them, submit a request for
>> vote.
>
> I was giving examples and reasons why it is a good idea to encourage
> developers to participate, not try to "jon-ize" every project out there.
Well... At the beginning bugs were sent here, then on this mailing list
people complained because of it, so we assigned them to individuals, now
people complain of the contrary...
>> (on the bug issue, I don't give a damn about where those emails end up to, I
>> get notified anyhow)
>
> YOU clearly don't give a damn about the rest of us either. :-(
I am just saying... FOR ONCE, someone tell me what to do, because I'm sick
and tired to be flamed for ANYTHING I do... I don't set up BugZilla, they
flame me about it since GNATS sucks, I set up BugZilla, I'm flamed because I
should use GNATS (which sucks and nobody uses anyway), I send out emails,
I'm flamed, I don't I'm flamed... I AM TIRED!
Pier
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 8:43 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> "Jon Stevens" <jo...@latchkey.com> wrote:
>
>> Here is another point: What if one of you goes on vacation and forgets to
>> make the switch to assign it to someone else? The *only* thing that will
>> notify the list of the bug is the weekly email. What if it is a security
>> hole bug report and the weekly email isn't set to go out for another 6 days?
>> I understand that you get a copy of all of the emails, but that is still a
>> single point of failure if you get behind a couple days on your own emails
>> (or don't read one of them closely enough).
>
> Nope... Because I check the web...
Pier, you missed the point. I'm trying to say that you and the person
assigned to the emails are potential central points of failures.
> Ok, propose a vote, then...
Isn't that what I'm doing?
> And again, so many projects have a separate -cvs mailing list... Not all
> project are "Jon-ized", if you want to change them, submit a request for
> vote.
I was giving examples and reasons why it is a good idea to encourage
developers to participate, not try to "jon-ize" every project out there.
> (on the bug issue, I don't give a damn about where those emails end up to, I
> get notified anyhow)
YOU clearly don't give a damn about the rest of us either. :-(
-jon
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
> Here is another point: What if one of you goes on vacation and forgets to
> make the switch to assign it to someone else? The *only* thing that will
> notify the list of the bug is the weekly email. What if it is a security
> hole bug report and the weekly email isn't set to go out for another 6 days?
> I understand that you get a copy of all of the emails, but that is still a
> single point of failure if you get behind a couple days on your own emails
> (or don't read one of them closely enough).
Nope... Because I check the web...
>> How isn't it adequate? (Sometimes I wish not to do shit, like the scripts to
>> send automatic email about bugs, so that people will not start complaining)
>
> See above *.
>
> p.s. I would be interested to see over time after sending the emails to this
> list when they get submitted, if random developers volunteer to fix bugs
> that come in.
Ok, propose a vote, then...
> p.p.s. Paulo's suggestion still defeats the point I'm trying to get across.
> For example, I have always preferred CVS commit emails going to the -dev
> list because it causes more people to look at the commits and comment on
> them (peer review is one of our selling points, lets capitalize on that). If
> bugs go to their own list, then chances are most people aren't going to see
> them because they either don't know about the bugs list or are to lazy to
> subscribe.
And again, so many projects have a separate -cvs mailing list... Not all
project are "Jon-ized", if you want to change them, submit a request for
vote.
(on the bug issue, I don't give a damn about where those emails end up to, I
get notified anyhow)
Pier
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 6:49 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> Ok, I agree with you, maybe "responsible" is the wrong word... I have no
> problems in moving all emails to the list (as I get a copy of each single
> mail bugzilla sends). Sending mails to individuals IMO is better because the
> people listed there are the ones who can see "on the spot" if a bug is valid
> or not, who can take immediate action, or not...
>
> If this list wants to be cluttered with mails about bugs, let's just do the
> change (but I remember that when I set up bugzilla, most didn't want to see
> them, and that's why we changed)...
This is a DEVELOPERS list. The people on this list are the ones who can fix
the bugs and by having the bug reports go here, people can volunteer more
easily to fix bugs they are interested in.
Unless the developer goes to the website to read the full description of the
bug report, then they can't easily fix the bug.
It is nice being able to see a full bug report *when it comes in* so that it
can be quickly dealt with or someone can quickly volunteer to fix it without
having to go to the website.
Your weekly report email is a good summary device, but it isn't an adequate*
solution (IMHO) towards encouraging random developers to jump in and fix
those outstanding bugs (which is what we want IMHO).
My opinion is that if people on this list don't care about bugs, then they
can either join the USERS list or filter them out with their email client.
Here is another point: What if one of you goes on vacation and forgets to
make the switch to assign it to someone else? The *only* thing that will
notify the list of the bug is the weekly email. What if it is a security
hole bug report and the weekly email isn't set to go out for another 6 days?
I understand that you get a copy of all of the emails, but that is still a
single point of failure if you get behind a couple days on your own emails
(or don't read one of them closely enough).
> How isn't it adequate? (Sometimes I wish not to do shit, like the scripts to
> send automatic email about bugs, so that people will not start complaining)
See above *.
p.s. I would be interested to see over time after sending the emails to this
list when they get submitted, if random developers volunteer to fix bugs
that come in.
p.p.s. Paulo's suggestion still defeats the point I'm trying to get across.
For example, I have always preferred CVS commit emails going to the -dev
list because it causes more people to look at the commits and comment on
them (peer review is one of our selling points, lets capitalize on that). If
bugs go to their own list, then chances are most people aren't going to see
them because they either don't know about the bugs list or are to lazy to
subscribe.
-jon
RE: Bug reports
Posted by Paulo Gaspar <pa...@krankikom.de>.
> Ok, I agree with you, maybe "responsible" is the wrong word... I have no
> problems in moving all emails to the list (as I get a copy of each single
> mail bugzilla sends).
Why not having a "tomcat-bugs" mailling list then?
And then, maybe a daily digest to "tomcat-dev", just to make everybody
aware (both of the bugs and of the existence of the "tomcat-bugs" list).
Besides that you can - of course - send bug messages to individuals,
depending on their scope.
Have fun,
Paulo Gaspar
P.S.: This solution looks so simple that I feel I am missing something.
> -----Original Message-----
> From: Pier Fumagalli [mailto:pier@betaversion.org]
> Sent: Monday, September 10, 2001 3:49 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: Bug reports
>
>
> "Jon Stevens" <jo...@latchkey.com> wrote:
>
> > on 9/9/01 5:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> >
> >> "Jon Stevens" <jo...@latchkey.com> wrote:
> >>
> >>> I think that new bug reports should go to the tomcat-dev
> mailing list. Not
> >>> to individuals.
> >>>
> >>> Edit component ... Initial owner
> >>> Catalina remm@apache.org
> >>> Connectors pier@betaversion.org
> >>> Jasper Justyna.Horwat@sun.com
> >>> Tester craig.mcclanahan@sun.com
> >>> Unknown craig.mcclanahan@sun.com
> >>> Webapps craig.mcclanahan@sun.com
> >>
> >> I don't agree... Having them assigned to a particular
> developer, makes it
> >> easy to see who's actually "responsible" for a particular component
> >
> > When did only one person become responsible for a particular
> component? I
> > thought (in true OSS fashion) it was all members of the project are
> > responsible for whatever they want.
>
> When you stopped fixing my bugs in the WebApp module :) :) :)
>
> > I'm thinking beyond just Tomcat, but all OSS projects on Jakarta.
>
> Ok, I agree with you, maybe "responsible" is the wrong word... I have no
> problems in moving all emails to the list (as I get a copy of each single
> mail bugzilla sends). Sending mails to individuals IMO is better
> because the
> people listed there are the ones who can see "on the spot" if a
> bug is valid
> or not, who can take immediate action, or not...
>
> If this list wants to be cluttered with mails about bugs, let's
> just do the
> change (but I remember that when I set up bugzilla, most didn't
> want to see
> them, and that's why we changed)...
>
> BTW, it's not only TC4 which does that, most of the projects on BugZilla
> (both Jakarta and XML) follow that scheme... It might be "more
> appropriate"
> to move this discussion to general@jakarta and general@xml...
>
> >> , and
> >> given that the weekly bug-report now gets to the mailing list,
> I believe
> >> that the current setup is right...
> >
> > This helps, but is still not adequate IMHO.
>
> How isn't it adequate? (Sometimes I wish not to do shit, like the
> scripts to
> send automatic email about bugs, so that people will not start
> complaining)
>
> Pier
>
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
> on 9/9/01 5:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
>
>> "Jon Stevens" <jo...@latchkey.com> wrote:
>>
>>> I think that new bug reports should go to the tomcat-dev mailing list. Not
>>> to individuals.
>>>
>>> Edit component ... Initial owner
>>> Catalina remm@apache.org
>>> Connectors pier@betaversion.org
>>> Jasper Justyna.Horwat@sun.com
>>> Tester craig.mcclanahan@sun.com
>>> Unknown craig.mcclanahan@sun.com
>>> Webapps craig.mcclanahan@sun.com
>>
>> I don't agree... Having them assigned to a particular developer, makes it
>> easy to see who's actually "responsible" for a particular component
>
> When did only one person become responsible for a particular component? I
> thought (in true OSS fashion) it was all members of the project are
> responsible for whatever they want.
When you stopped fixing my bugs in the WebApp module :) :) :)
> I'm thinking beyond just Tomcat, but all OSS projects on Jakarta.
Ok, I agree with you, maybe "responsible" is the wrong word... I have no
problems in moving all emails to the list (as I get a copy of each single
mail bugzilla sends). Sending mails to individuals IMO is better because the
people listed there are the ones who can see "on the spot" if a bug is valid
or not, who can take immediate action, or not...
If this list wants to be cluttered with mails about bugs, let's just do the
change (but I remember that when I set up bugzilla, most didn't want to see
them, and that's why we changed)...
BTW, it's not only TC4 which does that, most of the projects on BugZilla
(both Jakarta and XML) follow that scheme... It might be "more appropriate"
to move this discussion to general@jakarta and general@xml...
>> , and
>> given that the weekly bug-report now gets to the mailing list, I believe
>> that the current setup is right...
>
> This helps, but is still not adequate IMHO.
How isn't it adequate? (Sometimes I wish not to do shit, like the scripts to
send automatic email about bugs, so that people will not start complaining)
Pier
Re: Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/9/01 5:46 PM, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> "Jon Stevens" <jo...@latchkey.com> wrote:
>
>> I think that new bug reports should go to the tomcat-dev mailing list. Not
>> to individuals.
>>
>> Edit component ... Initial owner
>> Catalina remm@apache.org
>> Connectors pier@betaversion.org
>> Jasper Justyna.Horwat@sun.com
>> Tester craig.mcclanahan@sun.com
>> Unknown craig.mcclanahan@sun.com
>> Webapps craig.mcclanahan@sun.com
>
> I don't agree... Having them assigned to a particular developer, makes it
> easy to see who's actually "responsible" for a particular component
When did only one person become responsible for a particular component? I
thought (in true OSS fashion) it was all members of the project are
responsible for whatever they want.
I'm thinking beyond just Tomcat, but all OSS projects on Jakarta.
>, and
> given that the weekly bug-report now gets to the mailing list, I believe
> that the current setup is right...
This helps, but is still not adequate IMHO.
-jon
Re: Bug reports
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jon Stevens" <jo...@latchkey.com> wrote:
> I think that new bug reports should go to the tomcat-dev mailing list. Not
> to individuals.
>
> Edit component ... Initial owner
> Catalina remm@apache.org
> Connectors pier@betaversion.org
> Jasper Justyna.Horwat@sun.com
> Tester craig.mcclanahan@sun.com
> Unknown craig.mcclanahan@sun.com
> Webapps craig.mcclanahan@sun.com
I don't agree... Having them assigned to a particular developer, makes it
easy to see who's actually "responsible" for a particular component, and
given that the weekly bug-report now gets to the mailing list, I believe
that the current setup is right...
Pier
Bug reports
Posted by Jon Stevens <jo...@latchkey.com>.
I think that new bug reports should go to the tomcat-dev mailing list. Not
to individuals.
Edit component ... Initial owner
Catalina remm@apache.org
Connectors pier@betaversion.org
Jasper Justyna.Horwat@sun.com
Tester craig.mcclanahan@sun.com
Unknown craig.mcclanahan@sun.com
Webapps craig.mcclanahan@sun.com
-jon
Re: [TC4] Which classloader loads SSLServerSocketFactory?
Posted by "Craig R. McClanahan" <cr...@apache.org>.
SSLServerSocketFactory is in the catalina.jar file in
$CATALINA_HOME/server/lib, so it gets loaded by the "Catalina" class
loader. For more information, see the class loader docs, online at:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc-exp/class-loader-howto.html
You will also find detailed instructions on getting set up with SSL:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc-exp/ssl-howto.html
which suggests putting the JSSE classes in $JAVA_HOME/jre/lib/ext as
system extensions. Putting them anywhere inside one of the Catalina
repositories causes wierd errors, due to programming inside the JSSE
library. The other alternative is to modify the class path that is
created (inside catalina.sh or catalina.bat) to include them.
Craig
On Sun, 9 Sep 2001, Wolfgang Hoschek wrote:
> Date: Sun, 09 Sep 2001 12:51:42 +0200
> From: Wolfgang Hoschek <wo...@cern.ch>
> Reply-To: tomcat-dev@jakarta.apache.org
> To: tomcat-dev@jakarta.apache.org
> Subject: [TC4] Which classloader loads SSLServerSocketFactory?
>
> It itches that a standard JDK needs to modified to get SSL working. I'm
> trying to use bootclasspaths, etc. to pick up jsse from a dir outside the
> JDK. So far no luck (worked fine with TC 3.2.x).
>
> Can anyone tell me which classloader loads
>
> org.apache.catalina.net.SSLServerSocketFactory
>
> plus, which TC dir would be best suited to stuff jsse jars into?
>
> Thanks,
> Wolfgang.
>
>