avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19452] - XSLT processorImpl causes warnings to fired
Date Wed, 30 Apr 2003 14:11:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19452>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19452

XSLT processorImpl causes warnings to fired





------- Additional Comments From tagunov@motor.ru  2003-04-30 14:11 -------
I get the arguments and LIKE it very much -- indeed release null == no-op
Not cleaning up after a crash -- 
just the way I like it :-))

But

1) ECM does complain about null releases maybe it should stop 
doing so?

2) I'm willing to find out what the contract is -- if my component crashes
   and does not 
clean up -- then who is responsible for cleaning up
   the resources? I get it that the resource may be 
as expenisve as
   an open socket or something that should better be released.
   And such a beast 
may be hidden behind something harmless
   like Source object.. Am I right?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message