Hello Scott,
> I've looked into this bug using a simple RMI client/server testcase that
> simulates the behavior in JBoss in that the remote objects it exports
> are loaded by an application class loader. The fact that the annotated
> codebase of the class is a file url on the server is due to th
User: gropi
Date: 01/06/01 23:35:11
Modified:src/docs advconfig.xml
Log:
Update on Option D by Georg Rehfeld
Revision ChangesPath
1.11 +5 -5 manual/src/docs/advconfig.xml
Index: advconfig.xml
===
You may be using an old version of winzip. Try jar instead.
--- Ravindra Sharma <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I downloaded latest JBoss-2.2.2 Zip but when I expand zip file. It expands
> all the files with 0 (zero) size. It appears something is wrong with this
> file. Whereas JB
Hi folks,
I downloaded latest JBoss-2.2.2 Zip but when I expand zip file. It expands all the
files with 0 (zero) size. It appears something is wrong with this file. Whereas
JBoss-2.2.2_Tomcat-3.2.2.zip file expands fine.
-ravi
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROT
JBoss daily test results
SUMMARY
Number of tests run: 71
Successful tests: 50
Errors:10
Failures: 11
[time of test: 2 June 2001 2:48]
See http://lubega.com for f
My vote on the issue is turn the feature OFF by default.
A JMS queue is like a database table: I don't want the thing getting
created and destroyed every time I deploy and undeploy a bean. This is
mainly doe to the time indepenent processing "feature" JMS usually gives
you. If you are creating
|you make too many, and they're repetitive and become boring :)
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
repetition works, Juha
rep
|This effectively means that classes that are to be downloaded to
|clients must
|be on system classpath. The only solution short of resorting to use of the
|internal
|sun.rmi.server.LoaderHandler.registerCodebaseLoader(ClassLoader) method
|is to write a URLClassLoader that can handle funky urls
On Fri, 1 Jun 2001, marc fleury wrote:
> to clear fuck-ups... yet if you screw up it doesn't hide the mistake, your
> application won't work.
yes... but I want to know exactly *WHY* it doesn't work :)
> |I'd much rather see the lookup fail than have the server hide my fuck ups.
> |Because that
I need to add the code to remove the queue ad undeploy.
I can also make the message really huge when creating a new topic/queue.
Is there anything else I should do while I got the patient open?
d.
-Original Message-
From: marc fleury [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 01, 20
I've looked into this bug using a simple RMI client/server testcase that
simulates the behavior in JBoss in that the remote objects it exports
are loaded by an application class loader. The fact that the annotated
codebase of the class is a file url on the server is due to the fact that
this is th
User: starksm
Date: 01/06/01 15:08:46
Added: src/main/test/jboss/jrmp AString.java Client.java
Handler.java IRemote.java IString.java
MiniAppServer.java RemoteImpl.java
Log:
Simple tests of dynamic class loading for RMI/JRMP
Re
User: starksm
Date: 01/06/01 15:07:45
jboss/src/main/test/jboss/jrmp - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
|It will be trial to remove the topic/queue at undeployment,
|if and only if I added it at deploy time
Which is exactly what I am arguing for, glad to see it already coded. If no
topic, create and destroy at deployment boundaries. This enables the "I
listen to the topic as an MDB the server
On Fri, 1 Jun 2001, Ferguson, Doug wrote:
> It will be trial to remove the topic/queue at undeployment,
> if and only if I added it at deploy time
ok..
> We already display a message at deploytime that says that
> the queue/topic doesn't exist. So it isn't really correct
> that the serve
|> 2- If you miss the spelling.. we should put a message saying "Creating
|> topic" and that's it.. very convenient.
|
|In this case, no, its not very convenient in my opinion. My application
|won't work since the MDB is subscribed to the wrong topic. So why bother
|deploying it at all. It's not g
|Ok, I'm fine with this being an optional behavior. I'm not fine with that
|being the only way it is.
I agree. It should be labeled as default-city. JBoss only.
If you specify all the bells and whistles then of course we will find the
topic in JNDI and use it... J2EE standard.
marcf
|
|- O
It will be trial to remove the topic/queue at undeployment,
if and only if I added it at deploy time
This way the config file won't "build up"...
We already display a message at deploytime that says that
the queue/topic doesn't exist. So it isn't really correct
that the server hides your fuc
Ok, I'm fine with this being an optional behavior. I'm not fine with that
being the only way it is.
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2001 2:20 PM
Subject: RE: [JBoss-dev] JMSContainerInvoker.java
> |Its not redu
On Fri, 1 Jun 2001, marc fleury wrote:
> 1- If it is not there, right now we have to manually go and create the damn
> thing, very redundant.
> 2- If you miss the spelling.. we should put a message saying "Creating
> topic" and that's it.. very convenient.
In this case, no, its not very conveni
|Its not redundant as there are many provider specific properties
|that an admin
|has to set: security, clustering, etc. You don't create database
|connection pools
|automatically because there are too many provider specific options that an
|admin familiar with the database has to set. In general
Its not redundant as there are many provider specific properties that an admin
has to set: security, clustering, etc. You don't create database connection pools
automatically because there are too many provider specific options that an
admin familiar with the database has to set. In general the sa
Scott M Stark wrote:
> But your change works fine in the 2.2.2 codebase as I ran the same testsuite
> against it before making the release and I reran it today and it does not show
> the same errors. Is there a difference in the code comitted to the 2.2.2 branch
> versus main?
Thank you. I was
WTF... the create the MDB topic on deployment if not present?
I think it is a kick ass feature...
let me explain:
1- If it is not there, right now we have to manually go and create the damn
thing, very redundant.
2- If you miss the spelling.. we should put a message saying "Creating
topic" and
Bugs item #429397, was updated on 2001-06-01 11:28
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=429397&group_id=22866
Category: JBossServer
Group: v2.2.2 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: John Munsch (johnmunsch)
Assigned
But your change works fine in the 2.2.2 codebase as I ran the same testsuite
against it before making the release and I reran it today and it does not show
the same errors. Is there a difference in the code comitted to the 2.2.2 branch
versus main?
The tests typically run against the DefaultDS wh
Sreeram,
If you can look at this, it's probably related to some "instanceof
MarshalledObject" checking that I just added. This is probably leading
us into the wrong bit of logic somewhere.
This _might_ also be dependent somewhat on the database you're running
against - This code doesn't like p
This is probably (almost without a doubt) related to the change I
committed recently. What database are you running the tests against?
Scott M Stark wrote:
> I have rerun the jbosstest suite and I am also seeing errors on tests that worked a
> couple of days ago. Most of the new errors are comp
Hi there,
-Ursprüngliche Nachricht-
>Von: marc fleury [mailto:[EMAIL PROTECTED]]
>Gesendet: Mittwoch, 30. Mai 2001 20:20
>An: [EMAIL PROTECTED]
>Betreff: RE: Inital Checkin of J2eeGlobalScopeDeployer was AW:
>[JBoss-dev] CVS update:
>Hey,
>JBoss world tour is over... back to home base
Start by tracking down the current tracking down the current cmp errors
seen in the bank module of the jbosstest suite. There's nothing like
jumping into the deep end off of the high dive from the start.
- Original Message -
From: "K S Sreeram" <[EMAIL PROTECTED]>
To: "Juha Lindfors" <[E
Get the jbosstest cvs module and look at the current unit test cases. Most
likely this can be added to the dbtest testsuite which is under:
jbosstest/src/main/org/jboss/test/dbtest
- Original Message -
From: "Ferguson, Doug" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June
I have reasonable experience with database related programming. I would love
to help in the jboss-cmp engine, but i have no idea where to begin.. perhaps
you or somebody else can guide me on where to begin regarding the jboss-cmp
engine
Regards
KS
On Friday 01 June 2001 22:02, you wrote:
> Hi
Hi
I am an experienced java and j2ee developer. I am very interested in
contributing to the jboss project. As i am not sure where i can fit in, i
would be grateful if somebody can help and give me directions on what i can
code... I mailed [EMAIL PROTECTED], expressing my interest, but i
haven
I just commited the container configuration commit option d
and I should probably add some test cases for commit option d.
Who can point me in the right directrion for the daily tests?
d.
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lis
I have rerun the jbosstest suite and I am also seeing errors on tests that worked a
couple of days ago. Most of the new errors are complaints about not being able to
load a ResultSet column due to an EOFException like that shown below. The corresponding
server log exception follows and shows the p
poo poo!
;-D
--Juha
At 07:08 1.6.2001 -0700, you wrote:
>This is something that was suggested at the Atlanta training and Marc
liked so
>you need to slap him around. I was not particularly in favor of it and
that seems
>to be the general feeling so let's roll the change back.
>
>- Original
User: starksm
Date: 01/06/01 07:08:49
Modified:src/build/subprojects build-web.xml
Log:
Update the web integration test for resource access
Revision ChangesPath
1.5 +3 -0 jbosstest/src/build/subprojects/build-web.xml
Index: build-web.xml
==
User: starksm
Date: 01/06/01 07:08:49
Modified:src/main/org/jboss/test/web/util Util.java
Log:
Update the web integration test for resource access
Revision ChangesPath
1.2 +19 -1 jbosstest/src/main/org/jboss/test/web/util/Util.java
Index: Util.java
User: starksm
Date: 01/06/01 07:08:49
Modified:src/resources/web/WEB-INF web.xml
Log:
Update the web integration test for resource access
Revision ChangesPath
1.7 +4 -0 jbosstest/src/resources/web/WEB-INF/web.xml
Index: web.xml
User: starksm
Date: 01/06/01 07:08:49
Modified:src/main/org/jboss/test/web/servlets DebugServlet.java
EJBOnStartupServlet.java
Log:
Update the web integration test for resource access
Revision ChangesPath
1.2 +10 -1 jbosstest/src/main/o
This is something that was suggested at the Atlanta training and Marc liked so
you need to slap him around. I was not particularly in favor of it and that seems
to be the general feeling so let's roll the change back.
- Original Message -
From: "Juha-P Lindfors" <[EMAIL PROTECTED]>
To: <
Ok. What you have is fine.
- Original Message -
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2001 12:53 AM
Subject: Re: [JBoss-dev] jboss daily build failed - in cvs module: jbosssx
> Hi,
>
> The problem is that I have no dependency checking
I think, I've added it into the CVS tree for 2.3 to support Tyrex
DTM. Perhaps, we should move all the Tyrex-related jars into a separate
optional entry in class-path extensions.
I was hoping to wait till the new class loading infrastructure is in place
in Rabbit in the Hole (or whatever the co
Hi,
Just re-ran the tests - it now compiles - but we have 17 new test failures!
Chris
>
>
> JBoss daily test results
>
> SUMMARY
>
> Number of tests run: 71
>
>
>
> Successful tests: 50
>
> Errors:10
>
> Failures:
On Fri, 1 Jun 2001, Peter Antman wrote:
>
> You see what will happen? Yes, the client will send its messages to one
> topic (no automatic creation here), and the MDB will listen on ANOTHER
> topic, namely a to the system unknown destination, since it was not
> correctly spelled.
>
> What do you
Hi,
The problem is that I have no dependency checking between modules - so if
the core jboss build fails, then so will this build - since its dependency
is not met...
Usually this works...
I guess I could make the build stop on the first error - but then if there
are errors in a non-dependant m
User: thedug
Date: 01/06/01 00:50:23
Modified:src/main/org/jboss/metadata ConfigurationMetaData.java
Log:
Added support for reading from jboss.xml
Also added accessor methods for this value (getOptionDRefreshRate)
Revision ChangesPath
1.13 +21 -5 jboss/src/
User: thedug
Date: 01/06/01 00:44:52
Modified:src/main/org/jboss/ejb/plugins
EntitySynchronizationInterceptor.java
Log:
Added support for commit option D dynamically configured refresh rate
Revision ChangesPath
1.33 +11 -11
jboss/src/ma
User: thedug
Date: 01/06/01 00:42:10
Modified:src/resources/org/jboss/metadata jboss.dtd
Log:
Added commit option D
Also added the tag
Revision ChangesPath
1.8 +12 -2 jboss/src/resources/org/jboss/metadata/jboss.dtd
Index: jboss.dtd
Hi,
I would have to agree with Peter on this one. I believe this goes
against the spirit of the JMS spec, where JMS destinations are to be
created EXPLICITLY using a vendor-defined administration interface.
Having your app silently create destinations brings up nightmarish
visions
of BAD THINGS HA
Hi alls!
Why there is castor-0.9.1 in lib/ext?
This jar is added in the common classloader path and so when I try to
deploy and redeploy my castor RAR module I have problems to reinitialize
castor (reloading the new DB mapping).
Another problems...
Is it possible to separate the common classlo
51 matches
Mail list logo
