March 2008 - jboss-jira - Jboss List Archives

[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

2
4
0 / 0

[JBoss JIRA] Created: (JBXB-132) Update JBossXB 2.0.0.CR7 to use Xerces 2.9.1

by Adrian Brock (JIRA)

Update JBossXB 2.0.0.CR7 to use Xerces 2.9.1 -------------------------------------------- Key: JBXB-132 URL: http://jira.jboss.com/jira/browse/JBXB-132 Project: JBoss XML Binding (JBossXB) Issue Type: Sub-task Reporter: Adrian Brock Assigned To: Alexey Loubyansky Fix For: JBossXB-2.0.0.CR7 Update Xerces to 2.9.1 to fix a schema parsing bug -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-3) Release JBoss Man 2.0.0.Beta11

by Adrian Brock (JIRA)

Release JBoss Man 2.0.0.Beta11 ------------------------------ Key: JBMAN-3 URL: http://jira.jboss.com/jira/browse/JBMAN-3 Project: JBoss Managed Issue Type: Task Components: release Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMan.2.0.0.CR1 Make a release of jboss managed 2.0.0.Beta11 -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-252) Create TemplateFactory to keep ManagedComponent and Template properties in sync

by Scott M Stark (JIRA)

Create TemplateFactory to keep ManagedComponent and Template properties in sync ------------------------------------------------------------------------------- Key: JBMICROCONT-252 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-252 Project: JBoss MicroContainer Issue Type: Feature Request Components: Management Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC-2.0.0.CR1 We need a template factory plugin the builds the DeploymentTemplateInfo from the MangedObject properties annotated with a ManagementProperty(includeInTemplate=true) -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-238) Add MapCompositeMetaType support

by Scott M Stark (JIRA)

Add MapCompositeMetaType support -------------------------------- Key: JBMICROCONT-238 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-238 Project: JBoss MicroContainer Issue Type: Task Components: Metatype Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC-2.0.0.CR1 Right now MetaTypeFactory.resolve(Map[String,?].class) returns a TableMetaType. It seems more natural for this to be a CompositeMetaType that does not restrict the item names when the Map has String keys. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-239) @interface ManagementProperty needs an includeInTemplate flag

by Scott M Stark (JIRA)

@interface ManagementProperty needs an includeInTemplate flag ------------------------------------------------------------- Key: JBMICROCONT-239 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-239 Project: JBoss MicroContainer Issue Type: Feature Request Components: Management Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC-2.0.0.CR1 Right now the properties that go into a deployment template are created independent of the ManagedObject for the deployment attachment metadata. This is duplicate work and leads to the template getting out of date. We need an includeInTemplate in the ManagementProperty annotation. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-198) jboss-kernel and jboss-aop-mc-int have compile dependencies on jboss-test and junit

by Elias Ross (JIRA)

jboss-kernel and jboss-aop-mc-int have compile dependencies on jboss-test and junit ----------------------------------------------------------------------------------- Key: JBMICROCONT-198 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-198 Project: JBoss MicroContainer Issue Type: Task Reporter: Elias Ross jboss-test (and its dependencies) and junit are pulled into projects that depend on "jboss-kernel" and "jboss-aop-mc-int" because the project contains child classes of TestCase within src/main/java ... Probably the best way to deal with this is to create a separate jboss-kernel-test and mc-int-test artifacts. These dependencies pull in: junit\junit\4.1\junit-4.1.jar jboss\profiler\jvmti\jboss-profiler-jvmti\1.0.0.CR5\jboss-profiler-jvmti-1.0.0.CR5.jar jboss\jboss-test\1.0.4-SNAPSHOT\jboss-test-1.0.4-SNAPSHOT.jar which aren't relevant to people's runtime. -- 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

2
4
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-926) CLONE -add remoting based chat sample

by wang weifeng (JIRA)

CLONE -add remoting based chat sample ------------------------------------- Key: JBREM-926 URL: http://jira.jboss.com/jira/browse/JBREM-926 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Reporter: wang weifeng Assigned To: Ron Sigal Priority: Optional Fix For: 2.4.1.Beta Add a simple chat application using remoting for the communication layer to the remoting samples. -- 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

1
1
0 / 0

[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

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008