[
http://issues.apache.org/jira/browse/AXIS-849?page=comments#action_12312604 ]
Peter Wisnovsky commented on AXIS-849:
--------------------------------------
I see from a closer reading of the spec that use=prohibited exists to remove
superclass attributes from the subclass. This is obviously not possible to map
into the Java type system except using something like
complex type a
attribute blah type=int
complex type b
extension base a
attribute blah use=prohibited
ends up as
public class a { int blah; getBlah() {return blah}}
public class b { getBlah() {throw new IllegalAccessException(blah not
accessible in class b); }}
The semantic for a prohibited field that does not override a superclass field
is not defined. It might not be considered unreasonable to generate the
illegalaccessexception getter/setter pair or an abstract method if the class is
abstract.
I know I'm incorrectly viewing xml schema as defining a class inheritence
system here, but its a not unuseful way to look at it.
Peter
> WSDL2Java ignores fixed elements/attributes
> -------------------------------------------
>
> Key: AXIS-849
> URL: http://issues.apache.org/jira/browse/AXIS-849
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: 1.0-rc2
> Environment: Operating System: Other
> Platform: Other
> Reporter: Nikolay Metchev
> Assignee: Axis Developers Mailing List
>
> If in the types section of a wsdl document you specify a type which has an
> attribute/element that has a fixed value. The client code that gets generated
> does not enforce that by disallowing the setting of that attribute externally.
> On a similar note if a type has an element and an attribute with the same
> name
> then the generated code does not compile.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
