Skip to content
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.

No error check done on Policy elements (at least in security) #11

Closed
glassfishrobot opened this issue Oct 28, 2008 · 5 comments
Closed

Comments

@glassfishrobot
Copy link

I just wasted 15 minutes or so because I had the following in the WSDL:

<sc:ValidatorConfiguration wspp:visibility="private"
certificateValidator="test.ValidatorImpl" />

... whereas the system expected

<sc:ValidatorConfiguration wspp:visibility="private">
<sc:Validator wspp:visibility="private" name="certificateValidator"
classname="test.ValidatorImpl"/>
</sc:ValidatorConfiguration>

Users are supposed to make mistakes like this, and it's a tool's responsibility
to catch a problem and report an error. As an example, the JAXB RI reports any
such incorrect attribute on any schema elements.

This is made worse by issue #4, which would have otherwise helped me catch this
problem in IDE or other schema-aware XML editors.

"you are not supposed to edit WSDL manually" is not an excuse — NetBeans
doesn't provide UI for all these configurations.

Environment

Operating System: All
Platform: All

Affected Versions

[current]

@glassfishrobot
Copy link
Author

Reported by kohsuke@java.net

@glassfishrobot
Copy link
Author

Was assigned to snajper

@glassfishrobot
Copy link
Author

Marked as fixed on Friday, December 9th 2011, 1:55:23 am

@glassfishrobot
Copy link
Author

snajper said:
The error reporting was improved.

@glassfishrobot
Copy link
Author

This issue was imported from java.net JIRA METRO-11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant