JNDIView should not depend on anything other than the
naming serivce. It needs a mechanism to query for the
ObjectNames of the deployers from which it attempts
to obtain the deployed application info from, or this
needs to be available in a different manner.
- Original Message -
From:
We need to get away from usernames and passwords in the config
files. I'm thinking the resource adapators should be associated with
a security domain the same as ejbs and web content. A security
domain is an MBean(org.jboss.security.plugins.JaasSecurityDomain in
security)
and an
Hello Scott,
But where on SF do you have a synthetized list of recent CVS commits? The
site simply says, in the CVS section, No CVS History Available.
Cheers,
Sacha
Seperate them as they can be merged by any decent mail client
if desired. Do we really need
That is true and it seems that SF will not be implementing the
cvs history feature.
But where on SF do you have a synthetized list of recent CVS commits? The
site simply says, in the CVS section, No CVS History Available.
Cheers,
Sacha
Seperate them as they can be merged by any
User: slaboure
Date: 02/01/06 03:45:46
Modified:.build.xml
Log:
Now compiles the clustered HttpSession and creates .jar and .sar. THEY HAVE NOT YET
BEEN TESTED!
Revision ChangesPath
1.21 +50 -16jbossmx/build.xml
Index: build.xml
User: slaboure
Date: 02/01/06 03:46:18
jbossmx/src/resources/ClusteredHTTPSessionService - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: slaboure
Date: 02/01/06 03:46:57
Modified:src/resources/ClusteredHTTPSessionBean/META-INF ejb-jar.xml
jboss.xml
Log:
Added local interfaces support
Revision ChangesPath
1.2 +5 -1
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
[mkdir] Created dir:
User: slaboure
Date: 02/01/06 04:04:37
Added: src/main/org/jboss/ha/httpsession/interfaces
LocalClusteredHTTPSession.java
LocalClusteredHTTPSessionHome.java
Log:
Added local interfaces support
Revision ChangesPath
1.1
User: slaboure
Date: 02/01/06 04:05:32
Modified:src/main/org/jboss/ha/httpsession/server
ClusteredHTTPSessionService.java
ClusteredHTTPSessionServiceMBean.java
Log:
Added local interfaces support and generation of session-id available
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
[mkdir] Created dir:
User: slaboure
Date: 02/01/06 05:16:12
jbossmx/src/resources/ClusteredHTTPSessionService/META-INF - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: slaboure
Date: 02/01/06 05:17:53
Added: src/resources/ClusteredHTTPSessionService/META-INF
jboss-service.xml
Log:
Clustered HTTP session JMX service
Revision ChangesPath
1.1
If I add a jndi.properties file to a testsuite jar,
will it use that file for InitialContext? InitialContext looks for
jndi.properties in the CLASSPATH correct?
Thanks,
Bill
User: slaboure
Date: 02/01/06 08:02:35
Modified:src/resources/ClusteredHTTPSessionBean/META-INF ejb-jar.xml
Log:
Added abstract-schema-name tag and reference to correct DTD on SUN web site (had
moved)
Revision ChangesPath
1.3 +2 -1
User: slaboure
Date: 02/01/06 08:03:12
Modified:src/resources/ClusteredHTTPSessionBean/META-INF jboss.xml
Log:
forgot container-configurations tag
Revision ChangesPath
1.3 +2 -0
jbossmx/src/resources/ClusteredHTTPSessionBean/META-INF/jboss.xml
Index:
User: slaboure
Date: 02/01/06 08:04:22
Modified:src/main/org/jboss/ejb/plugins
CMPClusteredInMemoryPersistenceManager.java
Log:
Bug in findAll when no beans in store
Revision ChangesPath
1.4 +9 -2
User: slaboure
Date: 02/01/06 08:05:19
Modified:src/main/org/jboss/ha/httpsession/server
ClusteredHTTPSessionService.java
Log:
local home lookup was wrong
Revision ChangesPath
1.3 +3 -4
I'm not at all sure...
I think that the testcase classes are not packaged into a jar at the
moment, and there is one jndi.properties on the classpath that gets used
for all of them by default. This is very handy for non-cluster tests, but
obviously may not work for you. Could you create an
No, the unit tests run out of the build.classes directory and do
not use the output jars. You would need to load the testcase
specific jndi.properties and use an explicit env in the construction
of the InitialContext. You could try setting the System.properties
from the testcase jndi.properties
I'm having a little trouble understanding exactly what the spec requires
with regards to connection association.
I think that the following is supposed to be a requirement:
scenario:
mc1 is a ManagedConnection from ManagedConnectionFactory mcf
Object c = mc.getConnection(subject, cri)
c is
I reread the spec and what I discuss seems to be a requirement (section 6.11), however
little I like it. I think the specs are a little contradictory on this point however,
so I asked for clarification from sun and the connector interest list.
User: jules_gosnell
Date: 02/01/06 15:54:16
Modified:jetty/src/main/org/jboss/jetty
DistributedSessionManager.java
Added: jetty/src/main/org/jboss/jetty AbstractHttpSessionData.java
Log:
abstract out the pieces that need to plug into Sacha's JMX
User: jules_gosnell
Date: 02/01/06 15:54:16
Modified:jettybuild.xml
Log:
abstract out the pieces that need to plug into Sacha's JMX Session stuff
fix up javadoc for generated code too
Revision ChangesPath
1.19 +1 -1 contrib/jetty/build.xml
Index:
User: jules_gosnell
Date: 02/01/06 15:54:17
Modified:jetty/src/main/org/jboss/jetty/ejb
CoarseHttpSessionBean.java
Log:
abstract out the pieces that need to plug into Sacha's JMX Session stuff
fix up javadoc for generated code too
Revision Changes
JBoss daily test results
SUMMARY
Number of tests run: 258
Successful tests: 256
Errors:0
Failures: 2
[time of test: 7 January 2002 2:52 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 258
Successful tests: 257
Errors:0
Failures: 1
[time of test: 7 January 2002 3:20 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 258
Successful tests: 257
Errors:0
Failures: 1
[time of test: 7 January 2002 4:5 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 258
Successful tests: 257
Errors:0
Failures: 1
[time of test: 7 January 2002 4:52 GMT]
[java.version:
Anyone interested ?
This stuff is never simple !
Jules
---BeginMessage---
jules,
If you want this for fault tolerance, then I would say that the only
reasonable points that you can distribute/persist a session would be:
+ When there are no requests for that session active.
+ When
30 matches
Mail list logo
