Id: | d1e120 |
---|
Severity: | Critical |
---|
Title: |
Validator / session threads get into a messy state when users browse among democases
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
When the user browses back and forth between democases, all
sorts of strange things happen to the session state.
That is not good for confidence.
An immediate solution is to ask users to shut down their browser
between each democase. A better solution hopefully is found.
|
|
Id: | d1e248 |
---|
Severity: | High |
---|
Title: |
What ever happened to schema validation...
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
... of the provided XSLT stylesheets and schemas?
If enabling it right now (ModelConfiguration.java), XSLV goes dead in some mysterious way.
|
|
Id: | d1e269 |
---|
Severity: | High |
---|
Title: |
Validation dies in some large cases
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
Validation terminates in some funny way with for example the dsd2xhtml case, without a result.
Is that really a feature (time out)?
|
|
Id: | d1e3 |
---|
Severity: | Medium |
---|
Title: |
Too many template conflict / competition messages
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: | |
---|
There are too many messages about competition between templates.
Each competing pair is reported twice (x with y and y with z)Competing pairs that are a consequence of stylesheet simplification (does that exist??) should not be reported.
A proper fix requires a better framework for competition analysis
than just logging each case as it is discovered.
| |
|
Id: | d1e162 |
---|
Severity: | Medium |
---|
Title: |
Gateway timeout message
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
When a large / heavy validation case is run, the
BRICS apache server comes up with some kind of gateway
timeout message, even though the validator is still running.
Could the server timeout be extended?
|
|
Id: | d1e78 |
---|
Severity: | Low |
---|
Title: |
Too many options appear in input schema diagnostics view
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
After clicking update in the input diagnostics view, FOUR checkboxes
appear. The three of them are irrelevant and should not appear.
|
|
Id: | d1e206 |
---|
Severity: | Low |
---|
Title: |
The enabled=true/false attribute in the triple element should be respected
in the on-line democase code
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
Instead of having to edit jsp's to enable or disable demo cases,
the already existing enabled attribute on the triple.xml's triple
element should be used.
|
|
Id: | d1e227 |
---|
Severity: | Low |
---|
Title: |
Schematools could use some kind of settable resolution context...
|
---|
Status: | Open |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
...for pulling in included or imported resources referred by URIs in another way than just resolving the URI.
Without that, includes in xsds won't work so well.
|
|
Id: | d1e33 |
---|
Severity: | High |
---|
Title: |
Does NS URI work for DTD?
|
---|
Status: | Closed |
---|
Reproducability: |
ObservedIncident
|
---|
Environment: | |
---|
In the purchaseorder2invoice democase, try using the DTD instead of the RNG on the output side.
Specify the correct namespace URI, 'invoice'.
The validator seems not to get the namespace right.
| Research Log: |
Date: It might have been the radio button gone forgotten. The value comes through OK _when_ the
radio button is selected. |
|
|
Id: | d1e57 |
---|
Severity: | Medium |
---|
Title: |
JS bugs in BRICS production - edit page
|
---|
Status: | Closed |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
MSIE 6
|
---|
The line and column number computation or display JS on the edit pages does not work.
Seems OK in Mozilla.
|
|
Id: | d1e183 |
---|
Severity: | Medium |
---|
Title: |
Output schema root element for XSD must be manually
inputtable also when using Schematools-style output
schema construction
|
---|
Status: | Closed |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
The format of the output schema root element name (given by the user / environment)
is different in Schematools from in the XSLV: Schematools uses
Clark form, while the dongfang stuff uses plain names.
A feature must be provided for the user to give a root element name
manually when Schematools constructs the output schema (see .......).
Right now that is only possible when the output schema is constructed
in the dongfang identity-transform-input way.
|
|
Id: | d1e99 |
---|
Severity: | Low |
---|
Title: |
Download of input schema diagnostics fails
|
---|
Status: | Closed |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
Clicking download in the input schema diagnostics causes a JSP exception.
org.apache.jasper.JasperException: /XMLDownload.jspx(7,77) According to TLD or attribute directive in tag file, attribute items does not accept any expressions
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
|
|
Id: | d1e141 |
---|
Severity: | Low |
---|
Title: |
Missing JS auto-selection of string input radio button
|
---|
Status: | Closed |
---|
Reproducability: |
Reproduceable
|
---|
Environment: |
Any
|
---|
When a stylesheet module or a schema is uploaded, there is JS functionality
that automatically switches to the BrowseFile / URL / TEXT input type
used by the user.
This functionality is missing for text inputs (namespace URI and root
element name).
|
|