Per http://jira.jboss.com/jira/browse/JBAS-3208, this has been resolved.
Dimitris Andreadis wrote:
A couple of days ago Telrod modifed JBossRemoting to fix a dubious
warning in SerializationStreamFactory, and re-checked this in as jboss
remoting 1.4.2.GA
Now Bill, made some change in
catches
throwable and allows processing to continue (but is going to require
another remoting release).
Dimitris Andreadis wrote:
I meant actually used by remoting in this setup, sorry.
-Original Message-
From: Dimitris Andreadis
Sent: 04 May, 2006 23:34
To: Tom Elrod
Cc: Scott M
is
using it yet.
Does this make sense?
-Original Message-
From: Tom Elrod
Sent: 05 May, 2006 04:38
To: Dimitris Andreadis
Cc: Tom Elrod; Scott M Stark; Clebert Suconic; QA;
jboss-development@lists.sourceforge.net
Subject: Re: Problem with minimal config in Branch_4_0
Not really
- JBossRemoting, (a) the version number shouldn't be 1.4.2.GA ??.
Second, I don't see any dependency in its component-info.xml on
JBossRemoting ?
Don't understand what you mean by the second point.
---
Using Tomcat but need to do more?
Remoting changed to be 1.4.2.GA (as well as ws references)
Dimitris Andreadis wrote:
This is the current jboss project dependencies on JBoss 4.0.4.GA
componentref name=jboss/aop version=1.5.0-snapshot/
componentref name=jboss/backport-concurrent version=2.1.0.GA/
componentref name=jboss/cache
declared
-Original Message-
From: Tom Elrod
Sent: Thursday, May 04, 2006 9:34 AM
To: Dimitris Andreadis
Cc: Scott M Stark; Adrian Brock; Kabir Khan; Alexey Loubyansky; Thomas
Diesler; Tom Elrod; Clebert Suconic;
jboss-development@lists.sourceforge.net; QA
Subject: Re: JBAS 4.0.4.GA
, even if not configured by default, so a
possible version conflict with other components using a different
version of JBossSerialization can be detected.
-Original Message-
From: Tom Elrod
Sent: 04 May, 2006 21:39
To: Clebert Suconic
Cc: Tom Elrod; Dimitris Andreadis; Scott M Stark; Adrian
: 02 May, 2006 07:34
To: Clebert Suconic; Tom Elrod
Cc: Dimitris Andreadis; QA; 'jboss-development@lists.sourceforge.net'
Subject: RE: Problem with minimal config in Branch_4_0
Ok, this package already is in the jboss-minmal.jar
-Original Message-
From: Clebert Suconic
Sent: Monday, May 01
just
include the org.jboss.remoting.serialization package classes. These are
self container aren't they?
-Original Message-
From: Tom Elrod
Sent: Friday, April 28, 2006 8:47 AM
To: Dimitris Andreadis
Cc: QA; jboss-development@lists.sourceforge.net; Clebert
Suconic; Tom Elrod
Subject
The problem stems from NamingService using MarshalledInvocation, which
now requires org.jboss.remoting.serialization.IMarshalledValue and
org.jboss.remoting.serialization.SerializationStreamFactory (which is
found within jboss-remoting.jar).
However, jboss-remoting.jar is not included within
Running the all config from a clean check out and build is fine (at
least for booting). Running the testsuite does give an error when
booting the all configuration (during jboss-all-config-tests target),
but logs indicate is due to port 1098 already being in use. Saw the
same on the
.
Hany Mesha
On 4/5/06, *Tom Elrod* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Running the all config from a clean check out and build is fine (at
least for booting). Running the testsuite does give an error when
booting the all configuration (during jboss-all-config-tests target
I have updated the remoting road map to reflect what I want to deliver
within the next quarter -
http://jira.jboss.com/jira/secure/BrowseProject.jspa?id=10031subset=-1.
In short:
2.0.0 (Boon) - mainly stability and performance release with minor
features and bug fixes. estimated release mid
:
So jboss-remoting 2.0.0 could come with the next version of jboss-as
2.0.5, unless there are other dependencies.
Why not putting dates on the remoting releases?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: 04 April, 2006 17:04
Ok. I have rolled back to 1.4.0. The web services team can put back to
1.4.1 when they are ready.
Scott M Stark wrote:
Start doing a clean build before committing any changes to
build-thirdparty.xml to avoid this consistent problem:
[synchronizeinfo] Checking currentComponentRef:
I think this has to do with moving the IMarshalledValue out of common
and into remoting (which would be in the remoting 1.4.1 release). I
know Clebert was waiting on the upgrade to 1.4.1 to commit his changes
to 4.0 branch that reflected this change (am guess he made that commit?)
Scott M
I think jmx server uses (or at least used to use) gnu-regexp
Scott M Stark wrote:
Where are all of these thirdparty elements being used such that they are
specified here? In particular, what is using the * ones?
componentref name=antlr version=2.7.6rc1/
* componentref
@lists.sourceforge.net
Subject: RE: [JBoss-dev] Why isn't server building?
I didn't commit my changes. I was waiting the newer version of Remoting.
I will be looking into that now.
From: [EMAIL PROTECTED] on behalf of Tom Elrod
Sent: Tue 3/28/2006 8:51
for this
within the ejb3 project.
Ryan Campbell wrote:
Yes, this is Branch_4_0. Thanks, Tom.
-Original Message-
From: Tom Elrod
Sent: Tuesday, January 31, 2006 1:28 PM
To: Tom Elrod
Cc: Ryan Campbell; Tom Elrod; Kabir Khan; Bill Burke;
jboss-development@lists.sourceforge.net
Subject
JBoss Remoting 1.4.0 final was release late last week. I am finishing
up integrating this into JBossAS 4.0 branch and HEAD. The items of note
with this integration are:
4.0 branch HEAD
- Updated build-thirdpary.xml to use remoting 1.4.0_final from repository
- removed javax.servlet.jar
The class that is not being found is within jbossas-remoting.jar. This
is part of JBossAS code base and not remoting. Only way this would be
called to be loaded is if was configured to use the JBossAS security
domain via configuration. So am guessing the jar was excluded from the
build?
I think I get the mis-match now. This is being build out of JBoss 4.x
branch, right? If so, then the code for jbossas-remoting.jar is not
there. There is an issue for this (JBAS-2698), which I will work on today.
Tom Elrod wrote:
The class that is not being found is within jbossas
=0x8df3ba00 nid=0x4ec6
waiting on condition
*From:* Ryan Campbell
*Sent:* Monday, January 23, 2006 2:57 PM
*To:* Tom Elrod
*Cc:* QA
*Subject:* RE: jboss-remoting-testsuite-1.5 Build Completed With
Testsuite Errors
I
So how should the be addressed when using 1.4? I just added used of
Timer for client side leases within remoting.
Adrian Brock wrote:
1.5 added a java.util.Timer.purge()
I didn't realise Elias had changed TimeoutFactory to use a Timer.
He said he was just changing it so it can be used as
TaskJBAS-2604 Update the remoting version to a stable release
I'll have a 1.4.0 RC1 available for testing before tomorrow morning (if
no problems with this, will make the final next week).
---
This SF.net email is sponsored by:
This should be fixed now. Don't know if I made it in time for tonight's
build though.
Ryan Campbell wrote:
JRunit tests/config for remoting seem to be broken:
http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite/20050913121659/tests.log
[receiver] Caused by:
Scott M Stark wrote:
another package that needs to be broken out of jboss.jar is
org.jboss.invocation. There are dependencies on the remoting
implementation in the NamingService, HttpNamingContextFactory and the
naming proxy interceptors. This package should be in a
jboss-remoting-legacy.jar
Scott M Stark wrote:
... The only thing that has
been done as far as I know if removal of remoting from jboss-head to
introduce the binary.
Correct. I did two things.
1. Added remoting binary and changed the current builds to use the
library instead of the module.
2. Added new integration
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: Tuesday, May 10, 2005 8:58 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] creating jboss thirdparty directory
...
I think we are there. There is already a jbossas module
defined with nothing
The changes to make JBossRemoting a completely external project of
JBossAS is now complete. To get the changes, either do a clean checkout
of HEAD, or and update and then cvs checkout thirdparty/jboss from the
root jboss-head directory. This ONLY pertains to CVS HEAD (i.e.
jboss-head,
-4.0) to avoid breaking the build of existing
releases.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: Monday, May 09, 2005 1:34 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] creating jboss thirdparty directory
Since
:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: Tuesday, May 10, 2005 11:42 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] creating jboss thirdparty directory
I have the old build ready locally for both the jboss-head
and JBossRemoting. Now I need to change the CVSROOT
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: Tuesday, May 10, 2005 12:55 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] creating jboss thirdparty directory
So you want?
1. The jboss-head/remoting directory and its contents (which
now only contains
Since I am now doing all new development in the JBossRemoting module,
which is stand alone, I would like to make a few changes as to how
jboss-head picks up the remoting code.
First, I would like to make the remoting code visible to jboss-head as a
binary. For the old build, this means adding
[ http://jira.jboss.com/jira/browse/JBREM-101?page=history ]
Tom Elrod resolved JBREM-101:
--
Resolution: Done
Should be up to date and in sync with remoting release in JBossAS 4 series
(based on 4.0.1 and 4.0.2 release).
Fix serialization
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.1.0 beta
Need to fix the classes that will be passed over the wire so that they contain
serialVersionUID and versioning for Externalizable classes to allowed for
release version compatibility.
--
This message
[ http://jira.jboss.com/jira/browse/JBREM-86?page=history ]
Tom Elrod closed JBREM-86:
---
Resolution: Done
All methods implemented.
finish RMIJRMPServerImpl implementation
---
Key: JBREM-86
URL
[ http://jira.jboss.com/jira/browse/JBREM-78?page=comments#action_12316825
]
Tom Elrod commented on JBREM-78:
-
Finished all implementation besides notification handling, which needs to be
implemented throughout.
RMIConnector implementation
[ http://jira.jboss.com/jira/browse/JBREM-76?page=history ]
Tom Elrod closed JBREM-76:
---
Resolution: Done
This has been implemented throughout the RMI implementation (will need to add
into any new transport implementations).
Classloading support
[ http://jira.jboss.com/jira/browse/JBREM-74?page=comments#action_12316827
]
Tom Elrod commented on JBREM-74:
-
Pretty much all the other core calls have been implemented except the
notification handling. All the notification methods have been
[ http://jira.jboss.com/jira/browse/JBREM-93?page=comments#action_12316828
]
Tom Elrod commented on JBREM-93:
-
I don't think this is documented anywhere.
The real problem lies in that there can be many exceptions that are raised that
have nothing
[ http://jira.jboss.com/jira/browse/JBREM-96?page=comments#action_12316829
]
Tom Elrod commented on JBREM-96:
-
Standalone build working, but does not use new jboss build and is static, so
will have to change it often to keep up with the other jboss
[ http://jira.jboss.com/jira/browse/JBREM-95?page=comments#action_12316830
]
Tom Elrod commented on JBREM-95:
-
Is cleaned up as good as it can get for now, but will need to switch to jboss
build.
Need to clean up lib directory
Switch to jboss build
-
Key: JBREM-99
URL: http://jira.jboss.com/jira/browse/JBREM-99
Project: JBoss Remoting
Type: Sub-task
Reporter: Tom Elrod
Assigned to: Tom Elrod
--
This message is automatically generated by JIRA.
-
If you
Add remoting standalone to CVSROOT/modules
--
Key: JBREM-100
URL: http://jira.jboss.com/jira/browse/JBREM-100
Project: JBoss Remoting
Type: Sub-task
Reporter: Tom Elrod
Assigned to: Tom Elrod
--
This message
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.2.0 beta
--
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
-
If you want more information
[ http://jira.jboss.com/jira/browse/JBREM-98?page=history ]
Tom Elrod closed JBREM-98:
---
Resolution: Done
Either removed the isDebugEnabled() or changed to isTraceEnabled().
remove isDebugEnabled() within code as is now depricated
[ http://jira.jboss.com/jira/browse/JBREM-93?page=comments#action_12316700
]
Tom Elrod commented on JBREM-93:
-
It just wraps any Throwable thrown when calling
callBackClient.invoke(internalInvocation,callback.getRequestPayload()), so can
just get
[ http://jira.jboss.com/jira/browse/JBREM-97?page=history ]
Tom Elrod closed JBREM-97:
---
Resolution: Done
Changed so not using enum keyword for variable names. Everything else is fine.
Won't compile under JDK 1.5
Need to clean up lib directory
--
Key: JBREM-95
URL: http://jira.jboss.com/jira/browse/JBREM-95
Project: JBoss Remoting
Type: Sub-task
Components: general
Versions: 1.2.0 beta
Reporter: Tom Elrod
Assigned to: Tom Elrod
Get stand alone build working
-
Key: JBREM-96
URL: http://jira.jboss.com/jira/browse/JBREM-96
Project: JBoss Remoting
Type: Sub-task
Reporter: Tom Elrod
Assigned to: Tom Elrod
--
This message is automatically generated
[ http://jira.jboss.com/jira/browse/JBREM-43?page=history ]
Tom Elrod updated JBREM-43:
Priority: Critical (was: Major)
custom socket factories
---
Key: JBREM-43
URL: http://jira.jboss.com/jira/browse/JBREM-43
Elrod
Assigned to: Tom Elrod
Fix For: 1.2.0 beta
Since it is possible to have a callback server that never receives direct
invocations and only callbacks, there is no need for the requirement to have a
handler registered for the server (since will never be called upon).
Therefore, need
[ http://jira.jboss.com/jira/browse/JBREM-36?page=history ]
Tom Elrod updated JBREM-36:
Fix Version: 1.0.2 final
(was: 1.2.0 beta)
performance tests fail for http transports
--
Key
[ http://jira.jboss.com/jira/browse/JBREM-36?page=history ]
Tom Elrod resolved JBREM-36:
-
Resolution: Done
Fixed. Tests passing for standard and oneway invocations using the http
invoker.
performance tests fail for http transports
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.2.0 beta
Need transport that will allow for calling back from the server to the client
using the same socket. This will allow for async callbacks to clients that
will not allow outside connections. This is basically the same
: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.2.0 beta
Need ability to provide more information in the Detection message about the
server invoker's handlers. Should include subsystem and other metadata that
the handler supplies. This would then be included in the NetworkNotification
[ http://jira.jboss.com/jira/browse/JBREM-83?page=history ]
Tom Elrod updated JBREM-83:
Fix Version: 1.0.2 final
(was: 1.2.0 beta)
Updated Invocation marshalling to support standard payloads
[ http://jira.jboss.com/jira/browse/JBREM-66?page=history ]
Tom Elrod updated JBREM-66:
Fix Version: 1.0.2 final
(was: 1.2.0 beta)
Race condition on startup
-
Key: JBREM-66
URL: http
[ http://jira.jboss.com/jira/browse/JBREM-70?page=history ]
Tom Elrod updated JBREM-70:
Fix Version: 1.0.2 final
(was: 1.2.0 beta)
Clean up build.xml. Fix .classpath and .project for eclipse
[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod resolved JBREM-82:
-
Resolution: Done
Moved from 1.2.0 beta to 1.0.2 final release.
Bad warning in Connector.
-
Key: JBREM-82
URL
[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod reopened JBREM-82:
-
Reopening to move to 1.0.2 release.
Bad warning in Connector.
-
Key: JBREM-82
URL: http://jira.jboss.com/jira/browse
[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod updated JBREM-82:
Fix Version: 1.0.2 final
(was: 1.2.0 beta)
Bad warning in Connector.
-
Key: JBREM-82
URL: http
HTTP invoker only binds to localhost
Key: JBREM-88
URL: http://jira.jboss.com/jira/browse/JBREM-88
Project: JBoss Remoting
Type: Bug
Components: transport
Versions: 1.0.1 final
Reporter: Tom Elrod
Assigned
: 1.0.1 final
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.0.2 final
The HTTPServerInvoker was not picking up the headers properly and putting into
the metadata map being passed to both the unmarshaller and the handler. The
value in the metadata was actually the header
[ http://jira.jboss.com/jira/browse/JBREM-88?page=history ]
Tom Elrod resolved JBREM-88:
-
Resolution: Done
Have fixed so will use the host specified by the locator url to bind to.
HTTP invoker only binds to localhost
[ http://jira.jboss.com/jira/browse/JBREM-89?page=history ]
Tom Elrod resolved JBREM-89:
-
Resolution: Done
Fixed by taking the content-length value from the header (via metadata passed)
to figure out what the total amount read should
[ http://jira.jboss.com/jira/browse/JBREM-90?page=history ]
Tom Elrod resolved JBREM-90:
-
Resolution: Done
Fixed so will get the header value instead of the header name for the value of
the metadata map.
HTTP header values not being picked up
implement RMI IIOP
--
Key: JBREM-85
URL: http://jira.jboss.com/jira/browse/JBREM-85
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix
Elrod
Assigned to: Tom Elrod
Fix For: JMX Remoting 1.0.1
A few methods yet to be implemented.
--
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
-
If you want
final
Reporter: Tom Elrod
Assigned to: Tom Elrod
Priority: Critical
Fix For: 1.2.0 beta
Need to update InvocationMarshaller/InvocationUnMarshaller so that if payload
not org.jboss.Invocation or org.jboss.MarshalledInvocation, will just
marshall/unmarshaller using default parent
[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod closed JBREM-82:
---
Resolution: Done
Fix Version: 1.2.0 beta
Have updated the ObjectName generated for the server invoker to be unique to
the locator uri so that if a new server
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: 1.2.0 beta
if shutdown a connector that is using the same server invoker as another
connector, will be shutting down the server invoker underneath the other
connector (without warning or notification).
--
This message is automatically
[ http://jira.jboss.com/jira/browse/JBREM-83?page=history ]
Tom Elrod resolved JBREM-83:
-
Resolution: Done
Updated the InvocationMarshaller so will allow for non org.jboss.Invocation
payloads. Should be able to send any Serialiable payloads
[ http://jira.jboss.com/jira/browse/JBREM-8?page=history ]
Tom Elrod updated JBREM-8:
---
Priority: Major (was: Minor)
Ability to stream files via remoting
Key: JBREM-8
URL: http://jira.jboss.com/jira
: Tom Elrod
Assigned to: Tom Elrod
Priority: Optional
Per javadoc for JMXConnectorFactory:
An implementation may choose to find providers by other means. For example, it
may support the JAR conventions for service providers, where the service
interface is JMXConnectorProvider
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix For: JMX Remoting 1.0.1
Per spec, Every implementation must support the RMI connector protocols,
specified with the string rmi or iiop.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one
JMXMP connector implementation
--
Key: JBREM-73
URL: http://jira.jboss.com/jira/browse/JBREM-73
Project: JBoss Remoting
Type: Feature Request
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Notification support
Key: JBREM-74
URL: http://jira.jboss.com/jira/browse/JBREM-74
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix
[ http://jira.jboss.com/jira/browse/JBREM-73?page=history ]
Tom Elrod updated JBREM-73:
Original Estimate: 288000
Remaining Estimate: 288000
JMXMP connector implementation
--
Key: JBREM-73
URL: http
Termination detection
-
Key: JBREM-75
URL: http://jira.jboss.com/jira/browse/JBREM-75
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix
Connector server security
-
Key: JBREM-77
URL: http://jira.jboss.com/jira/browse/JBREM-77
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Classloading support
Key: JBREM-76
URL: http://jira.jboss.com/jira/browse/JBREM-76
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix
RMIConnector implementation
---
Key: JBREM-78
URL: http://jira.jboss.com/jira/browse/JBREM-78
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom
Generic connector implementation
Key: JBREM-79
URL: http://jira.jboss.com/jira/browse/JBREM-79
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned
JNDI discovery
--
Key: JBREM-80
URL: http://jira.jboss.com/jira/browse/JBREM-80
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Priority: Minor
Remoting discovery
--
Key: JBREM-81
URL: http://jira.jboss.com/jira/browse/JBREM-81
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Versions: JMX Remoting 1.0.1
Reporter: Tom Elrod
Assigned to: Tom Elrod
Fix
[ http://jira.jboss.com/jira/browse/JBREM-72?page=history ]
Tom Elrod resolved JBREM-72:
-
Resolution: Done
Implement provider for rmi and iiop protocols
-
Key: JBREM-72
URL: http
[ http://jira.jboss.com/jira/browse/JBREM-69?page=history ]
Tom Elrod closed JBREM-69:
---
Resolution: Done
Implementation finished and should be compliant. As for default protocol, am
asking jsr 255 group to clarify (but think indirectly means have
[ http://jira.jboss.com/jira/browse/JBREM-70?page=comments#action_12316043
]
Tom Elrod commented on JBREM-70:
-
Nope. I have removed them and checked in a new build.xml.
Clean up build.xml. Fix .classpath and .project for eclipse
[ http://jira.jboss.com/jira/browse/JBREM-70?page=history ]
Tom Elrod updated JBREM-70:
Version: 1.0.1 final
Fix Version: 1.2.0 beta
Clean up build.xml. Fix .classpath and .project for eclipse
Implement JMXServiceURl
---
Key: JBREM-69
URL: http://jira.jboss.com/jira/browse/JBREM-69
Project: JBoss Remoting
Type: Task
Components: jmx remoting
Reporter: Tom Elrod
Assigned to: Tom Elrod
Priority: Critical
Fix For: JMX
[ http://jira.jboss.com/jira/browse/JBREM-69?page=history ]
Tom Elrod updated JBREM-69:
Description:
Per spec, need following requirements met:
- prefix of service:jmx:;
- string of one or more ASCII characters, each of which is a letter, a digit,
or one
[ http://jira.jboss.com/jira/browse/JBREM-69?page=comments#action_12316009
]
Tom Elrod commented on JBREM-69:
-
Implementation pretty much done. Only remaining issues are:
- is jmxmp required default by spec for the protocol?
- what is the default
Add persistent store for oneway messages
Key: JBREM-68
URL: http://jira.jboss.com/jira/browse/JBREM-68
Project: JBoss Remoting
Type: Task
Components: transport
Versions: 1.0.1 final
Reporter: Tom Elrod
[ http://jira.jboss.com/jira/browse/JBREM-42?page=comments#action_12315952
]
Tom Elrod commented on JBREM-42:
-
Need to add API in the ServerInvocationHandler to get the classloader the
handler wishes the server invoker to use for classloading
[ http://jira.jboss.com/jira/browse/JBREM-47?page=history ]
Tom Elrod updated JBREM-47:
Fix Version: 1.2.0 beta
Dynamic classloading
Key: JBREM-47
URL: http://jira.jboss.com/jira/browse/JBREM-47
Project
[ http://jira.jboss.com/jira/browse/JBREM-55?page=history ]
Tom Elrod updated JBREM-55:
Fix Version: 1.2.0 beta
Clean up Callback implementation
Key: JBREM-55
URL: http://jira.jboss.com/jira/browse
[ http://jira.jboss.com/jira/browse/JBREM-57?page=history ]
Tom Elrod updated JBREM-57:
Fix Version: 1.2.0 beta
Remove use of InvokerRequest in favor of Callback object
Key: JBREM-57
[ http://jira.jboss.com/jira/browse/JBREM-44?page=history ]
Tom Elrod updated JBREM-44:
Fix Version: 1.2.0 beta
HA support for unified invoker
--
Key: JBREM-44
URL: http://jira.jboss.com/jira/browse/JBREM
1 - 100 of 252 matches
Mail list logo
