Re: EventException

This is a multi-part message in MIME format...

------------=_1166034948-20094-107
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Quoting Denny Chambers <[email protected]>:

> I agree. Would you like to see these as web.xml parameters?

Maybe, but not necessarily.  I think web.xml parameters could get quite
voluminous depending on how many features need to be configured.  I envision
more of a componentization of Barracuda so features can be included or excl=
uded
with no overhead if they are excluded (and probably done via a separate con=
fig
file, such as the existing ones or some new one).  I'm thinking specificall=
y of
the way ApplicationGateway has increased in complexity as new features have=
 been
added, such as long running events.  That could have been a plugin, IMO.  I
don't claim to have an alternative design, but it seems to me it could be d=
one
in a cleaner way.

> Also I am
> curious to hear more about the "Moving forward" part. I have quite a bit
> invested in Barracuda, and would like to here more about the future road
> map.
>

Unfortunately, I can't say that I'm going to be the person moving things
forward.  Lately, my free time's been spent on my kids and some XMLC
development (actually quite a bit lately).  Since Barracuda is a good testb=
ed
for XMLC, I continue to integrate new versions and try to keep things gener=
ally
up to date, but as for big plans, I don't really have any.  I haven't been =
able
to use Barracuda for work for just about 3 years (all Struts-based developm=
ent
where I am now).  I treat it more as a hobby.

With Christian now more directed toward non-technical aspects of life and m=
e not
being able to dedicate much time to Barracuda, I think it's time for others=
 in
the community to step up and take the lead.  You and Franck seem to be the =
most
active.  I know ATMReports is heavily invested in Barracuda, but they must =
be
satisfied with where things are at since I've seen very little activity out=
 of
them for a while now (please correct me if I'm wrong).

So, it seems to me that you, the active users, can either build upon the ro=
ad
map in the docs (I think it's still there in the new docs that Christian put
there) or blaze your own path (along with the rest of the community, of
course).  My only guiding principal is that any new development on Barracuda
should make it simpler (in design, to use, etc...), not more complex.  If t=
his
requires an incompatible Barracuda3, which would be a whole new branch, I'd=
 be
fine with that.  I'm not trying to trash Barracuda2.  I'm just saying that I
think the codebase has become overly complex and could be simplified and ma=
de
more pluggable.

Anyway, the main point is, Barracuda is an open source project and if the
project leaders can't be as much involved as the community needs them to be=
, it
may be time for some new leaders to step up and take the reigns.

Jake

> Jacob Kjome wrote:
> > At 03:58 PM 12/12/2006, you wrote:
> > >Found another way to do this. In the ApplicationGateway class there is=
 a
> > >boolean value called RESPOND_WITH_404 that is set to false by default.
> > >Setting this to true will send a 404 error when an EventExceptions
> > >occurs. This works great for me, since sending the 404 is what I wanted
> > >in the first place.
> > >
> >
> > Glad it works.  I'm not so keen on all these static variables for
> > configuration, though.  Moving forward, I'd like to see less of this.
> >
> > Jake
> >
> > >Denny
> > >
> > >Denny Chambers wrote:
> > >> Looks like I need to override the  handleEventException(..) method f=
or
> > >> the ApplicationGateway class. This is also used in the
> > >> ComponentGateway class.
> > >>
> > >> Denny
> > >>
> > >> Denny Chambers wrote:
> > >>> The servlet spec will not work here, because the exception is not
> > >>> being bubbled up to the Web Server code. It is being handled by the
> > >>> Barracuda code. If they were throwing the excpetion up, I could
> > >>> handle it in the web.xml file in the way you described below. I
> > >>> already do this for most of the HTTP error code, and a few other
> > >>> exception. I think this response may be coming from the dispatch
> > >>> queue or some close to that, when it can't map the event url to a
> > >>> class. I will try to look at the code today, and see if I can figure
> > >>> it out from there.
> > >>>
> > >>> Denny
> > >>>
> > >>> Jacob Kjome wrote:
> > >>>>
> > >>>> Hi Denny,
> > >>>>
> > >>>> I don't recall of the top of my head if there's a way to capture
> > >>>> this?   I've had my head buried in XMLC development and other stuff
> > >>>> and haven't dealt with much Barracuda development of late.
> > >>>> Hopefully one of the guys at ATMReports can help with this, since I
> > >>>> know they use Barracuda on an ongoing basis.
> > >>>>
> > >>>> ....Actually, the servlet spec might provide for this.  I seem to
> > >>>> recall you can define error pages for particular exceptions.  This
> > >>>> would be configured in web.xml.  Check out the <error-page> element
> > >>>> (I think that's what it's called?).
> > >>>>
> > >>>>
> > >>>> Jake
> > >>>>
> > >>>> At 03:57 PM 12/5/2006, you wrote:
> > >>>> >Resent with the Digital Signature turned off.
> > >>>> >
> > >>>> >When an invalid event URL is requested to a Barracuda webapp,
> > you will
> > >>>> >get an Error: EventException, with a Barracuda specific message,
> > and a
> > >>>> >stacktrace. i would like to override this canned message with my
> > own
> > >>>> >error page. Is there an event that i need to listen for to make
> > this
> > >>>> >happen?
> > >>>> >
> > >>>> >Denny
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> >--
> > >>>> >Barracuda mailing list
> > >>>> >[email protected]
> > >>>> >http://www.objectweb.org/wws/lists/projects/barracuda
> > >>>>
> > >>>>
> > >>>>
> > ------------------------------------------------------------------------
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> Barracuda mailing list
> > >>>> [email protected]
> > >>>> http://www.objectweb.org/wws/lists/projects/barracuda
> > >>>>
> > >>>
> > >>>
> > ------------------------------------------------------------------------
> > >>>
> > >>>
> > >>> --
> > >>> Barracuda mailing list
> > >>> [email protected]
> > >>> http://www.objectweb.org/wws/lists/projects/barracuda
> > >>>
> > >>
> > >>
> > ------------------------------------------------------------------------
> > >>
> > >>
> > >> --
> > >> Barracuda mailing list
> > >> [email protected]
> > >> http://www.objectweb.org/wws/lists/projects/barracuda
> > >>
> > >
> > >
> > >
> > >--
> > >Barracuda mailing list
> > >[email protected]
> > >http://www.objectweb.org/wws/lists/projects/barracuda
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > --
> > Barracuda mailing list
> > [email protected]
> > http://www.objectweb.org/wws/lists/projects/barracuda
> >
>
>





------------=_1166034948-20094-107
Content-Type: text/plain; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: 8bit



--

Barracuda mailing list

[email protected]

http://www.objectweb.org/wws/lists/projects/barracuda


------------=_1166034948-20094-107--