[JBoss JIRA] Created: (JBMETA-5) jboss-metadata.jar needs refresh of schema/web-app_2_4.xsd
by Darryl Miles (JIRA)
jboss-metadata.jar needs refresh of schema/web-app_2_4.xsd
----------------------------------------------------------
Key: JBMETA-5
URL: http://jira.jboss.com/jira/browse/JBMETA-5
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Darryl Miles
Assigned To: Alexey Loubyansky
The main concern is that the regex for validating:
<mime-mapping>
<extension>xhtml</extension>
<mime-type>application/xhtml+xml</mime-type>
</mime-mapping>
The "+" character is not allowed by the older regex but its valid for a MIME type and at this time with the default out-the-box configuration of JBoss 5 any web-app using the above mime-mapping can not be deployed as the parser validates the XSD.
Is incorrect, Sun fixed their XSD sometime ago now to change:
--- web-app_2_4.xsd 2008-03-02 00:49:56.000000000
+0000
+++ ../web-app_2_4.xsd 2007-12-18 09:05:06.000000000 +0000
@@ -805,7 +798,7 @@
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:pattern value="[\p{L}\-\p{Nd}]+/[\p{L}\-\p{Nd}\.]+"/>
+ <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
See also Tomcat 6 Bugzilla entry: https://issues.apache.org/bugzilla/show_bug.cgi?id=44517
Also Sun have released a newer schema/web-app_2_5.xsd maybe that should be updated too, but the regex in the currently shipped one is okay with regards to this regex but I'm sure there have been other changes as bug in the original web-app_2_5.xsd have been worked out for the new 2.5 technology.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Updated: (JBREM-167) RMI Invoker does not use true remoting marshalling/unmarshalling
by Ron Sigal (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-167?page=all ]
Ron Sigal updated JBREM-167:
----------------------------
Assignee: Ron Sigal
> RMI Invoker does not use true remoting marshalling/unmarshalling
> ----------------------------------------------------------------
>
> Key: JBREM-167
> URL: http://jira.jboss.com/jira/browse/JBREM-167
> Project: JBoss Remoting
> Issue Type: Bug
> Components: transport
> Affects Versions: 1.2.0 final
> Reporter: Tom Elrod
> Assigned To: Ron Sigal
> Priority: Minor
> Fix For: 2.4.0.CR1 (Pinto)
>
>
> In process of fixing JBREM-165 (RMI support for UnifiedInvoker), have added ability to call on mashaller when making request so that can modify payload before sending. Although the RMIInvokerClient does use the configured marshaller, it does not use the configured unmarshaller (RMIInvokerServer is the opposite). This was done to get JBREM-165 working, but is not a total solution and needs to be fixed so anyone can add a marshaller/unmarshaller for RMI invoker that will be called both ways (in and out) on both the client and server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Created: (JBREM-924) Compilation errors in non ISO-8859-1 systems
by Trustin Lee (JIRA)
Compilation errors in non ISO-8859-1 systems
--------------------------------------------
Key: JBREM-924
URL: http://jira.jboss.com/jira/browse/JBREM-924
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Environment: Fedora 8, LANG=ko_KR.UTF-8
Reporter: Trustin Lee
Priority: Trivial
Fix For: 2.4.0.Beta2 (Pinto)
Attachments: remoting2-encoding.diff
The default encoding of my machine is UTF-8, but it seems like Remoting 2 trunk source code is encoded in ISO-8859-1. When I run 'ant tests', it bails out with a compilation error that there's a unmappable character in the source code. The solution of this problem is to specify the encoding of the source code explicitly in the build script and the IDE settings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months