If there isn't a bug for it now, please make one. Easier to track ya know...
--jason
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10170
___
Jboss-development mailing
We should also include the JMX HTML adapter, so users can get some
feedback that it works.
--jason
marc fleury wrote:
yes I think we need to show the netboot thing. It is under most people's
radar.
What I would like to do is adopt a rabbit directly from our website. So
they download a
Guys,
CSIRO is publishing a performance comparison report among application
servers. They provide the JBoss test results for free at:
http://www.cmis.csiro.au/adsat/jboss.htm
Enjoy.
HJP
___
Jboss-development mailing list
[EMAIL PROTECTED]
yes,
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Tuesday, March 05, 2002 12:25 AM
|To: marc fleury
|Cc: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] org.jboss.deployment.scanner.DeploymentScanner
|
|
|We should also
I'm forwarding this to Jetty-discuss...
Jules
--- Giorgio42 [EMAIL PROTECTED] wrote:
I have the same problem.
If none of the developers respond, this should
become a bug ticket on SourceForge.
Georg
_
View thread online:
Thanks for the patch Neale, works well.
Why did you think stateless session beans should
support createMETHOD? ;-)
Last night I completed the work to the verifier and the
container so the correct behaviour is observed
for EJB1.1
I tried to commit it, but I think the hotel where I'm
staying must
On Tue, Mar 05, 2002 at 08:07:26AM -0600, Adrian Brock wrote:
Thanks for the patch Neale, works well.
Why did you think stateless session beans should
support createMETHOD? ;-)
Ooops... I was obviously coding in autopilot mode
Obviously passing args in is probably pointless for SLSB's,
It is excluded for stateless beans, at least I read it
that way. :-)
If you look at the life-cycle diagram it only mentions
create().
I agree the spec is not very definite. When it talks about Session beans in general it
includes createMethod,
but when it talks about stateless it does not.
Hmmm, I think everyone agrees it's a stupid thing to do, I guess they
forgot to state this explicitly in the spec!!
On Tue, Mar 05, 2002 at 11:04:37AM -0600, Adrian Brock wrote:
It is excluded for stateless beans, at least I read it
that way. :-)
If you look at the life-cycle diagram it
User: ejort
Date: 02/03/05 10:41:48
Modified:src/main/org/jboss/ejb/plugins BMPPersistenceManager.java
CMPPersistenceManager.java
StatefulSessionFilePersistenceManager.java
Log:
Add support for createMETHOD
Revision Changes
User: ejort
Date: 02/03/05 10:44:24
Modified:src/main/org/jboss/verifier/strategy AbstractVerifier.java
EJBVerifier11.java EJBVerifier20.java
VerificationContext.java
Log:
Add support for createMETHOD and add a warning that the V2
User: ejort
Date: 02/03/05 10:41:47
Modified:src/main/org/jboss/ejb EntityContainer.java
StatefulSessionContainer.java
Log:
Add support for createMETHOD
Revision ChangesPath
1.71 +15 -6
I've commited the changes. I'm going to hang around
for about an hour to make sure the hourly compile
doesn't blow up ;-)
I haven't committed the testsuite changes yet,
depends which version you want.
Regards,
Adrian
Thanks for the patch Neale, works well.
Why did you think stateless
Hehe,
I've found a bug in sourceforge.
I accidently moved this change note to patches and it
won't let me move it back again :-)
Regards,
Adrian
Change Notes item #526086, was opened at 2002-03-05
19:35
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=38117
Bugs item #493188, was opened at 2001-12-14 06:00
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=493188group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Henri Chen (henrichen)
Assigned
Hi,
a clean checkout from cvs indicates that build is broken.
You van build one, but not more without having to do the complete cycle
(build clean, build):
compile-mbean-sources:
[xdoclet] Generating Javadoc
[xdoclet] Javadoc execution
[xdoclet] Loading source file
Very odd (I am not seeing this). I will do a checkout and double check
this. What system/ javadoc are you using? Is
tools/etc/xdoclet/templates/mbean-custom.j present? Could you be a little
more clear on exactly what works and what doesn't?
Thanks
david jencks
On 2002.03.05 16:19:01 -0500
Change Notes item #526087, was opened at 2002-03-05 19:39
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=526087group_id=22866
Category: JBossServer
Group: v3.0 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to:
Change Notes item #526086, was opened at 2002-03-05 19:35
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=526086group_id=22866
Category: JBossServer
Group: v3.0 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to:
I can't reproduce this with a clean checkout.
build/build.sh
build/build.sh clean
build/build.sh
all work fine.
Linux 2.4.16
sun jdk 1.3.1
david jencks
On 2002.03.05 16:19:01 -0500 Peter Antman wrote:
Hi,
a clean checkout from cvs indicates that build is broken.
You van build one, but
+1 (Just did a fresh checkout and built everything with no problems.)
Francisco
On Tue, 5 Mar 2002, David Jencks wrote:
I can't reproduce this with a clean checkout.
build/build.sh
build/build.sh clean
build/build.sh
all work fine.
Linux 2.4.16
sun jdk 1.3.1
david jencks
On
Alexander,
Which methods don't get changed?
getRequestURI used to change with a forward, but now does not. This
is according to the spec.
getServletPath and getPathInfo are definitely working for me.
getParameter has always been a little problematic and I would
not be surprized if there was
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 474
Errors:27
Failures: 5
[time of test: 6 March 2002 0:29 GMT]
[java.version:
User: jules_gosnell
Date: 02/03/05 16:45:39
Modified:jettyFAQ
Log:
update
Revision ChangesPath
1.3 +59 -4 contrib/jetty/FAQ
Index: FAQ
===
RCS file: /cvsroot/jboss/contrib/jetty/FAQ,v
User: jules_gosnell
Date: 02/03/05 16:34:34
Modified:jetty/src/main/org/jboss/jetty/util NaiveTimeOutManager.java
Log:
ensure that timeOut() and timeRemaining() are run with the same
ContextClassLoader as TimeOut was registered with.
Revision ChangesPath
1.10 +14
User: jules_gosnell
Date: 02/03/05 16:36:30
Modified:jettyTODO
Log:
update
Revision ChangesPath
1.14 +11 -6 contrib/jetty/TODO
Index: TODO
===
RCS file:
User: schaefera
Date: 02/03/05 17:07:46
Modified:.build.xml
Log:
Added some new JSR-77 components written by Scott McLaughlin adding
JCA, JMS and ResourceAdaptor as JSR-77 components.
I also added a new test to see how XMBean and the newest version of
XDoclet can be
User: schaefera
Date: 02/03/05 17:07:50
Modified:lib xdoclet.jar
Log:
Added some new JSR-77 components written by Scott McLaughlin adding
JCA, JMS and ResourceAdaptor as JSR-77 components.
I also added a new test to see how XMBean and the newest version of
XDoclet can be
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 474
Errors:27
Failures: 5
[time of test: 6 March 2002 1:7 GMT]
[java.version:
User: schaefera
Date: 02/03/05 17:07:50
Modified:varia/src/main/org/jboss/mail MailService.java
Log:
Added some new JSR-77 components written by Scott McLaughlin adding
JCA, JMS and ResourceAdaptor as JSR-77 components.
I also added a new test to see how XMBean and the newest
User: schaefera
Date: 02/03/05 17:07:46
Modified:src/main/org/jboss/resource ConnectionFactoryLoader.java
ConnectionManagerFactoryLoader.java
RARDeployer.java
Log:
Added some new JSR-77 components written by Scott McLaughlin adding
User: schaefera
Date: 02/03/05 17:07:47
Modified:src/main/org/jboss/management/j2ee J2EEDeployedObject.java
J2EEServer.java
Added: src/main/org/jboss/management/j2ee J2EEDomainTarget.java
JCAConnectionFactory.java
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 475
Errors:27
Failures: 4
[time of test: 6 March 2002 1:45 GMT]
[java.version:
Adrian or David,
ok I know I am on shaky grounds to raise a flag (heck I broke the build for
a week) but it seems that one of your builds just broke the tests and we
have 20 more testst that fail since yesterday.
Can you guys double check with the testsuite?
marcf
All of the new errors are in the org.jboss.test.cmp2.relationship package,
and all are NPEs in the unit test code. One example stack trace is:
N/A
java.lang.NullPointerException
at
org.jboss.test.cmp2.relationship.oneToOneBidirectional.ABTest.beforeChange(A
BTest.java:85)
at
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 475
Errors:27
Failures: 4
[time of test: 6 March 2002 2:45 GMT]
[java.version:
I'm looking into it.
-dain
Scott M Stark wrote:
All of the new errors are in the org.jboss.test.cmp2.relationship package,
and all are NPEs in the unit test code. One example stack trace is:
N/A
java.lang.NullPointerException
at
It appears the the createMethod patch has broken create for CMP 2
entities. Now create always returns null. Was the testsuite run before
this patch was committed?
I'll see if I can fix it.
-dain
Dain Sundstrom wrote:
I'm looking into it.
-dain
Scott M Stark wrote:
All of the
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 475
Errors:27
Failures: 4
[time of test: 6 March 2002 3:38 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 475
Errors:27
Failures: 4
[time of test: 6 March 2002 4:24 GMT]
[java.version:
User: dsundstrom
Date: 02/03/05 20:42:57
Modified:src/main/org/jboss/ejb EntityContainer.java
Log:
Fixed bug where create of an EJB 2.0 entity was always returning remote
objects. The create method mapping was keyed to createHome even for
local home methods.
Revision
User: d_jencks
Date: 02/03/05 20:44:21
Modified:.build.xml
Log:
added jboss_xmbean_1_0.dtd to pulled dtds
Revision ChangesPath
1.5 +5 -2 website-snapshots/build.xml
Index: build.xml
Fixed it. The createMethod patched was keyed to always return remote
objects. Once I opened the correct class it was obvious.
In the future, please run the testsuite before committing changes,
especially changes to the core of the server.
-dain
Dain Sundstrom wrote:
It appears the the
Hi Geeks
Two things:
1) I encounter the MBeanProxy (jmx/src/main/org/jboss/mx/util)
in AbstractDeploymentScanner. Because maybe we are going
towards XMBean (ModelMBeans) this will not work anymore
because there is not Interface with XMBeans. Shouldn't we
mark the MBeanProxy as deprecated ?
2)
Andreas Schaefer wrote:
Hi Geeks
Two things:
1) I encounter the MBeanProxy (jmx/src/main/org/jboss/mx/util)
in AbstractDeploymentScanner. Because maybe we are going
towards XMBean (ModelMBeans) this will not work anymore
because there is not Interface with XMBeans. Shouldn't we
mark the
Shit. This is so fucking simple. You just don't get it.
If you want to let folks implement http scanning or another type of
scanning, they will basically need this to keep from having to duplicate
it all... and the bugs that come with it.
If you want to combine them all into one... be my
Hi Jason
Two things:
1) I encounter the MBeanProxy (jmx/src/main/org/jboss/mx/util)
in AbstractDeploymentScanner. Because maybe we are going
towards XMBean (ModelMBeans) this will not work anymore
because there is not Interface with XMBeans. Shouldn't we
mark the MBeanProxy as deprecated ?
So you want to have an interface floating around even it is only used for
this MBeanProxy ?
In short yes. I would rather have calls like
serviceController.create(objectName);
over
server.invoke(controllerName,
new Object[] { objectName },
new
On 5 Mar, David Jencks wrote:
I can't reproduce this with a clean checkout.
build/build.sh
build/build.sh clean
build/build.sh
Sorry, had to go to sleep.
cd build
sh build.sh
sh build.sh
It only works if you do build.sh clean, but not when you build
incrementally, which is neccesary to
49 matches
Mail list logo
