Moin Mike,
WOLips has a console listener to grap the url and open the Eclipse
internal WebBrowser. Some lines for that and the interaction with the
webapp and we're done :-)
Uli
Am 07.09.2005 um 16:48 schrieb Mike Schrag:
> It was more of a "I think it would be cool to do" more than a "I'm
> working on it now". I need to see if it's possible to hook into
> the console and "see" when stack traces come across. I'm thinking
> it might be more useful as a log4j plugin, since that would have
> more direct access to when exceptions occur.
>
> ms
>
> On Sep 7, 2005, at 4:34 AM, Ulrich Köster wrote:
>
>
>> Hi Mike,
>>
>> is there a timeframe for the plugin part?
>>
>> Uli
>> Am 06.09.2005 um 19:45 schrieb Mike Schrag:
>>
>>
>>
>>> Yeah I agree -- Right now the UI just isn't very streamlined for
>>> this. It's actually designed behind the scenes for this. In
>>> fact, you should be able to put in a stack trace that already
>>> exists and click on that "add an explanation" at the top and it
>>> should do the right thing (i.e. there should now be two
>>> explanations for the same exception). I was meaning to add just
>>> an "add explanation" button on the stack trace browser, though,
>>> too. I'll put that on the to-do list.
>>>
>>> ms
>>>
>>> On Sep 6, 2005, at 12:55 PM, Chuck Hill wrote:
>>>
>>>
>>>
>>>
>>>> I think this will be quite useful. My only suggestion would be
>>>> to allow others to edit / annotate / comment on the causes of an
>>>> exception that they have not reported. Some of these have more
>>>> than one cause and it would be good to collect them all (get a
>>>> full set folks! :-P)
>>>>
>>>> Chuck
>>>>
>>>>
>>>>
>>>> On Sep 3, 2005, at 10:03 PM, Mike Schrag wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Since this mailing list is lower traffic, I thought I'd send
>>>>> this to you guys to play around w/ and try out first before I
>>>>> post it on the WO mailing list:
>>>>>
>>>>> http://www.mdimension.com/cgi-bin/WebObjects/Exceptional.woa
>>>>>
>>>>> Basically it's a database of stack traces that people can add
>>>>> to and post explanations/fixes for the root cause ... I got so
>>>>> annoyed with a particular really obtuse exception that was
>>>>> coming out of some really low level part of EOF (a result of a
>>>>> blanked out column by EOModeler) that took forever to track
>>>>> down. Basically it will parse your stack trace and look to see
>>>>> if anyone has posted an explanation of the same type of
>>>>> exception that came from the same line/class/method/etc as the
>>>>> the trace you're looking for. I'm thinking I might make an
>>>>> eclipse plugin or Log4J handler that wires into this via a
>>>>> webservice to basically intercept exceptions before they
>>>>> display to you and just lookup the real explanation of the
>>>>> problem ... Never again will I hunt for the reason a goofy
>>>>> exception occurred :)
>>>>>
>>>>> I've only loaded a handful of stack traces so far (any
>>>>> exception i got while i was writing the app itself, i loaded
>>>>> into it :) ).
>>>>>
>>>>> ms
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Practical WebObjects - a book for intermediate WebObjects
>>>> developers who want to increase their overall knowledge of
>>>> WebObjects, or those who are trying to solve specific
>>>> application development problems.
>>>> http://www.global-village.net/products/practical_webobjects
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Thu Sep 08 2005 - 07:25:53 EDT