Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Input/Output Schema/Encoding null #12

Open
dalcacer opened this issue Sep 17, 2014 · 1 comment
Open

Input/Output Schema/Encoding null #12

dalcacer opened this issue Sep 17, 2014 · 1 comment
Labels
bug wontfix
Milestone
v2.0

Comments

@dalcacer
Copy link
Member

If not set, schemas and encodings need to be null.
Otherwise the sever can't deal with created ProcessDescriptions.
@dalcacer dalcacer added the bug label Sep 17, 2014
@dalcacer dalcacer added this to the v2 milestone Sep 17, 2014
dalcacer pushed a commit that referenced this issue Sep 18, 2014
Added workaround for server-side emptystring/null. Refs #12.
1ca8197
@dalcacer
Copy link
Member Author

For now a workaround has been implemented. However a rollback and a bugfix within the server or the wps-client-lib is recommended.

//CC @romanwoessner

johannesfaltin pushed a commit to richwps/commons that referenced this issue Jan 9, 2015
Adapted TestProcessRequestBuilder due to issue richwps/modelbuilder#12.…
6521de2 
… Empty encoding or schema of Input are now replaced with null.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug wontfix
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
1 participant
@dalcacer