User: slaboure
Date: 01/11/20 00:48:44
Modified:javagroups/javagroups/lib JavaGroups.jar
Log:
Previous JAR didn't incorporated the JavaGroups/debug package which may be necessary
to some classes. Sorry!
Revision ChangesPath
1.3 +48 -28
User: starksm
Date: 01/11/20 01:20:07
Added: src/main/org/jboss/test/testbean/somepackage Tag: Branch_2_4
SomeClass.java
Log:
Move the class loading test target to under the org.jboss.test.testbean
package
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:20:07
Modified:src/main/org/jboss/test/testbean/bean Tag: Branch_2_4
StatelessSessionBean.java
Log:
Move the class loading test target to under the org.jboss.test.testbean
package
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:20:38
Modified:src/main/org/jboss/test/security/test Tag: Branch_2_4
TestEJBSpec.java
Log:
Remove the comment about the war deployer
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:18:53
jbosstest/src/main/org/jboss/test/testbean/somepackage - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: starksm
Date: 01/11/20 01:23:19
Modified:src/main/org/jboss/resource/security Tag: Branch_2_4
PrincipalMapping.java PrincipalMappingSupport.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:25:34
Modified:src/main/org/jboss/mq/server Tag: Branch_2_4
JBossMQService.java StateManager.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:25:34
Modified:src/lib Tag: Branch_2_4 jboss-j2ee.jar jboss-jaas.jar
jboss-jdbc_ext.jar jboss.jar
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
-Ursprüngliche Nachricht-
Von: Jason Dillon [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 19. November 2001 21:19
An: Bill Burke
Cc: marc fleury; Jboss-Development@Lists. Sourceforge. Net
Betreff: RE: [JBoss-dev] Ignorance
You do not need to have this
set unless you have modified a
User: starksm
Date: 01/11/20 01:25:34
Modified:src/main/org/jboss/mq/il/oil Tag: Branch_2_4
OILServerILService.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
User: starksm
Date: 01/11/20 01:21:46
Modified:src/build/subprojects Tag: Branch_2_4 build-testbean.xml
Log:
Move the class loading target to under the org.jboss.test.testbean package
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:23:19
Modified:src/main/org/jboss/resource Tag: Branch_2_4
ConnectionFactoryLoader.java
ConnectionManagerFactoryLoader.java
JBossConnectionListenerImpl.java
User: starksm
Date: 01/11/20 01:38:02
Modified:src/main/org/jboss/pool Tag: Branch_2_4 ObjectPool.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No revision
User: starksm
Date: 01/11/20 01:38:58
Modified:src/main/org/jboss/security/plugins Tag: Branch_2_4
JaasSecurityManagerService.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:38:59
Modified:src/main/org/jboss/security/srp Tag: Branch_2_4
SRPService.java SRPVerifierStoreService.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:48
Modified:src/main/org/jboss/deployment/scope Tag: Branch_2_4
Scope.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:42:48
Modified:src/main/org/jboss/configuration Tag: Branch_2_4
ConfigurationService.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
User: starksm
Date: 01/11/20 01:42:45
Modified:src/client Tag: Branch_2_4 jbossmq-client.jar
jbosssx-client.jar jnp-client.jar
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:45
Modified:src/etc/conf/default Tag: Branch_2_4 jboss.conf
log4j.properties
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:42:47
Modified:src/lib Tag: Branch_2_4 jboss-jaas.jar jbosscx.jar
jbossmq.jar jbosspool.jar jbosssx.jar jnpserver.jar
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:48
Modified:src/main/org/jboss/deployment Tag: Branch_2_4
DeployerMBeanSupport.java Installer.java
InstallerFactory.java J2eeDeployer.java
Log:
Change to the unified log4j based
User: starksm
Date: 01/11/20 01:42:51
Modified:src/main/org/jboss/ejb/plugins/jaws Tag: Branch_2_4
JAWSPersistenceManager.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:52
Removed: src/main/org/jboss/ejb/plugins/jrmp/interfaces Tag:
Branch_2_4 SecureSocketFactory.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
___
User: starksm
Date: 01/11/20 01:42:51
Modified:src/main/org/jboss/ejb/plugins/jaws/bmp Tag: Branch_2_4
CustomFindByEntitiesCommand.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:58
Modified:src/main/org/jboss/web Tag: Branch_2_4
AbstractWebContainer.java WebServer.java
WebService.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision
User: starksm
Date: 01/11/20 01:42:58
Modified:src/resources/org/jboss/metadata Tag: Branch_2_4
jboss-web.dtd
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:42:58
Modified:src/main/org/jboss/util/timeout Tag: Branch_2_4
TimeoutFactory.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
User: starksm
Date: 01/11/20 01:42:52
Modified:src/main/org/jboss/ejb/plugins/jrmp12/server Tag: Branch_2_4
JRMPContainerInvoker.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:57
Modified:src/main/org/jboss/util Tag: Branch_2_4
ClassPathExtension.java CounterService.java
Info.java MBeanProxy.java Scheduler.java
ServiceControl.java
User: starksm
Date: 01/11/20 01:42:52
Modified:src/main/org/jboss/ejb/plugins/jrmp/server Tag: Branch_2_4
JRMPContainerInvoker.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:52
Modified:src/main/org/jboss/ejb/plugins/jrmp13/server Tag: Branch_2_4
JRMPContainerInvoker.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:51
Modified:src/main/org/jboss/ejb/plugins/jaws/jdbc Tag: Branch_2_4
JDBCCommand.java JDBCCommandFactory.java
JDBCFindByCommand.java JDBCFindEntitiesCommand.java
User: starksm
Date: 01/11/20 01:42:52
Modified:src/main/org/jboss/ejb/plugins/lock Tag: Branch_2_4
BeanLockSupport.java MethodOnlyEJBLock.java
QueuedPessimisticEJBLock.java
SimplePessimisticEJBLock.java
Log:
User: starksm
Date: 01/11/20 01:42:53
Modified:src/main/org/jboss/jmx/client Tag: Branch_2_4
RMIClientConnectorImpl.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
User: starksm
Date: 01/11/20 01:42:53
Modified:src/main/org/jboss/jmx/server Tag: Branch_2_4
JMXAdaptorImpl.java JMXAdaptorService.java
RMIConnectorImpl.java RMIConnectorService.java
Log:
Change to the unified log4j based
User: starksm
Date: 01/11/20 01:23:18
Modified:src/build Tag: Branch_2_4 build.xml
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No revision
1.4.2.5 +1 -0
User: starksm
Date: 01/11/20 01:42:55
Modified:src/main/org/jboss/monitor Tag: Branch_2_4
BeanCacheMonitor.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No
User: starksm
Date: 01/11/20 01:42:53
Modified:src/main/org/jboss/jdbc Tag: Branch_2_4
HypersonicDatabase.java InstantDBDatabase.java
JDBCDataSourceLoader.java JdbcProvider.java
RawXADataSourceLoader.java
User: starksm
Date: 01/11/20 01:42:56
Modified:src/main/org/jboss/tm/plugins/tyrex Tag: Branch_2_4
ResourceInvoker.java TransactionManagerService.java
TyrexTransactionPropagationContextManager.java
User: starksm
Date: 01/11/20 01:42:54
Modified:src/main/org/jboss/management Tag: Branch_2_4
ContainerManagement.java ServerDataCollector.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:54
Modified:src/main/org/jboss/logging Tag: Branch_2_4 Log4jService.java
Logger.java
Removed: src/main/org/jboss/logging Tag: Branch_2_4
ConsoleLogging.java ConsoleLoggingMBean.java
User: starksm
Date: 01/11/20 01:42:56
Modified:src/main/org/jboss/tm/usertx/server Tag: Branch_2_4
ClientUserTransactionService.java
UserTransactionSessionImpl.java
Log:
Change to the unified log4j based org.jboss.logging.Logger
User: starksm
Date: 01/11/20 01:42:56
Modified:src/main/org/jboss/tm Tag: Branch_2_4
TransactionManagerService.java TxCapsule.java
TxManager.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision
User: starksm
Date: 01/11/20 01:49:01
Modified:tomcat/src/main/org/jboss/tomcat/security Tag: Branch_2_4
JBossSecurityMgrRealm.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No
User: starksm
Date: 01/11/20 01:42:54
Modified:src/main/org/jboss/logging/log4j Tag: Branch_2_4
CategoryWriter.java TracePriority.java
Removed: src/main/org/jboss/logging/log4j Tag: Branch_2_4
JBossCategory.java
Log:
Change to
User: starksm
Date: 01/11/20 01:42:56
Modified:src/main/org/jboss/proxy Tag: Branch_2_4 Proxies.java
ProxyProxy.java
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
User: starksm
Date: 01/11/20 01:49:00
Modified:tomcat/src/build Tag: Branch_2_4 build.xml
Log:
Change to the unified log4j based org.jboss.logging.Logger class.
Revision ChangesPath
No revision
No revision
1.15.2.8
User: starksm
Date: 01/11/20 01:54:19
Modified:catalina/src/main/org/jboss/web/catalina Tag: Branch_2_4
EmbeddedCatalinaServiceSX.java
EmbeddedCatalinaServiceSXMBean.java
Log4jLogger.java
Log:
Change to the
Another small question for Scott...
Are JBoss Realms scoped within a Server namespace, or
an Application ?
i.e. If 2 webapps see a Realm with the same name - is
it the same Realm instance ?
Currently I am working under the assumption that the
answer is no - but I'm open to suggestion.
JBoss security managers are not scoped. Every application referring to
the java:/jaas/domainX security manager is using the same instance and
executing the same JAAS login configuration. For the particular case of
two webapps referring to the same security domain via the jboss-web.xml
User: starksm
Date: 01/11/20 02:40:54
Removed: src/main/org/jboss/util Tag: Branch_2_4
CounterInterceptor.java
Log:
Move to the ejb/plugins package to limit cross package imports
___
Jboss-development mailing
User: starksm
Date: 01/11/20 02:41:18
Removed: src/main/org/jboss/logging Tag: Branch_2_4 LoggerMBean.java
Log:
The Logger is not an MBean anymore
___
Jboss-development mailing list
[EMAIL PROTECTED]
Thanks, Scott,
I'll do the necessary.
Jules
--- Scott M Stark [EMAIL PROTECTED]
wrote: JBoss security managers are not scoped. Every
application referring to
the java:/jaas/domainX security manager is using the
same instance and
executing the same JAAS login configuration. For the
dude,
I went to bed at 2 am with invoker madness in my head, but you are even
worse :)
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Tuesday, November 20, 2001 4:54 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] CVS
|The automatic serversion generation of RMI uses heavy reflection
|also on the
|method signatures
|and leads to CNFE´s in these cases.
So it is faster to include the serversion or not? I am thinking a lot about
ways to make these fast.
marcf
|
|CGJ
|
|
|
I guess, serversion is only computed once per VM class (ObjectStreamClass
is cached) ...
CGJ
-Ursprüngliche Nachricht-
Von: marc fleury [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 20. November 2001 16:24
An: Jung , Dr. Christoph; Jboss-Development (E-Mail)
Betreff: RE: [JBoss-dev]
Sacha Labourey wrote:
In RMI's Bible, hum, I mean Rickard's book,
Hehe, I was just reading the bible, I mean.. uhm, anyway.. to be sure.
It's always a good idea to do this, especially in such a controlled
environment as we have, with little need for allowing upgrades in the
system over
I unzipped 2.4.1 on our as400 v5r1 at work. The server runs without any
complaints.
Unfortunately I am a java newby. (don't stop reading now).
The as400 can compile java classes into native as400 byte code that runs
like lightning. What I would like to contribute is as/400 CL and RPG code to
Hi all --
Sorry for such a newbie question, but
Is there any place with jboss (working with rh) which stores data about
*all* pieces of an application deployment at runtime? For instance, I can
get the DeployedApplications attribute from the ContainerFactory MBean,
which gives me an
Uncle. It seems that JBOSS is designed assuming that it has full control
of creating tables. Well in my case I already have a database allready
set up so my view of things is how do I stuff this database into JBOSS.
I don't think it is worth the discussion which approach is right or
wrong
This jar (junitejb.jar) is an ejb-jar file. JUnitEJB uses a session bean to
run the test cases on the serverside. There are about a billion ways to
package this. The three styles I have used follow:
* An ejb-jar with a class-path ref to junit.jar in the MANIFEST-MF.
* An ejb-jar with junit.jar
Ernst,
I'm not sure what your asking here.
You should be able to run the distribution from QSH.
DISCLAIMER: I haven't done this myself! I don't own a AS/400.
I think you've done some of this, but I'll list it for completeness.
1) Build the distribution on your PC or Un*x machine
ant probably
Hi
Right now there is no more management information
available. But soon the implementation of JSR-77 should
provide you with the necessary informations.
Have fun - Andy
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 8:10 AM
Subject:
Yep, you fixed it. Thank you.
-David
On Sunday 18 November 2001 11:14pm, David Jencks wrote:
OK, I think I fixed the can't undeploy broken mbean problem, with a
testcase too. (in jmx/test/DeployServiceUnitTestCase).
Could you check and make sure I fixed the problem you were seeing?
Ernst,
Before you attempt to do what you suggest, I would suggest you first do
some analysis of your environment. There are some things that you need
to be aware of.
The first thing you need to do is determine if there is a performance
problem. What are your performance goals? What makes
User: d_jencks
Date: 01/11/20 10:35:31
Modified:src/xdocs/howto howtojetty.xml howtopetstore.xml
Removed: src/xdocs/howto howtojca.xml howtomssql.xml
Log:
Added Sybase ConnectionFactoryLoader example and removed 2.4-specific db
documentation.
Revision ChangesPath
User: d_jencks
Date: 01/11/20 10:35:30
Modified:src/xdocs jbossdocs.xml resource.xml
Removed: src/xdocs jdbc-database.xml
Log:
Added Sybase ConnectionFactoryLoader example and removed 2.4-specific db
documentation.
Revision ChangesPath
3.1 +2 -26
Uncle. It seems that JBOSS is designed assuming that it has
full control of creating tables.
This isn't really true. JBossCMP makes the assumption that if the table
structure is not specified the Application Deployer does not care what the
structure is, as long as it runs.
I strongly
thx -- i'll keep an eye out for it...
-jason
Andreas Schaefer [EMAIL PROTECTED]
11/20/2001 12:46 PM
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:
Subject:Re: [JBoss-dev] Application/Deployment Units
Hi
Right now there is no more management
Hi,
I've been observing some of the recent threads on the list and reflected
on my current project. Mark has mentioned something of the sort that j2ee
packaging sucks. I certainly agree.
Here is what seems to be a better design that is consistent with JBoss
philosophy. Please, don't flame,
Bugs item #483847, was opened at 2001-11-20 08:42
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=483847group_id=22866
Category: JBossCMP
Group: v2.5 Rabbit Hole (unstable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas
We have just noticed that whenever our code throws a SQLException,
the connection pool continues to grow. Apparently the connections
that get invalidated aren't ever cleaned up. These grow until Oracle
bails. I am looking at ObjectPool right now to see if I can figure it out.
If anybody
User: schaefera
Date: 01/11/20 12:46:15
Modified:src/main/org/jboss/deployment Tag: Branch_2_4
URLWizzard.java
Log:
Fixed bug #456467 by not adding a '/' when file in the root directory to
go along with JAR tool.
Revision ChangesPath
No
Title: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? (Postgres and CMP 2)
that
is not true
marcf
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Bunker, DanSent: Tuesday, November 20, 2001 9:59
AMTo: JBoss DevSubject: RE: [JBoss-dev]
User: user57
Date: 01/11/20 13:34:48
Modified:src/docs/developers cvs.jsp
Log:
o removed jboss-website (and website alias) from the public module list
o changed [zip] [tgz] button style back to previous form, since they
were easier on the eye.
Revision Changes
Please let me know if you think that the build system is too complicated, or
if there is some part of the system which is too complicated.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
So it appears that the ConnectionInPool is getting removed from the pool
but is inner connection is never getting closed.
I am thinking that the best approach is to obtain the JDBC connection
by calling getUnderlyingConnection. then call close() on that connection
If I get the ok. I will do
User: schaefera
Date: 01/11/20 13:43:53
Modified:src/main/org/jboss/deployment URLWizzard.java
Log:
Took the fix for bug #456467 in current CVS.
Revision ChangesPath
1.9 +8 -2 jboss/src/main/org/jboss/deployment/URLWizzard.java
Index: URLWizzard.java
Bugs item #435463, was opened at 2001-06-22 07:10
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=435463group_id=22866
Category: JBossTX
Group: v2.2.2 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to:
User: d_jencks
Date: 01/11/20 14:15:23
Modified:src/etc/conf/default hsqldb-default-service.xml
Log:
Added some warning comments about the anonymous mbean-ref to hsqldb
Revision ChangesPath
1.5 +5 -1 jboss/src/etc/conf/default/hsqldb-default-service.xml
I'm having a (related?) issue. When I hot-redeploy several times I end up
with no available connections on mysql and the ear cannot deploy. My app
only uses CMP, and even if I call no bean and only redeploy three or four
times I get the same error. I have to bounce the server back. No problem
On 2001.11.20 16:37:28 -0500 Ferguson, Doug wrote:
So it appears that the ConnectionInPool is getting removed from the pool
but is inner connection is never getting closed.
I am thinking that the best approach is to obtain the JDBC connection
by calling getUnderlyingConnection. then call
I updated about 20 minutes ago and it works fine for me.
-dain
-Original Message-
From: Dave Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 4:58 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] Current CVS build.
When running a JBOSS build from CVS Nov 20,
User: thedug
Date: 01/11/20 15:48:44
Modified:src/main/org/jboss/pool/connector Tag: Branch_2_4
ManagedConnectionPoolFactory.java
Log:
factory.destroy is now implemented to destroy the managed connection.
Revision ChangesPath
No
I agree that we need to much better notion of what constitutes an
application
deployment, and I would generalize this into the concept of application
domains. Not that your necessarily implying this, but focusing on a single
XML file as the centerpiece is not a fundamental design criterion. I'm
Bugs item #456467, was opened at 2001-08-29 03:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=456467group_id=22866
Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Peter Antman (pra)
Assigned to: Andreas
It has often seemed to me that there is substantial duplication between the
setup parts of the module level build.xml files. I sure haven't figured
out a clue of a way to reduce this, but if it could be done, it might make
the files a little less intimidating. In light of the vast improvement
Here is a dtd that may work for jbosscmp-jdbc, based on a large example
Dain sent me.
Except for a couple of description typos, the psgml parser apparently
not liking empty elements and one question, I think it agrees with the doc
Dain sent. 2 things:
- There is one
I have not found an easy way to provide this common setup/initialization
stuff as a resource. Perhaps if I could tell the JAXP parser to read a
resource file when parsing this could be done, but that would require the
Ant entity hooks to be installed to handle that.
Perhaps they have done
User: user57
Date: 01/11/20 18:42:55
Modified:src/docs/common picateam.jsp
Log:
o randomly setting the image alignment to left or right to spice up
things a little bit more =)
Revision ChangesPath
1.4 +6 -5 newsite/src/docs/common/picateam.jsp
Bugs item #456467, was opened at 2001-08-29 03:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=456467group_id=22866
Category: JBossServer
Group: None
Status: Closed
Resolution: Fixed
Priority: 3
Submitted By: Peter Antman (pra)
Assigned to: Andreas
JBoss daily test results
SUMMARY
Number of tests run: 188
Successful tests: 150
Errors:25
Failures: 13
[time of test: 21 November 2001 3:12 GMT]
[java.version:
User: user57
Date: 01/11/20 19:21:09
Modified:src/docs/developers cvs.jsp head.jsp index.jsp main.css
navigation.jsp slogan.jsp
Added: src/docs/developers webstyle.jsp
Log:
o consolidated common styles from /developers into /main.css
only
User: user57
Date: 01/11/20 19:21:09
Modified:src/docs head.jsp index.jsp main.css navigation.jsp
slogan.jsp
Added: src/docs printable.css
Log:
o consolidated common styles from /developers into /main.css
only specifying those colors that
User: user57
Date: 01/11/20 19:42:08
Modified:src/docs printable.css
Log:
o forgot to save file before commit =(
Revision ChangesPath
1.2 +5 -0 newsite/src/docs/printable.css
Index: printable.css
JBoss daily test results
SUMMARY
Number of tests run: 188
Successful tests: 152
Errors:24
Failures: 12
[time of test: 21 November 2001 3:59 GMT]
[java.version:
Bugs item #456467, was opened at 2001-08-29 03:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=456467group_id=22866
Category: JBossServer
Group: None
Status: Closed
Resolution: Fixed
Priority: 3
Submitted By: Peter Antman (pra)
Assigned to: Andreas
Here is a dtd that may work for jbosscmp-jdbc, based on a
large example
Dain sent me.
Except for a couple of description typos, the psgml parser
apparently
not liking empty elements and one question, I think it agrees
with the doc
Dain sent. 2 things:
- There is one
Hi All, well Hi David Jencks mostly I guess ;-),
With the new deployment system I have started deploying my application by
simply deploying the *service.xml file and including all the jars it uses in
a classpath / element.
This works very well, I can easily keep all my jars together in a lib
User: schaefera
Date: 01/11/20 20:50:54
Modified:sun/jsr77/lib jsr77.jar
Log:
Added a Node to JSR-77 implementation and added the mbean example to
jboss-service.xml to test it.
Revision ChangesPath
1.4 +8 -7 thirdparty/sun/jsr77/lib/jsr77.jar
1 - 100 of 125 matches
Mail list logo
