Hi,
I was reading the critique of JSR47:
http://jakarta.apache.org/log4j/docs/critique.html
and noticed this paragraph, in the Other Differences section;
Note that any third-party implementation using the java.* or
javax.* namespaces violates Sun's trademark on Java. Without explicit
Scott
there is an error in the jboss 2.4 dtd.
The SingletonStatelessSessionInstancePool class in org.jboss.ejb.plugins
has a boolean attribute isSynchronized that is set by an XML element
'Synchronized' in the container-pool-conf.
So :-
!ELEMENT container-pool-conf (MaximumSize ,
User: gropi
Date: 01/06/29 03:44:55
Modified:src/docs howtojavamail.xml
Log:
JBoss 2.2.2 compliance updates by Francois Charoy
Revision ChangesPath
1.5 +208 -226 manual/src/docs/howtojavamail.xml
Index: howtojavamail.xml
User: gropi
Date: 01/06/29 03:44:56
Modified:src/examples/build build.xml
Log:
JBoss 2.2.2 compliance updates by Francois Charoy
Revision ChangesPath
1.10 +161 -139 manual/src/examples/build/build.xml
Index: build.xml
User: gropi
Date: 01/06/29 03:44:56
Added: src/examples/org/jboss/docs/javamail Mailer.java
MailerBean.java MailerHome.java MailerServlet.java
application.xml build.xml ejb-jar.xml home.html
jboss-web.xml
Hi,
My firebird resource adapter is at firebird.sourceforge.net cvs under
client-java. I'm checking in my latest version which can build a rar that
jboss deploys, it will create tables via jaws, but then crashes. It works
ok with my test cases though!
Any input on it gratefully appreciated.
What does it do? Is it providing XA Connections for firebird?
Cheers
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 11:37 AM
To: [EMAIL PROTECTED]
Subject: RE: Isolation Levels was RE: [JBoss-dev] CVS update:
jboss/src/ma
On 27 Jun, Jason Dillon wrote:
Hey, I had to stop playing with build systems and get some actual work done.
I was finishing up integrating the JMS RA support, so my application has
better JMS/EJB TX integration and I started getting messages like the
snippet below. The application seems to
I updated the dtd in main and 2.4
- Original Message -
From: Mike Swainston-Rainford [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Scott M Stark [EMAIL PROTECTED]
Sent: Friday, June 29, 2001 3:06 AM
Subject: [JBoss-dev] jboss_2_4.dtd - take 2
Scott
there is an error in the jboss 2.4
User: starksm
Date: 01/06/29 11:13:14
Modified:src/resources/org/jboss/metadata Tag: Branch_2_4
jboss_2_4.dtd
Log:
Update container-pool-conf content model to:
((MaximumSize , MinimumSize) | Synchronized)
and add Synchronized element
Revision
Hi,
yes, as far as I can tell from my unit tests xa works fine (I don't have
Recover implemented yet, but should be easy).
My unit tests have most features needed working, however as noted it
doesn't yet work well with jboss. Also remember this is kind of pre-alpha,
for instance it logs all low
Alright,
This might sound a bit naive but do we need a little simple gui that one can use
to shut down JBoss or restart it? When you run JBoss on the command line in Unix
as a background process [./run.sh] it spawns loads of java processes that
need to be killed. Is there a cleaner way to
On Fri, 29 Jun 2001, Bill Burke wrote:
You can shut it down very easy from the JMX interface. Starting up is a
different story.
Last time I tried this, it unloaded all the beans and services,
but did not actually cause the JVM to exit, so JBoss was still taking a
boatload of system
Yo Dain,
I know absolutely nothing about CMP 2.x Relationships, but it makes me
really worried that you are working directly with EntityEnterpriseContexts
from the container.cache. Why aren't you going through the HOME interfaces
to access related beans? Remember, each entity type can have
I would think you'd want to be out of the guts too, that just seems a bit
too closely coupled with JBoss for the persistence manager. Shouldn't the
CMP persistence manager be some type of layer on top (well almost on top)
with a well defined interface? This should clearly tie in to take
There are two classes for this:
org.jboss.jmx.client.Stop
org.jboss.Shutdown
I don't know how well they work. Shutdown just invokes the shudown
method on the Shutdown service which you can do using the JMS
html adaptor.
- Original Message -
From: Vinay Menon [EMAIL PROTECTED]
To: Dev @
Works great for me on Linux.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron
Mulder
Sent: Friday, June 29, 2001 2:56 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Shutting down JBoss
On Fri, 29 Jun 2001, Bill Burke wrote:
You
Bill,
Thanks for the reply. I really need other people thinking about this,
because I don't understand the rest of the container.
Here's the deal. I delegate the actual storage of the other updated
contexts to the their respective persistence storage managers, so they get
stored by correct
The first implementation of the read-ahead messed around with the caches
before I decided that I didn't like it and took that out.
-danch
Dain Sundstrom wrote:
Jay,
Great point. Up until I started on this code, no part of JBossCMP worked
with the other container objects (cache, invoker
The org.jboss.Shutdown works fine for me to shut down
JBoss also from /etc/init.d on SuSE Linux 7.1.
Andy
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 12:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Shutting down JBoss
Well,
Shutting down is on half of the story ain't it? You obviously want to
restart the server you shut down at some point of time! I'll try going thru
the these startup and shutdown classes and see if I can come up with
anything!
Thanks,
Vinay
PS: Thanks for the correcting the
And if anyone bothers to check it, can someone please go thru the multiple
datasources code I'd sent? It only makes sense to have it at a bean level -
cannot think of an enterprise app connecting to single database!
- Original Message -
From: Dain Sundstrom [EMAIL PROTECTED]
To: [EMAIL
Dain Sundstrom wrote:
Bill,
Thanks for the reply. I really need other people thinking about this,
because I don't understand the rest of the container.
Here's the deal. I delegate the actual storage of the other updated
contexts to the their respective persistence storage managers, so
Seems like it's always an interesting tradeoff of whether the code belongs
in some runtime code (persistence manager) or in the generated code (CMP
bean implementation)... I'm glad you're working on CMP 2.0, it will be good
to have that implemented or JBoss.
Cheers
-Original Message-
How do I get write access to the cvs repository?
Mikael Tollefsen
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
You demonstrate you know what your doing by submitting patches to
sourceforge and when the volume and/or quality justifies write access
Marc will approve it.
- Original Message -
From: Mikael Tollefsen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, June 29, 2001 1:41 PM
Subject:
The OIL (stands for Optimized Invocation Layer). Just means that we use a
custom socket level protocol to talk to the server. Every connection
established uses 2 sockets (#1 for the client to talked to the server, and
#2 for the server to 'push' async messages to the client). The seconds
Hi,
I've been rethinking lately how should the deployment architecture be
redesigned in JBoss for the future clustering support and, incidentally,
my personal project. The existence of JSR-77 which did not put out any
kind of draft yet would, possibly, make our lives more complicated in the
Hi,
I like the idea of being able to pass arbitrary contexts
with the invocation request.
I guess that it means we should agree to some context
naming convention.
Are you talking about org.jboss.ejb.MethodInvocation?
Why should that class be Serializable?
It is only used locally on the server.
I am currently running everything on the same machine. I am correct in
beliving that this would not be a bug in the JMS RA? I am just trying to
narrow the scope of the hunt for this problem.
Does anyone know if the EOFException in this case is an error or more of a
notification?
--jason
On
Thanks, I was having trouble finding this information. Is this documented
anywhere?
Do you have any clues about the EOFException problem that I am getting?
--jason
On Fri, 29 Jun 2001, Hiram Chirino wrote:
The OIL (stands for Optimized Invocation Layer). Just means that we use a
custom
I can build it just fine. Perhaps you have some extra fluff in your
classpath?
--jason
On Fri, 29 Jun 2001, danch wrote:
The last couple of days I've been unable to build the HEAD version from
CVS. It looks like yet another XML parser version mismatch (YAXPVM? OK,
that's we nobody has
The src/build/build.xml file says that xml.jar is only there to support ejx.
Is that true? Does anyone know if it is being used anywhere else? If not
lets get rid of it.
--jason
On Fri, 29 Jun 2001, danch wrote:
More info:
There's an old version of the xml APIs in the lib directory, in
JBoss daily test results
SUMMARY
Number of tests run: 86
Successful tests: 81
Errors:1
Failures: 4
[time of test: 30 June 2001 2:49]
See http://lubega.com for
What did you have to change in build.xml? It also looks like xml.jar is
referenced in conf/default/jboss.conf, but I am not sure that it is required
or... but I can't really tell if any of those codebase attributes are even
used really.
If xml.jar is old and it is not being used by anything,
User: danch
Date: 01/06/29 21:32:32
jbosstest/src/main/org/jboss/test/readahead/interfaces - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: danch
Date: 01/06/29 21:33:31
jbosstest/src/resources/readahead - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: danch
Date: 01/06/29 21:34:16
jbosstest/src/resources/readahead/META-INF - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: danch
Date: 01/06/29 21:38:05
Added: src/build/subprojects build-readahead.xml
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
1.1
User: danch
Date: 01/06/29 21:38:05
Modified:src/build build.xml
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
1.37 +7 -2
User: danch
Date: 01/06/29 21:38:06
Added: src/main/org/jboss/test/readahead/interfaces
AddressHome.java AddressPK.java AddressRemote.java
CMPFindTestEntityHome.java
CMPFindTestEntityRemote.java
User: danch
Date: 01/06/29 21:38:06
Added: src/resources/readahead client.policy jndi.properties
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
User: danch
Date: 01/06/29 21:38:06
Added: src/resources/readahead/META-INF ejb-jar.xml jaws.xml
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
User: danch
Date: 01/06/29 21:38:05
Added: src/bin readaheadtest.bat readaheadtest.sh
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
1.1
User: danch
Date: 01/06/29 21:38:06
Added: src/main/org/jboss/test/readahead/test Main.java
Log:
Added tests for readahead functionality. Note that this only checks to see if they
work: it doesn't verify that it's actually performing well
Revision ChangesPath
1.1
User: danch
Date: 01/06/29 21:32:14
jbosstest/src/main/org/jboss/test/readahead - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
46 matches
Mail list logo
