axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <>
Subject Re: DO NOT REPLY [Bug 9881] New: - Stub._setProperty is too for giving
Date Mon, 17 Jun 2002 13:15:40 GMT
Glen Daniels wrote:

>This seems very bad, and we should take it up with the TCK/JAX-RPC guys.  Does the spec
actually mandate this?
>One of the whole points of _setProperty() is precisely that you can set properties that
the framework has no clue about, so that they can later be accessed by your Handlers - this
is how a lot of extensibility in Axis works.
>If _setProperty() only accepts "known" properties, then why both with _setProperty() at
all (as opposed to setKnownThing1(), setKnownThing2(), etc)?

Just an FYI.  Glen, we've (you+I) have had this dicussion before.  If 
there was some way a handler could declare what properties it is 
concerned with, Axis could provide more meaningful error messages.

I presume that the spec writers were trying to parallel 
javax.xml.parsers.DocumentBuilderFactory.setAttribute ... an interface 
that is both extensible and provides feedback when an attribute is 
specified that does not make sense in this particular implementation..

- Sam Ruby

View raw message