On Tue, 2005-09-13 at 17:15, Scott M Stark wrote:
> Looks like a typo I cannot error correct. Why wouldn't/couldn't the
> NonSerializableFactory be used with a standalone tomcat jndi?
>
e.g. NonSerializableFactory won't work with Tomcat JNDI
Tomcat's JNDI is read-only so the bind() will fail.
>
The har deployer is gone and the SAR deployer now handles .har too
(in any case .har really contained a jboss-service.xml descriptor)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, September 14, 2005 12:14
Ok, then any existing use of these utilities is a flag for either
non-portability, or there is a dependency on a root writable Context
that has to be provided differently depending on what context the mc is
used.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] O
A legacy build howto page is needed for the older tagged releases. I'll
look at creating it an linking it into the JBossBuild page.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, September 13, 2005 2:14 PM
> To
That seems ill-advised.
Dimitris Andreadis wrote:
The har deployer is gone and the SAR deployer now handles .har too
(in any case .har really contained a jboss-service.xml descriptor)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED
There still is a har deployer, its the sar deployer.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, September 13, 2005 3:00 PM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] 4.0 build
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.4?log=log20050913192451
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:178: Tests failed due to some errors or failures.Date of build: 09/13/2005 19:24:51Time to build
Anyone entertains the idea of making Clustering a top level project,
e.g., as a standalone release?
It can contain: tomcat clustering (standalone and embeded), HA-jndi
(standalone and embeded), DRM (or a version of distributed RPC),
HA-Remoting, ejb3 clustering, etc. Of course, all the integrtion
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 o
The classes I mentioned are the legacy remoting implementation. They
should be factored out of jboss.jar to further reduce dependencies on
it.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Tom Elrod
> Sent: Tuesday, September 13, 2005 9:39 PM
>
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: java.io.F
11 matches
Mail list logo
