[JBoss-dev] [ jboss-Bugs-462187 ] Typo in JNDIView
Bugs item #462187, was opened at 2001-09-17 00:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=462187group_id=22866 Category: None Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Typo in JNDIView Initial Comment: V. low priority this one (JBoss 2.4.0 final): Bound beans that appear in JNDI View under the heading Management are listed as: * jnidName=BoundName Thinking it should be jndiName= ? -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=462187group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
on 1-09-17 02.44, Julian Gosnell at [EMAIL PROTECTED] wrote: [JettyService] Initialized [JettyService] Starting [Jetty] start HttpServer version Jetty/3.1.RC9 [JettyService] Stopped java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405) at java.net.ServerSocket.init(ServerSocket.java:170) at org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:315) at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:386) I se something simular with hsqldb on Linux Blackdown VM ( have not tried other platform yet ) when redeploying ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JMX and HotDeploy GC
on 1-09-17 04.46, David Jencks at [EMAIL PROTECTED] wrote: Can you be very specific about how to reproduce this problem? I have wondered if something like this would show up but haven't seen it yet. Not sure if it is me or the autodeploy or a GC thingy yet ... I need to refactor some more before I have a hsql patch ready - meanwhile will send You a initial test case ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] 2.4.1 instance pool and ejbCreate/Remove
Hi,
I have to admit I am a little lost here. In the messaging forum a user
have wondered why ejbCreate is called every time the bean is accessed,
but never ejbRemove.
In one of his examples sending 1000 messages he gets this:
1) 1001 calls to ejbCreate()
2) 1000 calls to onMessage()
3) Zero calls to ejbRemove()
With an instence pool of 100 this does not seem reasonably. I checked
with a somewhat old 2.4.(1) CVS version, but could not verrify the
error. Then I downloaded the 2.4.1 binary, and yes, there it was.
Looking into the code I found the following new stuff in
AbstractInstancePool.free():
if (pool.size() maxSize)
{
// We do not reuse but create a brand new instance simplifies the design
try {
pool.push(create(container.createBeanClassInstance()));
} catch (Exception ignored) {}
//pool.push(ctx);
} else
{
discard(ctx);
}
To me this does not look ok. If we look at the examples statistics I
would guess he have serial behaviour. One actual object in the pool, but
will have ejbCreate called in free (1000 times), which calles create,
which created a new MDB container (same is vallid for Stateless
Session), which calles ejbCreate().
I don't know if there might be some other error somewhere, but this cind
of behaviour does not seem to be spec compliant. We basically get this:
* Bean instance does not exists
|
|
-newInstance().
-setSessionContext()
-ejbCreate
|
* Pool of ready instances -- onMethod() ---|
^ |
`--- ejbCreate() -´
It does not seems like correct behaviour that ejbCreate is called when
the instance is returned to the pool.
Or is it something I have missunderstood?
//Peter
--
Jobba hos oss: http://www.tim.se/weblab
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems ArchitectWWW: http://www.tim.se
Email: [EMAIL PROTECTED]WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 2.4.1 instance pool and ejbCreate/Remove
ejbRemove is called only when the bean is being removed from the datastore.
This is never invoked by the container. You're thinking of ejbPassivate.
Instances are not returned to the pool because we determined that there were
a few unfound bugs in the code. It may be reinstated later.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Peter
Antman
Sent: Monday, September 17, 2001 9:01 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] 2.4.1 instance pool and ejbCreate/Remove
Hi,
I have to admit I am a little lost here. In the messaging forum a user
have wondered why ejbCreate is called every time the bean is accessed,
but never ejbRemove.
In one of his examples sending 1000 messages he gets this:
1) 1001 calls to ejbCreate()
2) 1000 calls to onMessage()
3) Zero calls to ejbRemove()
With an instence pool of 100 this does not seem reasonably. I checked
with a somewhat old 2.4.(1) CVS version, but could not verrify the
error. Then I downloaded the 2.4.1 binary, and yes, there it was.
Looking into the code I found the following new stuff in
AbstractInstancePool.free():
if (pool.size() maxSize)
{
// We do not reuse but create a brand new instance
simplifies the design
try {
pool.push(create(container.createBeanClassInstance()));
} catch (Exception ignored) {}
//pool.push(ctx);
} else
{
discard(ctx);
}
To me this does not look ok. If we look at the examples statistics I
would guess he have serial behaviour. One actual object in the pool, but
will have ejbCreate called in free (1000 times), which calles create,
which created a new MDB container (same is vallid for Stateless
Session), which calles ejbCreate().
I don't know if there might be some other error somewhere, but this cind
of behaviour does not seem to be spec compliant. We basically get this:
* Bean instance does not exists
|
|
-newInstance().
-setSessionContext()
-ejbCreate
|
* Pool of ready instances -- onMethod() ---|
^ |
`--- ejbCreate() -´
It does not seems like correct behaviour that ejbCreate is called when
the instance is returned to the pool.
Or is it something I have missunderstood?
//Peter
--
Jobba hos oss: http://www.tim.se/weblab
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems Architect WWW: http://www.tim.se
Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.4.1 instance pool and ejbCreate/Remove
On 17 Sep, Bill Burke wrote:
ejbRemove is called only when the bean is being removed from the datastore.
This is never invoked by the container. You're thinking of ejbPassivate.
No I am not, since I talk about Stateless session beans and
MessageDriven beans-
The contract here is:
1. When bean goes from not exists to be added to the method ready pool:
ejbCreate is called.
2. Methods are invoked on beans in method ready pool (removed from pool
during invokation, returned to pool afterwards).
3. Bean is removed from method ready pool-ejbRemove is called and the
bean instance is ready for GC.
The way it works now is that each time a method has been invoked a new
bean (from does not exist state) is added to the pool, but the old bean
is never removed/discarded, i.e ejbRemove is never called.
Take a look at the lifecykle diagrams of the two bean types to see if
this is not the correct interpretation.
From StatelessSessionEnterpriseContext (looks the same for MDB):
public void discard()
throws RemoteException
{
((SessionBean)instance).ejbRemove();
}
This should be called whenever an instance of a bean is not more
referencable (i.e is no longer in the pool) which in the new code will
happen after every method call.
//Peter
Instances are not returned to the pool because we determined that there were
a few unfound bugs in the code. It may be reinstated later.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Peter
Antman
Sent: Monday, September 17, 2001 9:01 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] 2.4.1 instance pool and ejbCreate/Remove
Hi,
I have to admit I am a little lost here. In the messaging forum a user
have wondered why ejbCreate is called every time the bean is accessed,
but never ejbRemove.
In one of his examples sending 1000 messages he gets this:
1) 1001 calls to ejbCreate()
2) 1000 calls to onMessage()
3) Zero calls to ejbRemove()
With an instence pool of 100 this does not seem reasonably. I checked
with a somewhat old 2.4.(1) CVS version, but could not verrify the
error. Then I downloaded the 2.4.1 binary, and yes, there it was.
Looking into the code I found the following new stuff in
AbstractInstancePool.free():
if (pool.size() maxSize)
{
// We do not reuse but create a brand new instance
simplifies the design
try {
pool.push(create(container.createBeanClassInstance()));
} catch (Exception ignored) {}
//pool.push(ctx);
} else
{
discard(ctx);
}
To me this does not look ok. If we look at the examples statistics I
would guess he have serial behaviour. One actual object in the pool, but
will have ejbCreate called in free (1000 times), which calles create,
which created a new MDB container (same is vallid for Stateless
Session), which calles ejbCreate().
I don't know if there might be some other error somewhere, but this cind
of behaviour does not seem to be spec compliant. We basically get this:
* Bean instance does not exists
|
|
-newInstance().
-setSessionContext()
-ejbCreate
|
* Pool of ready instances -- onMethod() ---|
^ |
`--- ejbCreate() -´
It does not seems like correct behaviour that ejbCreate is called when
the instance is returned to the pool.
Or is it something I have missunderstood?
//Peter
--
Jobba hos oss: http://www.tim.se/weblab
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems Architect WWW: http://www.tim.se
Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
--
Jobba hos oss: http://www.tim.se/weblab
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems ArchitectWWW: http://www.tim.se
Email: [EMAIL PROTECTED]WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-462253 ] TextMessage fails for 64k content
Bugs item #462253, was opened at 2001-09-17 08:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=462253group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: TextMessage fails for 64k content Initial Comment: Subject says it all, I guess. Sending a TextMessage with more than 64k of content (actually, more than 64k UTF conformant content) fails. This is because of JDK 1.3.x limitations of readUTF/writeUTF methods defined in java.io.DataInput / java.io.DataOutput respectively. Its not by definition a bug in JBossMQ but its annoying nonetheless. The bug appears in JBoss 2.4.1, JBossMQ 1.0.0beta respectively. Prior versions are not affected. This has come up on the MQ Mailing List about a week ago, just wanted to file it into the Bug Tracking system so that this issue is generally known. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=462253group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-462261 ] JMSException: Invalid transaction id.
Bugs item #462261, was opened at 2001-09-17 08:36 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=462261group_id=22866 Category: JBossMQ Group: v2.5 Rabbit Hole (unstable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: JMSException: Invalid transaction id. Initial Comment: Operating System: Windows NT 4.0 SP6. Java version: 1.3.0,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Client VM 1.3.0-C,Sun Microsystems Inc. I believe this is a bug. If a TopicSession is reused (remains open) between transactions, an Invalid Transaction id exception is thrown. There seems to only be provisions of starting a new transaction when the TopicSession is returned from the pool and no provision of starting a new transaction if the TopicSession remains open between transactions. The exception occurs because, upon completion of the transaction, the SpySession's 'currentTransactionId' field is set to null. When a subsequent 'sendMessage' is called and redirects to 'connection.spyXAResourceManager.addMessage', a null value is passed-in as the 'xid'. This in turns causes a failed lookup of the TXState. Exception Stack Trace: [Default] javax.jms.JMSException: Invalid transaction id. [Default] javax.jms.JMSException: Invalid transaction id. [Default] at org.jboss.mq.SpyXAResourceManager.addMessage (SpyXAResourceManager.java:79) [Default] at org.jboss.mq.SpySession.sendMessage (SpySession.java:396) [Default] at org.jboss.mq.SpyTopicPublisher.publish (SpyTopicPublisher.java:106) [Default] at org.jboss.mq.SpyTopicPublisher.publish (SpyTopicPublisher.java:77) [Default] at com.novaplex.common.jms.JMSManager.publish (JMSManager.java:107) [Default] at com.novaplex.common.base.AbstractEntity.notify (AbstractEntity.java:146) [Default] at com.novaplex.common.base.AbstractEntity.notifyOnUpdate (AbstractEntity.java:121) [Default] at com.mvcsoft.pm.generated.ClientSession1000497402171.set ID(ClientSession1000497402171.java:82) [Default] at com.novaplex.common.base.AbstractEntity.ejbCreate (AbstractEntity.java:35) [Default] at com.novaplex.common.base.IndependentEntity.ejbCreate (IndependentEntity.java:27) [Default] at com.novaplex.common.session.ejb.ClientSession.ejbCreate (ClientSession.java:20) [Default] at com.mvcsoft.pm.generated.ClientSession1000497402171.ejb Create(ClientSession1000497402171.java:526) [Default] at java.lang.reflect.Method.invoke (Native Method) [Default] at org.jboss.ejb.plugins.BMPPersistenceManager.createEntit y(BMPPersistenceManager.java:168) [Default] at org.jboss.ejb.EntityContainer.createLocalHome (EntityContainer.java:534) [Default] at java.lang.reflect.Method.invoke (Native Method) [Default] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invo keHome(EntityContainer.java:927) [Default] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor. invokeHome(EntitySynchronizationInterceptor.java:231) [Default] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeH ome(EntityInstanceInterceptor.java:154) [Default] at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome (EntityLockInterceptor.java:215) [Default] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:99) [Default] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:154) [Default] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome (TxInterceptorCMT.java:54) [Default] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome (SecurityInterceptor.java:104) [Default] at org.jboss.ejb.plugins.LogInterceptor.invokeHome (LogInterceptor.java:111) [Default] at org.jboss.ejb.EntityContainer.invokeHome (EntityContainer.java:442) [Default] at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.i nvokeHome(BaseLocalContainerInvoker.java:246) [Default] at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker$H omeProxy.invoke(BaseLocalContainerInvoker.java:392) [Default] at $Proxy8.create(Unknown Source) [Default] at com.novaplex.common.session.ejb.SessionManager.logon (SessionManager.java:66) [Default] at java.lang.reflect.Method.invoke (Native Method) [Default] at org.jboss.ejb.StatelessSessionContainer$ContainerInterc eptor.invoke(StatelessSessionContainer.java:572) [Default] at org.jboss.ejb.plugins.StatelessSessionInstanceIntercept or.invoke(StatelessSessionInstanceInterceptor.java:67) [Default] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:97) [Default] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:154) [Default] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:63) [Default] at
[JBoss-dev] Re: Lutris announcement: a further look
Seems to me that JBoss can get more closely into compliance with the various Sun licenses by doing what Netbeans does: provide the various RI jars on a separate page, maybe with an installer build.xml, and ask users to accept Sun's license before getting the jar (or maybe that can be part of the installation process as well). I think right now, with all the sun jars being packaged in with the distribution, JBoss is on shaky ground, since the licenses for those jars, in most cases, specifically says they can't be redistributed. On the other hand, I agree that Lutris is spreading FUD about the J2EE specs. As long as JBoss doesn't claim to be J2EE compliant (which means passing the test, etc.), I think there is nothing in the specs for JMS, JDBC, etc. that prevents JBoss from implementing their functionality. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs preface.xml
User: gropi Date: 01/09/17 08:39:01 Modified:src/xdocs preface.xml Log: Updated links and set references to emacs tools. Revision ChangesPath 1.2 +3 -2 manual/src/xdocs/preface.xml Index: preface.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/preface.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- preface.xml 2001/08/29 09:19:36 1.1 +++ preface.xml 2001/09/17 15:39:01 1.2 @@ -25,9 +25,10 @@ paraAlthough Docbook DTD is very big, 300 + elements, the learning curve is very steep, and most of the time not more than 50 elements are used. This ulink url = http://www.caldera.de/~eric/crash-course/HTML; citetitlearticle/citetitle - /ulinkis suitable for a first contact with Docbook. A good reference that you might want to use can be found ulink url = http://www.docbook.org/tdg/html/docbook.html; + /ulinkis suitable for a first contact with Docbook. A good reference that you might want to use can be found ulink url = http://www.docbook.org/tdg/en/html/docbook.html; citetitlehere/citetitle - /ulink + /ulink. +There is also a ulink url = http://developer.arsdigita.com/doc/docbook-primer.html;citetitlevery brief introduction/citetitle/ulink with references to tools such as Emacs with PSGML. /para formalpara titleDocbook documentation guidelines/title ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest build.xml
User: d_jencks
Date: 01/09/17 10:33:52
Modified:.build.xml
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.26 +11 -6 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- build.xml 2001/09/16 05:48:28 1.25
+++ build.xml 2001/09/17 17:33:52 1.26
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.25 2001/09/16 05:48:28 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.26 2001/09/17 17:33:52 d_jencks Exp $ --
project default=main name=JBoss/Testsuite
@@ -996,6 +996,7 @@
include name=org/jboss/test/jrmp/interfaces/**/
include name=org/jboss/test/jrmp/test/DynLoading*.class/
include name=org/jboss/test/JBossTestCase.class/
+include name=org/jboss/test/JBossTestServices.class/
/fileset
/jar
@@ -1068,7 +1069,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/testbean/interfaces/**/
include name=org/jboss/test/testbean/bean/**/
-include name=org/jboss/test/testbean2/interfaces/**/
+!--include name=org/jboss/test/testbean2/interfaces/**/--
include name=org/somepackage/**/
/fileset
fileset dir=${build.resources}/testbean
@@ -1084,7 +1085,7 @@
include name=org/jboss/test/testbean2/interfaces/**/
include name=org/jboss/test/testbean2/bean/**/
/fileset
- fileset dir=${build.resources}/testbean
+ fileset dir=${build.resources}/testbean2
include name=**/*.xml/
/fileset
/jar
@@ -1261,7 +1262,8 @@
include name=org/jboss/test/security/test/PermissionName*/
/fileset
fileset dir=${build.resources}/security
-include name=**/*.xml/
+include name=**/ejb-jar.xml /
+include name=**/jboss.xml /
/fileset
/jar
@@ -1275,7 +1277,8 @@
include name=org/jboss/test/security/test/PermissionName*/
/fileset
fileset dir=${build.resources}/security-spec
-include name=**/*.xml/
+include name=**/ejb-jar.xml /
+include name=**/jboss.xml /
include name=users.properties/
include name=roles.properties/
/fileset
@@ -1295,7 +1298,8 @@
include name=org/jboss/test/security/proxy/SessionSecurityProxy.class/
/fileset
fileset dir=${build.resources}/security-spec
-include name=**/*.xml/
+include name=**/ejb-jar.xml /
+include name=**/jboss.xml /
include name=users.properties/
include name=roles.properties/
/fileset
@@ -1638,6 +1642,7 @@
sysproperty key=jbosstest.deploy.dir file=${build.lib}/
jvmarg value=-Djava.security.manager/
+ jvmarg value=-Dsecurity.domain=test-domain/
sysproperty key=java.security.policy
value=${build.resources}/security/tst.policy/
sysproperty key=java.security.auth.login.config
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/xa/test XAUnitTestCase.java
User: d_jencks
Date: 01/09/17 10:33:54
Modified:src/main/org/jboss/test/xa/test XAUnitTestCase.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +24 -18jbosstest/src/main/org/jboss/test/xa/test/XAUnitTestCase.java
Index: XAUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/xa/test/XAUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- XAUnitTestCase.java 2001/09/12 04:55:41 1.1
+++ XAUnitTestCase.java 2001/09/17 17:33:54 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.xa.test;
import java.rmi.*;
@@ -20,14 +27,22 @@
import junit.framework.TestCase;
import junit.framework.TestSuite;
-import org.jboss.test.util.Deploy;
+import org.jboss.test.JBossTestCase;
import org.jboss.test.xa.interfaces.CantSeeDataException;
import org.jboss.test.xa.interfaces.XATest;
import org.jboss.test.xa.interfaces.XATestHome;
+/* This needs lots more work to be an acceptable test case.
+Aside from needing an xa-capable database, we need an xa-test-service.xml
+file to deploy the two ConnectionFactoryLoaders.
+Then the printing needs to be changed to assertions.
+
+
+*/
+
public class XAUnitTestCase
-extends TestCase
+extends JBossTestCase
{
public XAUnitTestCase(String name)
{
@@ -117,23 +132,14 @@
protected void setUp() throws Exception
{
+ super.setUp();
+ deployJ2ee(xatest.jar);
}
- /**
-* Setup the test suite.
-*/
- public static Test suite() {
- TestSuite suite = new TestSuite();
-
- // add a test case to deploy our support applications
- String filename = xatest.jar;
- suite.addTest(new Deploy.Deployer(filename));
-
- suite.addTest(new TestSuite(XAUnitTestCase.class));
-
- // add a test case to undeploy our support applications
- suite.addTest(new Deploy.Undeployer(../deploy/xatest.jar));
-
- return suite;
+ protected void tearDown() throws Exception
+ {
+ undeployJ2ee(xatest.jar);
+ super.tearDown();
}
+
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test JBossTestServices.java JBossTestSetup.java JBossTestCase.java
User: d_jencks
Date: 01/09/17 10:33:53
Modified:src/main/org/jboss/test JBossTestCase.java
Added: src/main/org/jboss/test JBossTestServices.java
JBossTestSetup.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.3 +26 -119 jbosstest/src/main/org/jboss/test/JBossTestCase.java
Index: JBossTestCase.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/JBossTestCase.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- JBossTestCase.java2001/09/15 00:12:16 1.2
+++ JBossTestCase.java2001/09/17 17:33:52 1.3
@@ -42,22 +42,14 @@
* ../lib).
*
* @authora href=[EMAIL PROTECTED]David Jencks/a
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public class JBossTestCase
extends TestCase
{
- // Constants -
- private final static String serviceDeployerName =
JBOSS-SYSTEM:service=ServiceDeployer;
- private final static String j2eeDeployerName = J2EE:service=J2eeDeployer;
-
- // Attributes
- private RMIConnector server;
- private Category log;
- private InitialContext initialContext;
+ private JBossTestServices delegate;
- private HashSet deployed = new HashSet();
// Static
@@ -70,50 +62,45 @@
public JBossTestCase(String name)
{
super(name);
+ delegate = new JBossTestServices(getClass().getName());
}
// Public
/**
-* The JUnit setup method
+* This just checks the server is there... so you should get at least one
+* success!
*
* @exception Exception Description of Exception
*/
- protected void setUp() throws Exception
+ public void testServerFound() throws Exception
{
- log = Category.getInstance(getClass().getName());
- String serverName = System.getProperty(jbosstest.server.name);
- if (serverName == null)
- {
- serverName = InetAddress.getLocalHost().getHostName();
- }
- initialContext = new InitialContext();
- server = (RMIConnector)getInitialContext().lookup(jmx: + serverName +
:rmi);
+ assertTrue(Server was not found, getServer() != null);
}
/**
-* The teardown method for JUnit
+* The JUnit setup method
*
* @exception Exception Description of Exception
*/
- protected void tearDown() throws Exception
+ protected void setUp() throws Exception
{
- server = null;
+ delegate.setUp();
}
/**
-* This just checks the server is there... so you should get at least one
-* success!
+* The teardown method for JUnit
*
* @exception Exception Description of Exception
*/
- public void testServerFound() throws Exception
+ protected void tearDown() throws Exception
{
- assertTrue(Server was not found, server != null);
+ delegate.tearDown();
}
+
//protected-
/**
@@ -123,7 +110,7 @@
*/
protected InitialContext getInitialContext()
{
- return initialContext;
+ return delegate.getInitialContext();
}
/**
@@ -133,7 +120,7 @@
*/
protected RMIConnector getServer()
{
- return server;
+ return delegate.getServer();
}
/**
@@ -143,7 +130,7 @@
*/
protected Category getLog()
{
- return log;
+ return delegate.getLog();
}
/**
@@ -154,7 +141,7 @@
*/
protected ObjectName getServiceDeployerName() throws MalformedObjectNameException
{
- return new ObjectName(serviceDeployerName);
+ return delegate.getServiceDeployerName();
}
/**
@@ -165,7 +152,7 @@
*/
protected ObjectName getJ2eeDeployerName() throws MalformedObjectNameException
{
- return new ObjectName(j2eeDeployerName);
+ return delegate.getJ2eeDeployerName();
}
@@ -182,30 +169,7 @@
*/
protected String getDeployURL(final String filename) throws MalformedURLException
{
- //First see if it is already a complete url.
- try
- {
- return new URL(filename).toString();
- }
- catch (MalformedURLException mue)
- {
- }
- //OK, lets see if we can figure out what it might be.
- String deployDir = System.getProperty(jbosstest.deploy.dir);
- if (deployDir
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/perf/test Command.java PerfStressTestCase.java SecurePerfStressTestCase.java Setup.java
User: d_jencks
Date: 01/09/17 10:33:53
Modified:src/main/org/jboss/test/perf/test Command.java
PerfStressTestCase.java
SecurePerfStressTestCase.java Setup.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +7 -0 jbosstest/src/main/org/jboss/test/perf/test/Command.java
Index: Command.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/perf/test/Command.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Command.java 2000/08/25 13:43:45 1.1
+++ Command.java 2001/09/17 17:33:53 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.perf.test;
// Command.java
import org.jboss.test.perf.interfaces.*;
1.2 +66 -63
jbosstest/src/main/org/jboss/test/perf/test/PerfStressTestCase.java
Index: PerfStressTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/perf/test/PerfStressTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PerfStressTestCase.java 2001/09/12 04:55:40 1.1
+++ PerfStressTestCase.java 2001/09/17 17:33:53 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.perf.test;
import java.io.IOException;
@@ -23,14 +30,16 @@
import org.jboss.test.perf.interfaces.TxSession;
import org.jboss.test.perf.interfaces.TxSessionHome;
+import org.jboss.test.JBossTestCase;
+
/** Test of EJB call invocation overhead.
@author [EMAIL PROTECTED]
- @version $Revision: 1.1 $
+ @version $Revision: 1.2 $
*/
-public class PerfStressTestCase extends junit.framework.TestCase
+public class PerfStressTestCase extends JBossTestCase
{
- static int N = 1000;
+static int N = 1000;
public PerfStressTestCase(String name)
{
@@ -39,14 +48,13 @@
public void testClientSession() throws Exception
{
- System.out.println(+++ testClientSession());
- InitialContext jndiContext = new InitialContext();
- Object obj = jndiContext.lookup(ClientSession);
+ getLog().debug(+++ testClientSession());
+ Object obj = getInitialContext().lookup(ClientSession);
obj = PortableRemoteObject.narrow(obj, SessionHome.class);
SessionHome home = (SessionHome) obj;
- System.out.println(Found SessionHome @ jndiName=ClientSession);
+ getLog().debug(Found SessionHome @ jndiName=ClientSession);
Session bean = home.create(Entity);
- System.out.println(Created ClientSession);
+ getLog().debug(Created ClientSession);
try
{
bean.create(0, 100);
@@ -62,19 +70,18 @@
bean.remove(0, 100);
long end = System.currentTimeMillis();
long elapsed = end - start;
- System.out.println(Elapsed time = +(elapsed / N));
+ getLog().debug(Elapsed time = +(elapsed / N));
}
public void testTimings() throws Exception
{
- System.out.println(+++ testTimings());
- InitialContext jndiContext = new InitialContext();
- Object obj = jndiContext.lookup(Probe);
+ getLog().debug(+++ testTimings());
+ Object obj = getInitialContext().lookup(Probe);
obj = PortableRemoteObject.narrow(obj, ProbeHome.class);
ProbeHome home = (ProbeHome) obj;
- System.out.println(Found ProbeHome @ jndiName=Probe);
+ getLog().debug(Found ProbeHome @ jndiName=Probe);
Probe bean = home.create();
- System.out.println(Created Probe);
+ getLog().debug(Created Probe);
warmup(bean);
noop(bean);
ping(bean);
@@ -83,14 +90,13 @@
public void testTimingsCMT() throws Exception
{
- System.out.println(+++ testTimingsCMT());
- InitialContext jndiContext = new InitialContext();
- Object obj = jndiContext.lookup(ProbeCMT);
+ getLog().debug(+++ testTimingsCMT());
+ Object obj = getInitialContext().lookup(ProbeCMT);
obj = PortableRemoteObject.narrow(obj, ProbeHome.class);
ProbeHome home = (ProbeHome) obj;
- System.out.println(Found ProbeHome @ jndiName=ProbeCMT);
+ getLog().debug(Found ProbeHome @ jndiName=ProbeCMT);
Probe bean = home.create();
- System.out.println(Created ProbeCMT);
+ getLog().debug(Created ProbeCMT);
warmup(bean);
noop(bean);
ping(bean);
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/security/test EJBAccessUnitTestCase.java EJBSpecUnitTestCase.java NamespacePermissionCollection.java NamespacePermissionsUnitTestCase.java PermissionName.java PermissionNameUnitTestCase.java ProjRepositoryUnitTestCase.java SecurityProxyUnitTestCase.java StatelessSessionClient.java
User: d_jencks
Date: 01/09/17 10:33:54
Modified:src/main/org/jboss/test/security/test
EJBAccessUnitTestCase.java EJBSpecUnitTestCase.java
NamespacePermissionCollection.java
NamespacePermissionsUnitTestCase.java
PermissionName.java PermissionNameUnitTestCase.java
ProjRepositoryUnitTestCase.java
SecurityProxyUnitTestCase.java
StatelessSessionClient.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +24 -28
jbosstest/src/main/org/jboss/test/security/test/EJBAccessUnitTestCase.java
Index: EJBAccessUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/security/test/EJBAccessUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- EJBAccessUnitTestCase.java2001/09/12 04:55:40 1.1
+++ EJBAccessUnitTestCase.java2001/09/17 17:33:53 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.security.test;
import java.io.IOException;
@@ -13,7 +20,7 @@
import junit.framework.TestCase;
import junit.framework.TestSuite;
-import org.jboss.test.util.Deploy;
+import org.jboss.test.JBossTestCase;
import org.jboss.test.security.interfaces.StatelessSession;
import org.jboss.test.security.interfaces.StatelessSessionHome;
@@ -24,7 +31,7 @@
* @author [EMAIL PROTECTED]
*/
public class EJBAccessUnitTestCase
- extends TestCase
+ extends JBossTestCase
{
private boolean deployed;
@@ -33,29 +40,19 @@
super(name);
}
- /**
-* Setup the test suite.
-*/
- public static Test suite() {
- TestSuite suite = new TestSuite();
-
- // add a test case to deploy our support applications
- String filename = security.jar;
- suite.addTest(new Deploy.Deployer(filename));
-
- suite.addTest(new TestSuite(EJBAccessUnitTestCase.class));
-
- // add a test case to undeploy our support applications
- suite.addTest(new Deploy.Undeployer(filename));
-
- return suite;
- }
/** Deploy the security ejb jar one time
*/
protected void setUp() throws Exception
+ {
+ super.setUp();
+ deployJ2ee(security.jar);
+ }
+
+ protected void tearDown() throws Exception
{
- //Deploy.deploy(security.jar);
+ undeployJ2ee(security.jar);
+ super.tearDown();
}
public void testDeclarativeAccess() throws Exception
@@ -91,7 +88,7 @@
}
catch(Exception e)
{
-System.out.println(UnsecureStatelessSession not accessible);
+getLog().debug(UnsecureStatelessSession not accessible);
}
}
else
@@ -104,24 +101,23 @@
private void accessUnsecureStatelessSession() throws Exception
{
- InitialContext jndiContext = new InitialContext();
StatelessSession bean = null;
- Object obj = jndiContext.lookup(UnsecureStatelessSession);
+ Object obj = getInitialContext().lookup(UnsecureStatelessSession);
obj = PortableRemoteObject.narrow(obj, StatelessSessionHome.class);
StatelessSessionHome home = (StatelessSessionHome) obj;
- System.out.println(Found Unsecure StatelessSessionHome);
+ getLog().debug(Found Unsecure StatelessSessionHome);
try
{
bean = home.create();
- System.out.println(Created UnsecureStatelessSession);
- System.out.println(Bean.echo('Hello') - +bean.echo(Hello));
- System.out.println(Bean.npeError() - );
+ getLog().debug(Created UnsecureStatelessSession);
+ getLog().debug(Bean.echo('Hello') - +bean.echo(Hello));
+ getLog().debug(Bean.npeError() - );
bean.npeError();
}
catch(Exception e)
{
- System.out.println(Produced error as expected);
+ getLog().debug(Produced error as expected);
}
}
}
1.2 +77 -68
jbosstest/src/main/org/jboss/test/security/test/EJBSpecUnitTestCase.java
Index: EJBSpecUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/security/test/EJBSpecUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- EJBSpecUnitTestCase.java 2001/09/12 04:55:40 1.1
+++ EJBSpecUnitTestCase.java 2001/09/17
[JBoss-dev] CVS update: jbosstest/src/resources/testbean2/META-INF ejb-jar.xml
User: d_jencks Date: 01/09/17 10:33:54 Modified:src/resources/testbean2/META-INF ejb-jar.xml Log: Finished converting to JBossTestCase for deploy and logging. Security tests still do not work due to deploy problems Revision ChangesPath 1.2 +6 -6 jbosstest/src/resources/testbean2/META-INF/ejb-jar.xml Index: ejb-jar.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/testbean2/META-INF/ejb-jar.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ejb-jar.xml 2000/09/27 00:41:20 1.1 +++ ejb-jar.xml 2001/09/17 17:33:54 1.2 @@ -16,22 +16,22 @@ ejb-ref ejb-ref-nameejb/stateful/ejb-ref-name ejb-ref-typeSession/ejb-ref-type -homeorg.jboss.test.account.interfaces.StatefulSessionHome/home -remoteorg.jboss.test.account.interfaces.StatefulSession/remote +homeorg.jboss.test.testbean.interfaces.StatefulSessionHome/home +remoteorg.jboss.test.testbean.interfaces.StatefulSession/remote /ejb-ref ejb-ref ejb-ref-nameejb/stateless/ejb-ref-name ejb-ref-typeSession/ejb-ref-type -homeorg.jboss.test.account.interfaces.StatelessSessionHome/home -remoteorg.jboss.test.account.interfaces.StatelessSession/remote +homeorg.jboss.test.testbean.interfaces.StatelessSessionHome/home +remoteorg.jboss.test.testbean.interfaces.StatelessSession/remote /ejb-ref ejb-ref ejb-ref-nameejb/entity/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type -homeorg.jboss.test.account.interfaces.EnterpriseEntityHome/home -remoteorg.jboss.test.account.interfaces.EnterpriseEntity/remote +homeorg.jboss.test.testbean.interfaces.EnterpriseEntityHome/home +remoteorg.jboss.test.testbean.interfaces.EnterpriseEntity/remote /ejb-ref reentrantFalse/reentrant ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/testbean/test BeanUnitTestCase.java
User: d_jencks
Date: 01/09/17 10:33:54
Modified:src/main/org/jboss/test/testbean/test BeanUnitTestCase.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +22 -6
jbosstest/src/main/org/jboss/test/testbean/test/BeanUnitTestCase.java
Index: BeanUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/testbean/test/BeanUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- BeanUnitTestCase.java 2001/09/12 04:55:41 1.1
+++ BeanUnitTestCase.java 2001/09/17 17:33:54 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.testbean.test;
import java.rmi.*;
@@ -48,22 +55,22 @@
import org.jboss.test.bmp.interfaces.SimpleBMP;
import org.jboss.test.bmp.interfaces.SimpleBMPHome;
-import org.jboss.test.util.Deploy;
+import org.jboss.test.JBossTestCase;
/**
* Sample client for the jboss container.
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Hugo Pinto/a
-* @version $Id: BeanUnitTestCase.java,v 1.1 2001/09/12 04:55:41 d_jencks Exp $
+* @version $Id: BeanUnitTestCase.java,v 1.2 2001/09/17 17:33:54 d_jencks Exp $
*/
public class BeanUnitTestCase
- extends junit.framework.TestCase
+ extends JBossTestCase
{
static boolean deployed = false;
static int test = 0;
static Date startDate = new Date();
-
+
protected final String namingFactory =
System.getProperty(Context.INITIAL_CONTEXT_FACTORY);
@@ -1038,6 +1045,11 @@
protected void setUp()
throws Exception
{
+ super.setUp();
+ deployJ2ee(bmp.jar);
+ deployJ2ee(testbean.jar);
+ deployJ2ee(testbean2.jar);
+
/*
if (deployed) return;
@@ -1062,8 +1074,12 @@
protected void tearDown() throws Exception {
restoreValidNamingProperties();
+ undeployJ2ee(bmp.jar);
+ undeployJ2ee(testbean.jar);
+ undeployJ2ee(testbean2.jar);
+ super.tearDown();
}
-
+/*
public static Test suite() {
TestSuite suite = new TestSuite();
@@ -1091,5 +1107,5 @@
System.exit(0);
}
return suite;
- }
+ }*/
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: Lutris announcement: a further look
I think you are absolutely right. Can a JBG member agree on this ? Regards. -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Luigi P. Bai Sent: lundi 17 septembre 2001 17:28 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Re: Lutris announcement: a further look Seems to me that JBoss can get more closely into compliance with the various Sun licenses by doing what Netbeans does: provide the various RI jars on a separate page, maybe with an installer build.xml, and ask users to accept Sun's license before getting the jar (or maybe that can be part of the installation process as well). I think right now, with all the sun jars being packaged in with the distribution, JBoss is on shaky ground, since the licenses for those jars, in most cases, specifically says they can't be redistributed. On the other hand, I agree that Lutris is spreading FUD about the J2EE specs. As long as JBoss doesn't claim to be J2EE compliant (which means passing the test, etc.), I think there is nothing in the specs for JMS, JDBC, etc. that prevents JBoss from implementing their functionality. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/web/test WebIntegrationUnitTestCase.java
User: d_jencks
Date: 01/09/17 10:33:54
Modified:src/main/org/jboss/test/web/test
WebIntegrationUnitTestCase.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +31 -17
jbosstest/src/main/org/jboss/test/web/test/WebIntegrationUnitTestCase.java
Index: WebIntegrationUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/web/test/WebIntegrationUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- WebIntegrationUnitTestCase.java 2001/09/12 04:55:41 1.1
+++ WebIntegrationUnitTestCase.java 2001/09/17 17:33:54 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.web.test;
import java.io.IOException;
@@ -13,7 +20,7 @@
import junit.framework.TestSuite;
import org.jboss.jmx.connector.rmi.RMIConnector;
-import org.jboss.test.util.Deploy;
+import org.jboss.test.JBossTestCase;
/** Tests of servlet container integration into the JBoss server. This test
requires than a web container be integrated into the JBoss server. The tests
@@ -26,9 +33,9 @@
with a role of 'AuthorizedUser' in the servlet container.
@author [EMAIL PROTECTED]
- @version $Revision: 1.1 $
+ @version $Revision: 1.2 $
*/
-public class WebIntegrationUnitTestCase extends TestCase
+public class WebIntegrationUnitTestCase extends JBossTestCase
{
private static boolean setUp;
private static boolean webServerAvailable;
@@ -44,34 +51,35 @@
*/
protected void setUp() throws Exception
{
- if( setUp == true )
+ super.setUp();
+ /*if( setUp == true )
return;
setUp = true;
-
+ */
Integer port = Integer.getInteger(web.port, 8080);
baseURL = http://jduke:theduke@localhost:; + port + '/';
try
{
- String serverName = InetAddress.getLocalHost().getHostName();
- String connectorName = jmx: +serverName+ :rmi;
- RMIConnector server = (RMIConnector) new
InitialContext().lookup(connectorName);
- ObjectName deployerName = new ObjectName(J2EE:service=J2eeDeployer);
+ //String serverName = InetAddress.getLocalHost().getHostName();
+ //String connectorName = jmx: +serverName+ :rmi;
+ //RMIConnector server = (RMIConnector) new
InitialContext().lookup(connectorName);
+ //ObjectName deployerName = new ObjectName(J2EE:service=J2eeDeployer);
// Ask the deployer for the getWarDeployerName
Object[] params =
{};
String[] signature =
{};
- String warDeployerName = (String) server.invoke(deployerName,
- getWarDeployerName, params, signature);
+ String warDeployerName = (String) invoke(getJ2eeDeployerName(),
+ getWarDeployerName, params, signature);
// See if the warDeployerName exists
- deployerName = new ObjectName(warDeployerName);
- webServerAvailable = server.isRegistered(deployerName);
+ ObjectName deployerName = new ObjectName(warDeployerName);
+ webServerAvailable = getServer().isRegistered(deployerName);
if( webServerAvailable == true )
{
System.out.println(Found warDeployer named: +warDeployerName);
try
{
- Deploy.deploy(jbosstest-web.ear);
+ deployJ2ee(jbosstest-web.ear);
}
catch(Exception e)
{
@@ -84,7 +92,7 @@
{other};
signature = new String[]
{java.lang.String};
-server.invoke(jaasMgr, flushAuthenticationCache, params, signature);
+invoke(jaasMgr, flushAuthenticationCache, params, signature);
}
else
{
@@ -102,6 +110,12 @@
System.out.println(No war deployer found, skipping tests);
}
}
+
+ protected void tearDown() throws Exception
+ {
+ undeployJ2ee(jbosstest-web.ear);
+ super.tearDown();
+ }
/** Access the http://localhost/jbosstest/EJBOnStartupServlet
*/
@@ -220,7 +234,7 @@
throw e;
}
}
-
+/*
public static void main(java.lang.String[] args)
{
System.setErr(System.out);
@@ -253,5 +267,5 @@
return suite;
}
-
+*/
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/xa/bean XATestBean.java
User: d_jencks Date: 01/09/17 10:33:54 Modified:src/main/org/jboss/test/xa/bean XATestBean.java Log: Finished converting to JBossTestCase for deploy and logging. Security tests still do not work due to deploy problems Revision ChangesPath 1.4 +7 -0 jbosstest/src/main/org/jboss/test/xa/bean/XATestBean.java Index: XATestBean.java === RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/xa/bean/XATestBean.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- XATestBean.java 2001/07/06 00:38:51 1.3 +++ XATestBean.java 2001/09/17 17:33:54 1.4 @@ -1,3 +1,10 @@ +/* + * JBoss, the OpenSource J2EE webOS + * + * Distributable under LGPL license. + * See terms of license at gnu.org. + */ + package org.jboss.test.xa.bean; import java.sql.Connection; ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-462292 ] Tests converted to JBossTestCase
Change Notes item #462292, was opened at 2001-09-17 10:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=462292group_id=22866 Category: None Group: v3.0 (Rabbit Hole) Status: Open Priority: 5 Submitted By: David Jencks (d_jencks) Assigned to: Nobody/Anonymous (nobody) Summary: Tests converted to JBossTestCase Initial Comment: I have completed modifying the test cases to descend from JBossTestCase (and sometimes use JBossTestSetup). These provide deployment, logging, and InitialContext services and access to the MBean server (through the RMI connector) The following problems remain: 1. The jars for the security tests do not deploy. I haven't located what is misconfigured. Perhaps a security expert could fix this. 2. The TestBean test is not really a junit test yet: it does not appear to test everything with an assertion. For this reason I did not convert to use log4j logging. 3. The XA test fails due to lack of configured datasources and, presumably, an xa database. 4. The web tests fail. I am assuming this is due to Jetty not being deployed quite properly yet. Perhaps a Jetty expert could look at this. 5. Some of the Stress tests timeout on my machine. 6. Some tests appear to hang occasionally when run in a suite, but not when run alone. Desirable enhancements: I haven't checked thoroughly, but I think most ejbs are not configured to drop any tables they may have jaws create. I think they should. Some tests seem to duplicate a lot of other tests. More flexible timeout mechanism. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=462292group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/readahead/test ReadAheadUnitTestCase.java
User: d_jencks
Date: 01/09/17 10:33:53
Modified:src/main/org/jboss/test/readahead/test
ReadAheadUnitTestCase.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests still
do not work due to deploy problems
Revision ChangesPath
1.2 +19 -15
jbosstest/src/main/org/jboss/test/readahead/test/ReadAheadUnitTestCase.java
Index: ReadAheadUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/readahead/test/ReadAheadUnitTestCase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ReadAheadUnitTestCase.java2001/09/12 04:55:40 1.1
+++ ReadAheadUnitTestCase.java2001/09/17 17:33:53 1.2
@@ -1,3 +1,10 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
package org.jboss.test.readahead.test;
import javax.naming.Context;
@@ -10,17 +17,17 @@
import org.jboss.test.readahead.interfaces.CMPFindTestSessionHome;
import org.jboss.test.readahead.interfaces.CMPFindTestSessionRemote;
-import org.jboss.test.util.Deploy;
+import org.jboss.test.JBossTestCase;
/**
* TestCase driver for the readahead finder tests
*
* @author a href=mailto:[EMAIL PROTECTED];danch (Dan Christopherson/a
- * @version $Id: ReadAheadUnitTestCase.java,v 1.1 2001/09/12 04:55:40 d_jencks Exp $
+ * @version $Id: ReadAheadUnitTestCase.java,v 1.2 2001/09/17 17:33:53 d_jencks Exp $
*
* Revision:
*/
-public class ReadAheadUnitTestCase extends TestCase {
+public class ReadAheadUnitTestCase extends JBossTestCase {
CMPFindTestSessionRemote rem = null;
@@ -30,28 +37,25 @@
protected void tearDown() throws Exception {
if (rem != null) {
- System.out.println(Removing test data);
+ getLog().debug(Removing test data);
rem.removeTestData();
rem.remove();
rem = null;
}
+ undeployJ2ee(readahead.jar);
+ super.tearDown();
}
protected void setUp()
throws Exception
{
- if (rem != null)
- return;
-
- // System.out.println(Deploying);
- // new org.jboss.jmx.client.Deployer().deploy(../deploy/readahead.jar);
-
- System.out.println(Creating test data);
- Context ctx = new InitialContext();
+ super.setUp();
+ deployJ2ee(readahead.jar);
+ getLog().debug(Creating test data);
CMPFindTestSessionHome home =
- (CMPFindTestSessionHome)ctx.lookup(CMPFindTestSession);
+ (CMPFindTestSessionHome)getInitialContext().lookup(CMPFindTestSession);
rem = home.create();
rem.createTestData();
@@ -71,7 +75,7 @@
/**
* Setup the test suite.
-*/
+* /
public static Test suite() {
TestSuite suite = new TestSuite();
@@ -85,5 +89,5 @@
suite.addTest(new Deploy.Undeployer(filename));
return suite;
- }
+ }*/
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Can we move to hsqldb (1.6.1) only and drop 1.4? (rabbithole)
For rabbithole-- Assuming we can get the new hypersonic hsqldb 1.6.1 working properly, does anyone object if we drop support for the (now unsupported) Hypersonic 1.4? Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/util Deploy.java
User: d_jencks Date: 01/09/17 10:33:54 Removed: src/main/org/jboss/test/util Deploy.java Log: Finished converting to JBossTestCase for deploy and logging. Security tests still do not work due to deploy problems ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Security tests help wanted (rabbithole)
For rabbithole-- I've fixed the obvious (to me) problems in the security tests around deploying the security.jar etc (now the j2ee deployer is called), however the jars are still not deploying correctly. Could a security expert take a look and fix the configuration problems? Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-462306 ] JNDIBrowser.sh was missing
Patches item #462306, was opened at 2001-09-17 11:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462306group_id=22866 Category: None Group: v2.5 Rabbit Hole (unstable) Status: Open Resolution: None Priority: 5 Submitted By: Tom Vijlbrief (tvijlbrief) Assigned to: Nobody/Anonymous (nobody) Summary: JNDIBrowser.sh was missing Initial Comment: JNDIBrowser.sh is a new file for jboss-all/admin/src/bin (only the JNDIBrowser.bat was supplied) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462306group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Jboss source problem still
I'm using RH 7.1 (intel) Linux, JDK1.3.1 from sun. [dean@commander dean]$ echo $JAVA_HOME /usr/local/jdk1.3.1 [dean@commander dean]$ echo $CLASSPATH /usr/local/jdk1.3.1/lib/tools.jar:/usr/local/jdk1.3.1/lib/oracle.jar:/usr/lo cal/jdk1.3. 1/lib/interclient.jar:/usr/local/jdk1.3.1/lib/htmlconverter.jar:/usr/local/j dk1.3.1/lib /dt.jar:/usr/local/jdk1.3.1/jre/lib/ext/servlet.jar:/usr/local/jdk1.3.1/jre/ lib/ext/par ser.jar:/usr/local/jdk1.3.1/jre/lib/ext/jsse.jar:/usr/local/jdk1.3.1/jre/lib /ext/jnet.j ar:/usr/local/jdk1.3.1/jre/lib/ext/jcert.jar:/usr/local/jdk1.3.1/jre/lib/ext /jaxp.jar: [dean@commander dean]$ I downloaded from 2.4.1 and 2.4.0 (plain, not Jetty or Tomcat) from Sourceforge. (src dir, no build environment, nothing like jboss-all) used cvs from :pserver:[EMAIL PROTECTED]:/cvsroot/jboss to get jboss-all cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/jboss co jboss-all cd jboss-all cvs update -d cd build sh build.sh ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-462328 ] Fix for bug #462253 (TextMessage 64k)
Patches item #462328, was opened at 2001-09-17 12:46 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462328group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Riege (lqd) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for bug #462253 (TextMessage 64k) Initial Comment: the attached patch file (done vs. the Branch_2_4 CVS branch of JBossMQ module) should fix the message limit of 64k that was superimposed on us by the readUTF()/writeUTF() methods of JDK 1.3.x. It's not been tested extensively but it Works For Me (tm). Only tested with the RollingLog based persistence manager and OIL invocation layer. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462328group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/web/WEB-INF web.xml
User: jules_gosnell Date: 01/09/17 12:56:48 Modified:src/resources/web/WEB-INF web.xml Log: Servlet mappings must start with a '/', if not a '*' according to Greg (Jetty author) and the Servlet Spec (I'll dig out the quote if anyone takes me to task on this one). Jetty is rather strict on this one. So I am having to be likewise. Revision ChangesPath 1.15 +2 -2 jbosstest/src/resources/web/WEB-INF/web.xml Index: web.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/web/WEB-INF/web.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- web.xml 2001/09/09 07:09:15 1.14 +++ web.xml 2001/09/17 19:56:48 1.15 @@ -123,7 +123,7 @@ /servlet-mapping servlet-mapping servlet-nameIncludeServlet/servlet-name -url-patternIncludeServlet/url-pattern +url-pattern/IncludeServlet/url-pattern /servlet-mapping servlet-mapping servlet-nameSecureIncludeServlet/servlet-name @@ -139,7 +139,7 @@ /servlet-mapping servlet-mapping servlet-nameUnsecureEJBServlet/servlet-name -url-patternUnsecureEJBAccess/url-pattern +url-pattern/UnsecureEJBAccess/url-pattern /servlet-mapping servlet-mapping servlet-nameSecureEJBServletMT/servlet-name ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-462333 ] Translated admin/src/bin/*.bat to *.sh
Patches item #462333, was opened at 2001-09-17 13:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462333group_id=22866 Category: JBossServer Group: v2.5 Rabbit Hole (unstable) Status: Open Resolution: None Priority: 5 Submitted By: Tom Vijlbrief (tvijlbrief) Assigned to: Nobody/Anonymous (nobody) Summary: Translated admin/src/bin/*.bat to *.sh Initial Comment: tom@grumpy:~/src/jboss/jboss-all/admin/src/bin zip -o sh.zip *.sh adding: EJBVerifier.sh (deflated 41%) adding: InvocationLog.sh (deflated 41%) adding: JNDIBrowser.sh (deflated 41%) adding: Monitor.sh (deflated 45%) adding: SystemLog.sh (deflated 48%) adding: adminlogin.sh (deflated 41%) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=462333group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RH, Jetty, testsuite, Exceptions...
It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) [Default] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) [Default] at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) [Default] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) [Default] at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) [Default] at java.lang.Thread.run(Thread.java:484) [Jetty] Servlet Exception for /jbosstest/ENCServlet javax.naming.NameNotFoundException: QueueConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getObject(Unknown Source) at org.jnp.server.NamingServer.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) getRootCause(): I have a few more exceptions after this one, but they may be as a result of this failing. If any kind soul knows about this test, and whether it is new, and expecting me to do something that I am not doing, I would appreciate your letting me know. It is possible, that the testsuite is in a state of flux at the moment (refreshed an hour or so ago) and that this won't work anyway ? Cheers, Jules
RE: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) [Default] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) [Default] at org.mortbay.http.SocketListener.handleConnection(SocketListene r.java:146) [Default] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) [Default] at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool. java:613) [Default] at java.lang.Thread.run(Thread.java:484) [Jetty] Servlet Exception for /jbosstest/ENCServlet javax.naming.NameNotFoundException: QueueConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getObject(Unknown Source) at org.jnp.server.NamingServer.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListene r.java:146) at
Re: [JBoss-dev] Re: Jboss source problem still
The source for 2.4.x, no matter how you get it, uses a build system incompatible with the source for 3.0, which you get by checking out jboss-all. I think to check the source for 2.4.x out of cvs you have to check out each module under their cvs directory name (jboss, jbosscx, etc) independently and build each independently. The dependencies between the resulting jars are rather tricky to get right, thus the new build system. As I recall you don't need CLASSPATH set to build the modules, although I haven't built 2.4.x for a long time. Try again with only one version at a time. david jencks On 2001.09.17 14:36:19 -0400 Dean Anderson wrote: I'm using RH 7.1 (intel) Linux, JDK1.3.1 from sun. [dean@commander dean]$ echo $JAVA_HOME /usr/local/jdk1.3.1 [dean@commander dean]$ echo $CLASSPATH /usr/local/jdk1.3.1/lib/tools.jar:/usr/local/jdk1.3.1/lib/oracle.jar:/usr/lo cal/jdk1.3. 1/lib/interclient.jar:/usr/local/jdk1.3.1/lib/htmlconverter.jar:/usr/local/j dk1.3.1/lib /dt.jar:/usr/local/jdk1.3.1/jre/lib/ext/servlet.jar:/usr/local/jdk1.3.1/jre/ lib/ext/par ser.jar:/usr/local/jdk1.3.1/jre/lib/ext/jsse.jar:/usr/local/jdk1.3.1/jre/lib /ext/jnet.j ar:/usr/local/jdk1.3.1/jre/lib/ext/jcert.jar:/usr/local/jdk1.3.1/jre/lib/ext /jaxp.jar: [dean@commander dean]$ I downloaded from 2.4.1 and 2.4.0 (plain, not Jetty or Tomcat) from Sourceforge. (src dir, no build environment, nothing like jboss-all) used cvs from :pserver:[EMAIL PROTECTED]:/cvsroot/jboss to get jboss-all cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/jboss co jboss-all cd jboss-all cvs update -d cd build sh build.sh ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Jboss source problem still
on 1-09-17 20.36, Dean Anderson at [EMAIL PROTECTED] wrote: I downloaded from 2.4.1 and 2.4.0 (plain, not Jetty or Tomcat) from Sourceforge. (src dir, no build environment, nothing like jboss-all) Yes - BuildMagic _happens_ to evolve into RH (jboss-all = jboss3.0.0alpha) - before was another build structure -remembering building on Linux but not on 2k -the .bat did not work for me. You should use another cvs command to get : module = 2.4.1 or 2.4.0 ??? ... http://jboss.org/zip_archives/ listed all modules available ... right now it is empty tho ??? ... I guess they are collector items ;-) Downloading jboss-all and cd to build then run - should work out of the box ... and does inbetween ... I found the command 'sh build.sh help' very usefull ... it gave me 'clean' and 'clobber' also 'all' ++ just build some modules or test run -- TrueMagic ... some have to be adjusted -some of the commands is now differing depending on setup ... time is on our side ... so You need to get ahold of 2.4.0/1 src ? and learn the that build method ? /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RH: javac.jar - lib/ext ???
This is probably one for Jason, Jetty requires javac.jar to be somewhere in the runtime tree, for compilation of JSPs etc. 1. Where in the runtime tree should it go (I guessed lib/ext) ? 2. How should it get there (Is it a build action, a clever runtime dependency,...) ? Thanks, Jules _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at
[JBoss-dev] Re: Security and Jetty
Nicolai P Guba wrote: Julian Gosnell [EMAIL PROTECTED] writes: Nicolai, I'm afraid that I'm not the security expert. Put a little more about exactly what the problem is, and how to reproduce it, and cross-post this to [EMAIL PROTECTED] and [EMAIL PROTECTED] I will do everything I can to ensure the problem is sorted out quickly. Thanks for letting me know about this, No probs. I've noticed Scott posting some fix to the tomcat integration, could be that Jetty is affected as well. I've looked through the dev archive, but couldn't see anything going in to the tomcat stuff recently - any pointers ? BTW why not package the lot so that tomcat and jetty are seperate bundles? Smaller files and much easier to manage/upgrade. It used to be done that way - but the powers that be decided it would be easier for users if the bundles came preconfigured for one or the other. What we should do to encourage decent competition is ship a bundle with configurations and jars for both servlet engines (why not catalina as well!). Are you offering ? Jules Just a thought. It's only one jboss config directory and the jetty source tree. Happy Hacking! -- Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] GSM: +44 (0)7909 960 751 DDI: +44 (0)20 7368 9708 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq SpyTextMessage.java
User: dmaplesden
Date: 01/09/17 14:09:46
Modified:src/main/org/jboss/mq SpyTextMessage.java
Log:
Apply submitted patch for working around write/read utf limitation in jdk 1.3.*
Revision ChangesPath
1.3 +39 -4 jbossmq/src/main/org/jboss/mq/SpyTextMessage.java
Index: SpyTextMessage.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/SpyTextMessage.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- SpyTextMessage.java 2001/08/17 03:04:01 1.2
+++ SpyTextMessage.java 2001/09/17 21:09:46 1.3
@@ -7,6 +7,7 @@
package org.jboss.mq;
import java.io.*;
+import java.util.ArrayList;
import javax.jms.JMSException;
import javax.jms.MessageNotWriteableException;
@@ -17,7 +18,7 @@
*
* @author Norbert Lataille ([EMAIL PROTECTED])
* @createdAugust 16, 2001
- * @version$Revision: 1.2 $
+ * @version$Revision: 1.3 $
*/
public class SpyTextMessage
extends SpyMessage
@@ -28,7 +29,8 @@
String content = null;
private final static long serialVersionUID = 235726945332013953L;
-
+ private final static int chunkSize = 16384;
+
// Public
public void setText( String string )
@@ -65,7 +67,17 @@
if ( type == NULL ) {
content = null;
} else {
- content = in.readUTF();
+ // apply workaround for string 64K bug in jdk's 1.3.*
+
+ // Read the no. of chunks this message is split into, allocate
+ // a StringBuffer that can hold all chunks, read the chunks
+ // into the buffer and set 'content' accordingly
+ int chunksToRead = in.readInt();
+ StringBuffer sb = new StringBuffer(chunkSize * chunksToRead);
+ for (int i = 0; i chunksToRead; i++) {
+sb.append( in.readUTF() );
+ }
+ content = sb.toString();
}
}
@@ -75,8 +87,31 @@
if ( content == null ) {
out.writeByte( NULL );
} else {
+ // apply workaround for string 64K bug in jdk's 1.3.*
+
+ // Split content into chunks of size 'chunkSize' and assemble
+ // the pieces into a Vector ...
+ ArrayList v = new ArrayList();
+ int contentLength = content.length();
+
+ while (contentLength 0) {
+int beginCopy = (v.size()) * chunkSize;
+int endCopy = contentLength = chunkSize ?
+ beginCopy + contentLength : beginCopy + chunkSize;
+
+String theChunk = content.substring(beginCopy, endCopy);
+v.add(theChunk);
+
+contentLength -= chunkSize;
+ }
+
+ // Write out the type (OBJECT), the no. of chunks and finally
+ // all chunks that have been assembled previously
out.writeByte( OBJECT );
- out.writeUTF( content );
+ out.writeInt(v.size());
+ for (int i = 0; i v.size(); i++) {
+out.writeUTF( (String)v.get(i) );
+ }
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Hmm.. you sure the auth.conf file is available in your classpath for the client? -- Juha On Mon, 17 Sep 2001, Julian Gosnell wrote: Date: Mon, 17 Sep 2001 21:49:05 +0100 From: Julian Gosnell [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Security is broken in RH as the security setup code has been commented out in org.jboss.Main. Until I look into restoring this all security tests are pointless. - Original Message - From: Julian Gosnell [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, September 17, 2001 1:49 PM Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.j ava:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
HaHa! OK, Thanks, Scott, I'll move on Cheers, Jules Scott M Stark wrote: Security is broken in RH as the security setup code has been commented out in org.jboss.Main. Until I look into restoring this all security tests are pointless. - Original Message - From: Julian Gosnell [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, September 17, 2001 1:49 PM Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.j ava:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
I'm running the testsuite, so I assume that it is, or it would never have run. I've checked in all my changes. So if anyone wants to refresh their RH tree and run the web test module, I would be interested to hear their thoughts. Thanks, Jules Juha-P Lindfors wrote: Hmm.. you sure the auth.conf file is available in your classpath for the client? -- Juha On Mon, 17 Sep 2001, Julian Gosnell wrote: Date: Mon, 17 Sep 2001 21:49:05 +0100 From: Julian Gosnell [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at
[JBoss-dev] JBoss/Jetty - Virtual Host support.
There is a patch in the jboss patch list to do virtual host support. It seems to take the route of adding a virtual host attribute to the J2EEDeployer - one deployer:one host. So the more virtual hosts you want, the more J2EEDeployers you run. This is quite nice as it means you can do stuff like move an ear from host1.deploy/foo.ear to host2.deploy/foo.ear and your app will be hot-undeployed from one virtual host and hot-redeployed onto another one. I did kick off a thread about this a while ago, but I want to approach this from a different angle and get a consensus on how it should be done, since I think it would be fun to have. 1. Are virtual hosts an EAR or WAR level thang ? e.g. do they have any relevance to EJBs ? 2. Is there any support for it in standard J2EE descriptors ? 3. If not, should it be configured in e.g. a proprietary descriptor, or achieved in some other way (like multiple deployers) ? I like the multiple deployer solution presented, however I see a couple of problems. If this is a WAR level abstraction, then you could argue that changes to accomodate it should only impact on the web-container. What happens if you want to say e.g. app1 runs on host1,2,3 and app2 runs on host2,3,4 ? You could do it by deploying multiple copies of the apps, but I am sure i recall being shown a piece of configuration in which a list of hosts was configured for a single app Perhaps a single deployer could support a group of virtual hosts ? - or is this just multiple deployers watching a single directory (No, because you may want to talk to a single deployer via e.g. JMX)_.. etc... Anyone interested ? Jules _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Build failed of the module jboss-all
When i try to compile the jboss-all module i get a compile errors (with jdk1.4 on Windows 2000) 1) org.jboss.ejb.DeploymentException (in the server module) Exception getCause() compile-error try to override with a different return type should be Throwable 2) jboss.security.ssl.RMISSLServerSocketFactory (in the security module) compiler error reference to SSLContext and KeyManagerFactory are ambiguous. classes are duplicated in the packages com.sun.net.ssl and javax.net.ssl their are more compiler errors but i got to go sleep.(connector module) and lost of warnings of deprecations and the assert method that seems to be a keyword in jdk1.4 Greetz-Tbone ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/main/org/jboss/jetty JBossLogSink.java JBossUserRealm.java Jetty.java JettyMBean.java JettyResolver.java SetupHandler.java
User: jules_gosnell Date: 01/09/17 16:10:57 Modified:jetty/src/main/org/jboss/jetty Tag: Branch_2_4 JBossLogSink.java JBossUserRealm.java Jetty.java JettyMBean.java JettyResolver.java SetupHandler.java Log: share src between 2.4 and 3.0 Revision ChangesPath No revision No revision 1.2.2.2 +4 -7 contrib/jetty/src/main/org/jboss/jetty/JBossLogSink.java Index: JBossLogSink.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/JBossLogSink.java,v retrieving revision 1.2.2.1 retrieving revision 1.2.2.2 diff -u -r1.2.2.1 -r1.2.2.2 --- JBossLogSink.java 2001/09/15 13:14:59 1.2.2.1 +++ JBossLogSink.java 2001/09/17 23:10:57 1.2.2.2 @@ -1,6 +1,3 @@ -// -// $Id: JBossLogSink.java,v 1.2.2.1 2001/09/15 13:14:59 jules_gosnell Exp $ -// /* * jBoss, the OpenSource EJB server * @@ -8,16 +5,16 @@ * See terms of license at gnu.org. */ -// $Id: JBossLogSink.java,v 1.2.2.1 2001/09/15 13:14:59 jules_gosnell Exp $ +// $Id: JBossLogSink.java,v 1.2.2.2 2001/09/17 23:10:57 jules_gosnell Exp $ package org.jboss.jetty; +import java.util.HashMap; +import org.apache.log4j.Category; import org.mortbay.util.Code; import org.mortbay.util.Frame; import org.mortbay.util.Log; import org.mortbay.util.LogSink; -import java.util.HashMap; -import org.apache.log4j.Category; /* */ @@ -25,7 +22,7 @@ * This class bidges the API between Jetty and Log4J. * * @author a href=mailto:;Jules Gosnell/a - * @version $Id: JBossLogSink.java,v 1.2.2.1 2001/09/15 13:14:59 jules_gosnell Exp $ + * @version $Id: JBossLogSink.java,v 1.2.2.2 2001/09/17 23:10:57 jules_gosnell Exp $ * @since 1.0 * @see org.mortbay.util.LogSink */ 1.2.2.2 +12 -6 contrib/jetty/src/main/org/jboss/jetty/JBossUserRealm.java Index: JBossUserRealm.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/JBossUserRealm.java,v retrieving revision 1.2.2.1 retrieving revision 1.2.2.2 diff -u -r1.2.2.1 -r1.2.2.2 --- JBossUserRealm.java 2001/09/15 13:14:59 1.2.2.1 +++ JBossUserRealm.java 2001/09/17 23:10:57 1.2.2.2 @@ -1,3 +1,12 @@ +/* + * jBoss, the OpenSource EJB server + * + * Distributable under GPL license. + * See terms of license at gnu.org. + */ + +// $Id: JBossUserRealm.java,v 1.2.2.2 2001/09/17 23:10:57 jules_gosnell Exp $ + package org.jboss.jetty; import java.util.HashSet; @@ -12,14 +21,11 @@ import org.mortbay.http.HttpRequest; import org.mortbay.http.UserPrincipal; import org.mortbay.http.UserRealm; - -// $Id: JBossUserRealm.java,v 1.2.2.1 2001/09/15 13:14:59 jules_gosnell Exp $ - -/** An implementation of UserRealm that integrates with the JBossSX security -manager associted with the web application. +/** An implementation of UserRealm that integrates with the JBossSX + * security manager associted with the web application. * @author [EMAIL PROTECTED] - * @version $Revision: 1.2.2.1 $ + * @version $Revision: 1.2.2.2 $ */ public class JBossUserRealm implements UserRealm 1.9.2.4 +4 -4 contrib/jetty/src/main/org/jboss/jetty/Jetty.java Index: Jetty.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/Jetty.java,v retrieving revision 1.9.2.3 retrieving revision 1.9.2.4 diff -u -r1.9.2.3 -r1.9.2.4 --- Jetty.java2001/09/15 13:14:59 1.9.2.3 +++ Jetty.java2001/09/17 23:10:57 1.9.2.4 @@ -5,16 +5,13 @@ * See terms of license at gnu.org. */ -// $Id: Jetty.java,v 1.9.2.3 2001/09/15 13:14:59 jules_gosnell Exp $ +// $Id: Jetty.java,v 1.9.2.4 2001/09/17 23:10:57 jules_gosnell Exp $ // A Jetty HttpServer with the interface expected by JBoss' // J2EEDeployer... package org.jboss.jetty; -import org.mortbay.http.HttpHandler; -import org.mortbay.jetty.servlet.WebApplicationContext; -import org.mortbay.util.Resource; import java.io.FileNotFoundException; import java.net.URL; import java.util.HashMap; @@ -24,6 +21,9 @@ import org.jboss.ejb.DeploymentException; import org.jboss.web.AbstractWebContainer.WebDescriptorParser; import org.jboss.web.WebApplication; +import org.mortbay.http.HttpHandler; +import org.mortbay.jetty.servlet.WebApplicationContext; +import org.mortbay.util.Resource; public class
[JBoss-dev] CVS update: contrib/jetty/src/main/org/jboss/jetty JBossUserRealm.java JettyMBean.java JettyResolver.java
User: jules_gosnell Date: 01/09/17 16:07:47 Modified:jetty/src/main/org/jboss/jetty JBossUserRealm.java JettyMBean.java JettyResolver.java Log: share src between 2.4 and 3.0 Revision ChangesPath 1.7 +4 -5 contrib/jetty/src/main/org/jboss/jetty/JBossUserRealm.java Index: JBossUserRealm.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/JBossUserRealm.java,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- JBossUserRealm.java 2001/09/16 17:14:17 1.6 +++ JBossUserRealm.java 2001/09/17 23:07:47 1.7 @@ -5,7 +5,7 @@ * See terms of license at gnu.org. */ -// $Id: JBossUserRealm.java,v 1.6 2001/09/16 17:14:17 jules_gosnell Exp $ +// $Id: JBossUserRealm.java,v 1.7 2001/09/17 23:07:47 jules_gosnell Exp $ package org.jboss.jetty; @@ -22,11 +22,10 @@ import org.mortbay.http.UserPrincipal; import org.mortbay.http.UserRealm; -/** An implementation of UserRealm that integrates with the JBossSX security -manager associted with the web application. - +/** An implementation of UserRealm that integrates with the JBossSX + * security manager associted with the web application. * @author [EMAIL PROTECTED] - * @version $Revision: 1.6 $ + * @version $Revision: 1.7 $ */ public class JBossUserRealm implements UserRealm 1.4 +1 -1 contrib/jetty/src/main/org/jboss/jetty/JettyMBean.java Index: JettyMBean.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/JettyMBean.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 1.3 +1 -1 contrib/jetty/src/main/org/jboss/jetty/JettyResolver.java Index: JettyResolver.java === RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/JettyResolver.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss/Jetty - Virtual Host support.
1. Are virtual hosts an EAR or WAR level thang ? e.g. do they have any relevance to EJBs ? Yes it does if you expose EJBs through the virtual host interface. On the other hand, you may only want HTTP exposed as most security geeks have a hang up about only allowing incoming HTTP through the firewall. Other resources may need to be exposed as well: JNDI, JMS, JavaMail, etc. 2. Is there any support for it in standard J2EE descriptors ? Not that I have seen. 3. If not, should it be configured in e.g. a proprietary descriptor, or achieved in some other way (like multiple deployers) ? I like the multiple deployer solution presented, however I see a couple of problems. If this is a WAR level abstraction, then you could argue that changes to accomodate it should only impact on the web-container. What happens if you want to say e.g. app1 runs on host1,2,3 and app2 runs on host2,3,4 ? You could do it by deploying multiple copies of the apps, but I am sure i recall being shown a piece of configuration in which a list of hosts was configured for a single app Perhaps a single deployer could support a group of virtual hosts ? - or is this just multiple deployers watching a single directory (No, because you may want to talk to a single deployer via e.g. JMX)_.. etc... I see this as more of a MBean(deployer) configuration rather than an application configuration because in general there are a number of administrative issues associated with the interface: routing, firewalls, encryption... So the deployer is configured based on the virtual host accessibility. Anyone interested ? Yes. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily build failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = HERE ARE THE LAST 50 LINES OF THE LOG FILE java.class.path: /home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3_ibm_20010723/lib/tools.jar java.version:1.3.0 java.vendor: IBM Corporation java.vm.version: 1.3.0 java.vm.name:Classic VM java.vm.info:J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc) os.name: Linux os.arch: x86 os.version: 2.4.3-12 compile-classes: [mkdir] Created dir: /home/lubega/jbossro/jboss-all/naming/output/classes [javac] Compiling 12 source files to /home/lubega/jbossro/jboss-all/naming/output/classes compile-rmi: [rmic] Verify has been turned on. [rmic] RMI Compiling 1 class to /home/lubega/jbossro/jboss-all/naming/output/classes java.lang.NoClassDefFoundError: com/sun/corba/se/internal/util/Utility at sun.rmi.rmic.RMIGenerator.sourceFileForClass(RMIGenerator.java:186) at sun.rmi.rmic.RMIGenerator.init(RMIGenerator.java:267) at sun.rmi.rmic.RMIGenerator.generate(RMIGenerator.java:105) at sun.rmi.rmic.Main.doCompile(Main.java:526) at sun.rmi.rmic.Main.compile(Main.java:133) at java.lang.reflect.Method.invoke(Native Method) at org.apache.tools.ant.taskdefs.rmic.SunRmic.execute(SunRmic.java:89) at org.apache.tools.ant.taskdefs.Rmic.execute(Rmic.java:397) at org.apache.tools.ant.Task.perform(Task.java:217) at org.apache.tools.ant.Target.execute(Target.java:164) at org.apache.tools.ant.Target.performTasks(Target.java:182) at org.apache.tools.ant.Project.executeTarget(Project.java:601) at planet57.tools.buildmagic.task.Ant.execute(Ant.java:261) at planet57.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:282) at planet57.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:197) at org.apache.tools.ant.Task.perform(Task.java:217) at org.apache.tools.ant.Target.execute(Target.java:164) at org.apache.tools.ant.Target.performTasks(Target.java:182) at org.apache.tools.ant.Project.executeTarget(Project.java:601) at org.apache.tools.ant.Project.executeTargets(Project.java:560) at org.apache.tools.ant.Main.runBuild(Main.java:454) at org.apache.tools.ant.Main.start(Main.java:153) at org.apache.tools.ant.Main.main(Main.java:176) [rmic] error: An error has occurred in the compiler; please file a bug report (http://java.sun.com/cgi-bin/bugreport.cgi). [rmic] 1 error BUILD FAILED /home/lubega/jbossro/jboss-all/naming/build.xml:297: Rmic failed, messages should have been provided. Total time: 1 minute 14 seconds ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Regarding javac.jar distribution
Were not distributing the javac.jar file as it is unknown where it came from and the current JDK replacement, tools.jar is not a redistributable component. If a servlet container wants to verify that a javac compiler exists it would have to query for the javac entry point. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest build.xml
User: d_jencks
Date: 01/09/17 20:43:52
Modified:.build.xml
Log:
added log4j properties so you can see the logging
Revision ChangesPath
1.27 +18 -1 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- build.xml 2001/09/17 17:33:52 1.26
+++ build.xml 2001/09/18 03:43:51 1.27
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.26 2001/09/17 17:33:52 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.27 2001/09/18 03:43:51 d_jencks Exp $ --
project default=main name=JBoss/Testsuite
@@ -306,6 +306,7 @@
property name=build.resources value=${module.output}/resources/
property name=build.stylesheets value=${module.output}/stylesheets/
property name=build.reports value=${module.output}/reports/
+property name=build.testlog value=${module.output}/log/
!-- Install/Release structure --
property name=install.id value=${module.name}-${module.version}/
@@ -1462,6 +1463,7 @@
target name=tests-standard-unit depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1472,6 +1474,7 @@
jvmarg value=${junit.jvm.options}/
sysproperty key=jbosstest.deploy.dir file=${build.lib}/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
classpath
pathelement location=${build.classes}/
@@ -1500,6 +1503,7 @@
target name=tests-standard-stress depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1510,6 +1514,7 @@
jvmarg value=${junit.jvm.options}/
sysproperty key=jbosstest.deploy.dir file=${build.lib}/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
classpath
pathelement location=${build.classes}/
@@ -1544,6 +1549,7 @@
target name=tests-client-unit depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1554,6 +1560,7 @@
jvmarg value=${junit.jvm.options}/
sysproperty key=jbosstest.deploy.dir file=${build.lib}/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
jvmarg value=-Djava.security.manager/
sysproperty key=java.security.policy
@@ -1584,6 +1591,7 @@
target name=tests-client-stress depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1600,6 +1608,7 @@
value=${build.resources}/security/tst.policy/
sysproperty key=java.security.auth.login.config
value=${build.resources}/security/auth.conf/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
classpath
pathelement path=${build.lib}/jrmp-dl-client.jar/
@@ -1630,6 +1639,7 @@
target name=tests-security-basic-unit depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1647,6 +1657,7 @@
value=${build.resources}/security/tst.policy/
sysproperty key=java.security.auth.login.config
value=${build.resources}/security/auth.conf/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
classpath
pathelement location=${build.classes}/
@@ -1673,6 +1684,7 @@
target name=tests-security-basic-stress depends=jars
mkdir dir=${build.reports}/
+mkdir dir=${build.testlog}/
junit dir=${module.output}
printsummary=${junit.printsummary}
haltonerror=${junit.haltonerror}
@@ -1689,6 +1701,7 @@
value=${build.resources}/security/tst.policy/
sysproperty key=java.security.auth.login.config
value=${build.resources}/security/auth.conf/
+ sysproperty key=log4j.properties
file=${build.resources}/log4j.properties/
classpath
pathelement
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha HAPartitionImpl.java HAPartition.java DistributedReplicantManagerImpl.java
User: patriot1burke
Date: 01/09/17 21:15:10
Modified:src/main/org/jboss/ha HAPartitionImpl.java HAPartition.java
DistributedReplicantManagerImpl.java
Log:
work in progress. ClusterPartion is finally loadable and working
Revision ChangesPath
1.4 +62 -1 jbossmx/src/main/org/jboss/ha/HAPartitionImpl.java
Index: HAPartitionImpl.java
===
RCS file: /cvsroot/jboss/jbossmx/src/main/org/jboss/ha/HAPartitionImpl.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- HAPartitionImpl.java 2001/09/16 15:29:07 1.3
+++ HAPartitionImpl.java 2001/09/18 04:15:10 1.4
@@ -9,6 +9,7 @@
import JavaGroups.MethodLookup;
import JavaGroups.MethodLookupClos;
+import JavaGroups.MethodLookupJava;
import JavaGroups.MembershipListener;
import JavaGroups.MessageListener;
import JavaGroups.JChannel;
@@ -27,6 +28,14 @@
import java.util.Iterator;
import java.io.Serializable;
import javax.naming.InitialContext;
+import javax.naming.Reference;
+import javax.naming.StringRefAddr;
+import javax.naming.Name;
+import javax.naming.Context;
+import javax.naming.NamingException;
+import javax.naming.NameNotFoundException;
+import org.jboss.naming.NonSerializableFactory;
+import java.lang.reflect.Method;
import org.jboss.logging.Logger;
@@ -42,6 +51,33 @@
protected DistributedReplicantManagerImpl replicantManager;
protected String nodeName;
protected Logger log = null;
+
+ /*
+ protected class PIMethodLookup implements JavaGroups.MethodLookup
+ {
+ public Method FindMethod(Class target_class, String method_name, Vector args)
throws Exception
+ {
+ System.out.println(looking for method: + method_name + Class name:
+ target_class.getName());
+ Method retval=null, method;
+ Method[] methods=target_class.getMethods();
+ intnum_args=args.size();
+
+ // FIXME: Get funkier later.
+ for(int i=0; i methods.length; i++) {
+ method=methods[i];
+System.out.println(does method match? + method.getName());
+ if(method.getName().equals(method_name)
+method.getParameterTypes().length == num_args) {
+ return method;
+ }
+ }
+ System.out.println(method not found!);
+ throw new NoSuchMethodException();
+ }
+
+ }
+ */
+
final MethodLookup method_lookup_clos=new MethodLookupClos();
public HAPartitionImpl(String partitionName, JChannel channel,
@@ -66,7 +102,31 @@
log.info(init replicant manager);
this.replicantManager.init();
log.info(bind replicant manager);
- new InitialContext().bind(/HAPartition/ + partitionName, this);
+
+ Context ctx = new InitialContext();
+ String jndiName = /HAPartition/ + partitionName;
+ // Ah ! Session isn't serializable, so we use a helper class
+ NonSerializableFactory.bind(jndiName, this);
+ Name n = ctx.getNameParser().parse(jndiName);
+ while (n.size() 1)
+ {
+ String ctxName = n.get(0);
+ try
+ {
+ctx = (Context)ctx.lookup(ctxName);
+ }
+ catch (NameNotFoundException e)
+ {
+log.info(creating Subcontext + ctxName);
+ctx = ctx.createSubcontext(ctxName);
+ }
+ n = n.getSuffix(1);
+ }
+ // The helper class NonSerializableFactory uses address type nns, we go on to
+ // use the helper class to bind the javax.mail.Session object in JNDI
+ StringRefAddr addr = new StringRefAddr(nns, jndiName);
+ Reference ref = new Reference(HAPartitionImpl.class.getName(), addr,
NonSerializableFactory.class.getName(), null);
+ ctx.bind(n.get(0), ref);
log.info(done initing..);
}
@@ -125,6 +185,7 @@
if (!excludeSelf)
{
+ m.SetName(methodName);
Object handler = rpcHandlers.get(objName);
Object retval=m.Invoke(handler, method_lookup_clos);
if (retval != null) rtn.add(retval);
1.2 +3 -2 jbossmx/src/main/org/jboss/ha/HAPartition.java
Index: HAPartition.java
===
RCS file: /cvsroot/jboss/jbossmx/src/main/org/jboss/ha/HAPartition.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HAPartition.java 2001/09/14 03:53:29 1.1
+++ HAPartition.java 2001/09/18 04:15:10 1.2
@@ -15,7 +15,7 @@
{
// General methods
//
- public String getNodeName ();
+ public String getNodeName();
public String getPartitionName();
public
