[JBoss JIRA] Created: (GTNPORTAL-1001) GateIn+Opera: problem with script
by Benjamin Seyinbour (JIRA)
GateIn+Opera: problem with script
---------------------------------
Key: GTNPORTAL-1001
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1001
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.0.0-GA
Environment: Linux [Centos 5.4] Opera[version:10.10) Java [version 1.6.0_16]
Reporter: Benjamin Seyinbour
Fix For: 3.0.0-GA
I keep getting the following error in Opera whenever I click a command button or link in GateIn :
<localhost>
[Error:
name: TypeError
message: Statement on line 221: Type mismatch (usually non-object value supplied where object required)
]
When this happens the top half of the screen turns black and I can't see GateIn .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (GTNPC-70) Behavioral change: New portlet metadata parser silently discards unexpected elements.
by Chris Laprun (JIRA)
Behavioral change: New portlet metadata parser silently discards unexpected elements.
-------------------------------------------------------------------------------------
Key: GTNPC-70
URL: https://issues.jboss.org/browse/GTNPC-70
Project: GateIn Portlet Container
Issue Type: Enhancement
Components: API, Documentation
Affects Versions: 2.3.0-Beta05
Reporter: Chris Laprun
Fix For: 2.3.0-GA
portlet.xml parsing was previously very tolerant with respect to out-of-order elements (XSD kinda sucks for this), thus silently allowing portlet.xml that were not strictly valid according to portlet-app_2_0.xsd. The new staxnav parser, on the other hand, is a lot stricter (while still not validating) meaning that it will silently discard unexpected (in particular, out-of-order) elements, resulting in portlet metadata that previously was imported, now being silently discarded. While this is not strictly a bug (after all, the portlet.xml that result in errors are invalid), this is a rather big behavioral change compounded with the fact that the new parser silently discards information resulting in errors showing up much later than the parsing process and without any informational context that the user could use to fix the issue... :(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months