Pages.xsd - Page element's scheme attribute use enum of http and https
----------------------------------------------------------------------
Key: JBSEAM-3387
URL: https://jira.jboss.org/jira/browse/JBSEAM-3387
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.BETA1
Environment: N/A
Reporter: Arron Ferguson
Priority: Optional
Currently the pages.xml file has the following page element's scheme attribute defined as:
<xs:attribute name="scheme"/>
Since the user will be using one of two protocols: http or https, the scheme attribute should have:
<xs:attribute name="scheme" default="false">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="http"/>
<xs:enumeration value="https"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
--
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
Seam GWT servlet should no longer use deprecated SerializableException
----------------------------------------------------------------------
Key: JBSEAM-3828
URL: https://jira.jboss.org/jira/browse/JBSEAM-3828
Project: Seam
Issue Type: Patch
Components: GWT
Reporter: Jan Vorwerk
Priority: Optional
Since GWT 1.5 the usage of SerializableException has been deprecated, while Seam Remoting servlet for GWT compells its usage as a base class for serializable exceptions to be marshalled from the server to the client.
See code in: org.jboss.seam.remoting.gwt.GWTService#processCall(String)
// Serialize the exception back to the client if it's a declared
// exception
if (cause instanceof SerializableException)
--
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