axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bu...@us.ibm.com
Subject RE: DO NOT REPLY [Bug 9881] New: - Stub._setProperty is too for giving
Date Mon, 17 Jun 2002 14:11:04 GMT
Dang!  I forgot about that method.  Yeah, you're right.  I guess we can't
fight this.

Russell Butek
butek@us.ibm.com


Davanum Srinivas <dims@yahoo.com> on 06/17/2002 08:52:37 AM

Please respond to axis-dev@xml.apache.org

To:    axis-dev@xml.apache.org
cc:
Subject:    RE: DO NOT REPLY [Bug 9881] New: - Stub._setProperty is too for
       giving



Russell,

The way i read it...."an invalid or unsupported property name" is one that
is not in the iterator
returned by _getPropertyNames. If a stub allows a _getProperty/_setProperty
on a property name
then IT SHOULD be part of the iterator returned by _getPropertyNames. Am i
completely off?

Thanks,
dims

--- butek@us.ibm.com wrote:
> I agree with you two, and I DID raise the issue a few months ago.  I
think
> we lost the battle.  HOWEVER.  reading the spec carefully, it STILL
sounds
> vague enough that perhaps we can fight it.  The following bullets appears
> in both Stub (8.2.2) and Call (8.2.4) descriptions, relative to
> _setProperty:
>
> • If an optional standard property name is specified, however this Stub
> implementation
> class does not support the configuration of this property.
> • If an invalid or unsupported property name is specified or if a value
of
> mismatched
> property type is passed. An example is an illegal property with the
> standard property
> name prefix javax.xml.rpc.
> • If there is any error in the configuration of a valid property.
>
> Who defines "an invalid or unsupported property name"?  Perhaps it can be
> argued that any name starting with "javax.xml.rpc" that is NOT defined in
> the spec is invalid, but ANY OTHER NAME is valid if the runtime treats it
> as valid.  The TCK uses "foo.bar" to test invalidity.  Perhaps we can
argue
> with them that this should change to "javax.xml.rpc.foo.bar"?
>
> Russell Butek
> butek@us.ibm.com
>
>
> Doug Davis/Raleigh/IBM@IBMUS on 06/16/2002 02:05:59 PM
>
> Please respond to axis-dev@xml.apache.org
>
> To:    axis-dev@xml.apache.org
> cc:
> Subject:    RE: DO NOT REPLY [Bug 9881] New: - Stub._setProperty is too
for
>        giving
>
>
>
>
> +1!  (to glen's comments)
> -Dug
>
> Please respond to axis-dev@xml.apache.org
>
> To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> cc:
> Subject:    RE: DO NOT REPLY [Bug 9881] New:  -  Stub._setProperty is too
> for   giving
>
>
>
>
> -1!
>
> 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)?
>
> Cheers,
> --Glen
>
> > -----Original Message-----
> > From: bugzilla@apache.org [mailto:bugzilla@apache.org]
> > Sent: Friday, June 14, 2002 3:59 PM
> > To: axis-dev@xml.apache.org
> > Subject: DO NOT REPLY [Bug 9881] New: - Stub._setProperty is too
> > forgiving
> >
> >
> > 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=9881>.
> > 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=9881
> >
> > Stub._setProperty is too forgiving
> >
> > Â  Â  Â  Â  Â  Â Summary: Stub._setProperty is too forgiving
> > Â  Â  Â  Â  Â  Â Product: Axis
> > Â  Â  Â  Â  Â  Â Version: current (nightly)
> > Â  Â  Â  Â  Â  Platform: Other
> > Â  Â  Â  Â  OS/Version: Other
> > Â  Â  Â  Â  Â  Â  Status: NEW
> > Â  Â  Â  Â  Â  Severity: Critical
> > Â  Â  Â  Â  Â  Priority: Other
> > Â  Â  Â  Â  Â Component: Basic Architecture
> > Â  Â  Â  Â  AssignedTo: axis-dev@xml.apache.org
> > Â  Â  Â  Â  ReportedBy: butek@us.ibm.com
> >
> >
> > The TCK is failing because Stub._setProperty accepts unknown
> > properties.
> >
> > dims just made some fixes so that Call.setProperty doesn't
> > accept unknown
> > properties. Â The same fixes must be done here. Â (I'm hoping
> > dims can do them
> > since he already did the same thing in Call.java!)
> >
>
>


=====
Davanum Srinivas - http://xml.apache.org/~dims/

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
Mime
View raw message