[JBoss JIRA] Created: (JBOSGI-12) OSGi testsuite
by Ales Justin (JIRA)
OSGi testsuite
--------------
Key: JBOSGI-12
URL: http://jira.jboss.com/jira/browse/JBOSGI-12
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Reporter: Ales Justin
Assigned To: Kevin Conner
We need tests for our new [OSGi] Classloader layer and OSGi API facade - 'measuring' our OSGi compliance.
Tests should also cover back compatibility with existing UCL:
- import *
- export *
- import not local
- import not system [filter]
- hierarchical dependency graph
- translator
- replace system classloader
- unit testing classloader
- management console classloader
- proper EE client application exposure
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBBUILD-472) Maven JBoss Retro-produced jar has full paths
by Justin Edelson (JIRA)
Maven JBoss Retro-produced jar has full paths
---------------------------------------------
Key: JBBUILD-472
URL: http://jira.jboss.com/jira/browse/JBBUILD-472
Project: JBoss Build System
Issue Type: Bug
Components: maven-jboss-retro-plugin
Affects Versions: jboss-retro-maven-plugin-0.5.GA
Environment: Win XP. Fine on Linux
Reporter: Justin Edelson
Priority: Critical
I have a project that uses the jboss-retro-maven-plugin to produce a 1.4-compatible JAR. When I run my build on a Windows PC (XP SP2), the generated JAR has the full path in each entry:
C:\home\devel\CoreLib\target>jar -tf CoreLib-jdk14.jar
META-INF/MANIFEST.MF
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\exceptions\UCSARuntimeException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\Context$ScopeMap.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\Context.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\GlobalIdException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\InternalException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\ParseException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\ResolverException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\IdElement.class
...
I suspect there is an easy fix for this, presuambly just a hardcoded "/" instead of getting the file separator.
--
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
15 years, 11 months
[JBoss JIRA] Created: (JGRP-430) Support accessing multiple GossipRouters in TUNNEL
by Bela Ban (JIRA)
Support accessing multiple GossipRouters in TUNNEL
--------------------------------------------------
Key: JGRP-430
URL: http://jira.jboss.com/jira/browse/JGRP-430
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.5
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
Multiple GossipRouters can only be used for lookups, not for routing... However, since all traffic to the GR goes out via TUNNEL (as JGroups transport), and TUNNEL uses a RouterStub to send a message to the GR, we could do the following:
* the RouterStub is currently configured with the address of *one* GR
* a Stub.send() succeeds in connecting to the GR and sending the
message, or goes into a state where it tries to reconnect *forever*
* I could simply change that to configure the RouterStub with
multiple GRs:
o for send(), we iterate through the GRs until send() returns
true
EFFECT: a GossipRouter is not a single point of failure any longer
--
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
15 years, 11 months