Hi James, You patch got filtered out :(
The best way to submit a patch is to first create a Bugzilla bug and then attach the patch there. That way: 1) We (the developers) are guaranteed to notice it. 2) The patch is recorded so it can be added to the release notes. We are more than happy to evaluate and apply you other patches, just post them to Bugzilla. p.s. Please make sure your patches are created against the CVS head, this makes the committer's life SO much easier ;) Regards, *===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: James Agnew [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 10:28 AM > To: [EMAIL PROTECTED] > Subject: Submitting patch > > Hello to anyone reading this list.. > > I would just like to submit a small patch, in case the > jetspeed community finds it useful. The patch affects > the following file: > > src/java/org/apache/jetspeed/modules/actions/portlets/PortletActionEvent.j > ava > > Currently, upon firing an action event, the > fireEvent() method will silently discard any > exceptions thrown by the portlet action classes, > making the debugging of action classes more difficult. > This patch causes any exceptions thrown in the action > classes to be re-thrown upwards. > > ps, I will attach the patch to this message. If this > doesn't work, please accept my appologies. I will find > an alternate method of providing the patch. And, fyi: > my organisation is currently developing a large > physician portal, and we are using JetSpeed as a > portal framework. I have several other bugfixes and > features in mind that I will be submitting patches for > in the coming weeks. > > James Agnew > University Health Network > Toronto, Canada > > ______________________________________________________________________ > Post your free ad now! http://personals.yahoo.ca
