[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
17 years, 6 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
17 years, 6 months
[JBoss JIRA] Created: (JBXB-131) Update JBossXB 2.0.0.CR7 to use JBoss Common Core 2.2.3.GA
by Adrian Brock (JIRA)
Update JBossXB 2.0.0.CR7 to use JBoss Common Core 2.2.3.GA
----------------------------------------------------------
Key: JBXB-131
URL: http://jira.jboss.com/jira/browse/JBXB-131
Project: JBoss XML Binding (JBossXB)
Issue Type: Sub-task
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossXB-2.0.0.CR7
Update to latest version of jboss-common-core
and exclude things that are optional or override explicit versions in JBossXB's pom.
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-common-core</artifactId>
<version>2.2.3.GA</version>
<exclusions>
<exclusion>
<groupId>jboss</groupId>
<artifactId>jboss-common-logging-spi</artifactId>
</exclusion>
<exclusion>
<groupId>apache-httpclient</groupId>
<artifactId>commons-httpclient</artifactId>
</exclusion>
<exclusion>
<groupId>apache-slide</groupId>
<artifactId>webdavlib</artifactId>
</exclusion>
<exclusion>
<groupId>apache-xerces</groupId>
<artifactId>xml-apis</artifactId>
</exclusion>
</exclusions>
</dependency>
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBCACHE-1288) Handling of default eviction region config leads to duplicates
by Brian Stansberry (JIRA)
Handling of default eviction region config leads to duplicates
--------------------------------------------------------------
Key: JBCACHE-1288
URL: http://jira.jboss.com/jira/browse/JBCACHE-1288
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Eviction
Affects Versions: 2.1.0.CR3
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.1.0.CR4
The way the EvictionConfig.getEvictionRegionConfigs() method works leads to duplicate entries for the _default_ region when the JBoss Microcontainer builds up a configuration.
Problem is when there is no list of ERCs, the method builds one with a config for the _default_ region in it, and returns that. The MC will call this method, and then try to add xml-configured ERCs to the returned list. If a _default_ region is configured in XML, the _default_ region will end up being in the resulting list twice.
Test org.jboss.cache.config.EvictionRegionConfigurationTest.testDuplicateDefaultRegion() shows the issue.
I think the core problem here is that the attempt to add a default region is being done in the wrong place. It's not really the concern of the EvictionConfig class. I think it properly belongs in RegionManager.setEvictionConfig() -- that's the class that's responsible for checking the configuration and making it conform to its requirements.
I've got a patch along the above lines.
--
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
17 years, 6 months