Easy-WSDL

Provider cross-file helpers

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: New
Resolution: Unresolved
Affects Version/s: 2.3
Fix Version/s: None
Component/s: None
Security Level: Public

Description:

Hide

I have just tested EasyWSDL 3.0 40M1.
The basic API is fine. However, parsing seems to be limited to one file. Imports are not taken into account.
It would be very convenient to have helpers that cross boundaries.

Static methods could be fine.
Or there could be a SuperDefinition class, built from a Definition instance, and which would also include imported parts.
No matter how it is done, as long as it is available for end users.

This API should also work with the write mode.
It means we should be able to push modifications back to the file system in the respected files (in case of ambiguity, the library could make a default choice, and might also provide a method to let the user choose).

Show
I have just tested EasyWSDL 3.0 40M1. The basic API is fine. However, parsing seems to be limited to one file. Imports are not taken into account. It would be very convenient to have helpers that cross boundaries. Static methods could be fine. Or there could be a SuperDefinition class, built from a Definition instance, and which would also include imported parts. No matter how it is done, as long as it is available for end users. This API should also work with the write mode. It means we should be able to push modifications back to the file system in the respected files (in case of ambiguity, the library could make a default choice, and might also provide a method to let the user choose).

Environment:

Windows 7, JDK 6

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

mjambert added a comment - Thu, 15 Dec 2011 - 10:54:17 +0100

I do not understand when you say "parsing seems to be limited to one file". Actually, imports are taken into accounts.
Saying that the API should work in write mode respecting imports layout is far from being always possible. Anyway, the use case for that is obscure, and the way you propose to solve ambiguity (provide a method to let the user choose) is out of library scope to my mind.

Show

mjambert added a comment - Thu, 15 Dec 2011 - 10:54:17 +0100

I do not understand when you say "parsing seems to be limited to one file". Actually, imports are taken into accounts.
Saying that the API should work in write mode respecting imports layout is far from being always possible. Anyway, the use case for that is obscure, and the way you propose to solve ambiguity (provide a method to let the user choose) is out of library scope to my mind.

People

Assignee:

mjambert

Reporter:

Vincent Zurczak
Watchers:

0

Dates

Created:

Tue, 4 Oct 2011 - 18:43:34 +0200

Updated:

Mon, 9 Jan 2012 - 11:07:49 +0100