Comments (12)
I located the tutorial project ECF's and got the same issue. The problem appears to be in the:
path: "[user_path]\EWF-0.3\library\server\wsf\default\nino-safe.ecf"
In the tutorial "hello" target, the error is the same:
Description Location Position
2 VD88: A class relies on another class with less strict void safety settings. Provider class: WSF_DEFAULT_RESPONSE_SERVICE. HELLO_APPLICATION (src) 17, 2
Error code: VD88
Configuration error: a class relies on another class with less strict void safety settings.
What to do: change void safety options so that ancestor or supplier provides higher or equal void safety.
Class: HELLO_APPLICATION
Other class: WSF_DEFAULT_RESPONSE_SERVICE
Line: 17
inherit
-> WSF_DEFAULT_RESPONSE_SERVICE
from ewf.
Hi,
Which version of EiffelStudio are you using ?
Do you use the version of EWF that comes bundled with EiffelStudio or the Git one ?
from ewf.
Indeed one need to apply a commit I made on the master to ensure all compile fine.
I am in vacation right now until end of July.
I may try to fix it when I find a computer but if Javier or Olivier could fix it this would help me.
For now either use eiffelstudio 7.3 with the EWF lib delivered with 7.3. Or use the master branch of EWF
from ewf.
Just realized I'm not part of the EiffelWebFramework Owners Team so I won't be able to fix it as I don't have the right to π
@jvelilla : can you fix it ?
from ewf.
Just to double check, we want to merge the release-03 branch with the master branch?
from ewf.
From what @jocelyn said, I think we can just cherry-pick commit 8040dd5 on the release-03 branch and release a new tag (something like v0.3.1)
from ewf.
Using v. 7.2, but curious to know what changes are in 7.3 that facilitate the EWF.
from ewf.
Quick reply
7.3 introduces the notion of complete void safety.
And I tried to have most of the ewf libs at this level. But this was
breaking the 7.2 compilation so I reverted some changes in the master
branch to support 7.2
But I forgot to apply this change to v0.3 because for me this was mainly
for Eiffel studio 7.3 and thus this was not an issue for 7.3 itself.
Hopefully Olivier and Javier corrected this since I am currently in
vacation.
I hope this is clear now = all my mistake.
Jocelyn
Le 15 juil. 2013 02:13, "Larry Rix" [email protected] a Γ©crit :
Using v. 7.2, but curious to know what changes are in 7.3 that facilitate
the EWF.β
Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-20947357
.
from ewf.
Thanks to Jocelyn, I'm now part of the EWF Owners Team π
I've updated the release-0.3 branch and also created a new tag v0.3.1.
@ljr1981 : can you update your local repository and try again ?
from ewf.
I will try today! :-) Thank you folks!
from ewf.
Larry, can you confirm this issue is fixed?
If not, please let use know
from ewf.
I am not entirely certain, but the issue seems to have been a confusion based on the different void-safety settings in 7.3 v. 7.2 and I was opening the project in 7.2. I had a similar issue with another project and then noted the differences in the void-safety settings. Having downloaded 7.3 GPL for my local laptop, there appears to be no issue. I think you can close this one out.
from ewf.
Related Issues (20)
- WebSocket Client HOT 1
- WebSocket Test HOT 1
- / as part of the value of a URI template variable results in handler not being found HOT 6
- WSF_REQUEST.percent_encoded_path_info does not work HOT 8
- WSF_REQUEST.save_uploaded_file: unsafe
- WSF_POST_HELPER does not support non-RESTful POSTs HOT 2
- gewf and autodetect which connector to use
- Consistency of Not Modified responses in WSF_METHOD_HELPER HOT 1
- Policy-driven framework should reject PUT requests that contain a Content-Range header HOT 1
- Add a last_modified routine to WSF_SKELETON_HANDLER HOT 1
- WSF_TRACE_RESPONSE does not include Content-Type header HOT 1
- Possible replacement for code 301 Moved permanently
- Use of 411 Length required response code HOT 2
- CORS headers for policy-driven framework HOT 2
- VARY header set to application/json rather than accept HOT 1
- Documentation error in {WSF_SKELETON_HANDLER}.check_request
- WSF_REQUEST.cookies_table does not terminate on cookies without a value. HOT 2
- Issues are WSF_RESPONSE.status_code/status_is_set
- Segmentation Fault on map_uri_template_agent_with_request_methods HOT 4
- JSON_PARSER.parse_string can exhaust memory HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ewf.