So...
relocate to the middle of these Countries - Danmark... Have fun, try the
yoghurt, its great...
Burkhard
- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: Jboss-Development@Lists. Sourceforge. Net
[EMAIL PROTECTED]
Cc: Jboss-User@Lists. Sourceforge. Net [EMAIL PROTECTED]
Title: Felicidades!
¡Felicidades! Usted y su familia se ganaron las vacaciones celebrando los 100 Años
de Magia en Magico Orlando.Por favor de llamar GRATIS al 1 866 371 7144 desde Puerto Rico o los Estados Unidos.
Desde otros paises, 00 1 305 371 7144, para reclamar sus vacaciones.
Su
Sorry all,
I did run the tests before commiting that patch.
Trouble was, I'd already broken some tests trying
to get some sort of server running on Sunday when I
hit problems with the RARDeployer being deployed
out of sequence.
Moan, Moan ... :-(
I guess it was stupid to commit mods to CMP
I'm try use getRequestURI(), but this method receive uri for old servlet not for
forwarding :(
I try test it in Tomcat - it too work, like in early build of Jetty.
//Alexander
_
View thread online:
Doh!
Actually Dain's mod just reverts the behaviour to
1.1 create :-(
Could somebody with CVS access apply this change
in org.jboss.ejb.EntityContainer.setHomeMappingImpl
[pre]
else if (isEJB1x == false methodName.startsWith(create))
{
- map.put(m[i],
After enthusiastically using mbean proxies for a while now I'm going to
turn around and agree with Andreas that they are kind of a bad idea. For
instance, I think they led Jason to not put the MainDeployer as an
attribute of the scanner because Main Deployer and the farm deployer don't
extend a
I no longer have the clean checkout but I have never had this problem with
many recompiles without cleans. I'm not sure what else I can do about
this.
david jencks
On 2002.03.06 02:39:21 -0500 Peter Antman wrote:
On 5 Mar, David Jencks wrote:
I can't reproduce this with a clean checkout.
As further argument against mbean proxies... they encourage you to think
you can set attibutes by using the getter/setter methods directly rather
than using setAttribute[s]. This is enough to prohibit them in my opinion.
david jencks
On 2002.03.06 08:31:13 -0500 David Jencks wrote:
After
On 6 Mar, David Jencks wrote:
I no longer have the clean checkout but I have never had this problem with
many recompiles without cleans. I'm not sure what else I can do about
this.
Hi, changed JAVA_HOME=/usr/local/lib/jdk1.3.1
to JAVA_HOME=/usr/local/lib/jdk1.3.0_02/
and then it started
On 2002.03.06 10:03:30 -0500 [EMAIL PROTECTED] wrote:
On 6 Mar, David Jencks wrote:
I no longer have the clean checkout but I have never had this problem
with
many recompiles without cleans. I'm not sure what else I can do about
this.
Hi, changed JAVA_HOME=/usr/local/lib/jdk1.3.1
On 6 Mar, David Jencks wrote:
On 2002.03.06 10:03:30 -0500 [EMAIL PROTECTED] wrote:
On 6 Mar, David Jencks wrote:
I no longer have the clean checkout but I have never had this problem
with
many recompiles without cleans. I'm not sure what else I can do about
this.
Hi, changed
Bugs item #526465, was opened at 2002-03-06 17:28
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=526465group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas Hamann (thomash76)
Assigned to:
User: pra
Date: 02/03/06 09:13:43
Modified:src/main/org/jboss/mq/xml XElement.java
Log:
Changed attribute to be access throug getQName since the namespace aware method
getLocalName did not return anything
Revision ChangesPath
1.6 +3 -2
Bugs item #526465, was opened at 2002-03-06 16:28
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=526465group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Thomas Hamann (thomash76)
User: pra
Date: 02/03/06 09:16:29
Modified:src/main/org/jboss/mq SpyTopicPublisher.java
SpyQueueSender.java
Log:
Changed to add correct behaviour when running as identifyes or unidentifyed
producer; throw UnsupportedOperationException accrording to
User: pra
Date: 02/03/06 09:18:25
jbossmq/src/main/org/jboss/mq/sm - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 02/03/06 09:25:07
Removed: src/main/org/jboss/mq/server StateManager.java
StateManagerMBean.java
Log:
Moved state manager into sm.file package as OldStateManager
___
Jboss-development mailing
User: pra
Date: 02/03/06 09:27:49
Modified:src/main/org/jboss/mq/il ClientIL.java ServerIL.java
ServerILJMXService.java
Log:
Commit of JBossMQ new JAAS based security architecture
Revision ChangesPath
1.4 +6 -9
User: pra
Date: 02/03/06 09:27:48
Modified:src/main/org/jboss/mq Connection.java ConnectionToken.java
SpyConnection.java SpySession.java
SpyXAConnection.java
Log:
Commit of JBossMQ new JAAS based security architecture
User: pra
Date: 02/03/06 09:27:49
Modified:src/main/org/jboss/mq/il/jvm JVMServerIL.java
JVMServerILFactory.java JVMServerILService.java
Log:
Commit of JBossMQ new JAAS based security architecture
Revision ChangesPath
1.7 +21 -7
User: pra
Date: 02/03/06 09:27:49
Modified:src/main/org/jboss/mq/il/oil OILClientIL.java
OILClientILService.java OILConstants.java
OILServerIL.java OILServerILService.java
Log:
Commit of JBossMQ new JAAS based security
User: pra
Date: 02/03/06 09:27:50
Modified:src/main/org/jboss/mq/il/rmi RMIServerIL.java
RMIServerILRemote.java RMIServerILService.java
Log:
Commit of JBossMQ new JAAS based security architecture
Revision ChangesPath
1.5 +16 -7
User: pra
Date: 02/03/06 09:27:52
Added: src/main/org/jboss/mq/sm/file DynamicLoginModule.java
DynamicStateManager.java
DynamicStateManagerMBean.java OldStateManager.java
OldStateManagerMBean.java
Log:
User: pra
Date: 02/03/06 09:27:51
Added: src/main/org/jboss/mq/sm AbstractStateManager.java
AbstractStateManagerMBean.java StateManager.java
Log:
Commit of JBossMQ new JAAS based security architecture
Revision ChangesPath
1.1
User: pra
Date: 02/03/06 09:27:50
Modified:src/main/org/jboss/mq/il/uil UILServerIL.java
UILServerILService.java
Log:
Commit of JBossMQ new JAAS based security architecture
Revision ChangesPath
1.7 +24 -4
User: pra
Date: 02/03/06 09:17:36
jbossmq/src/main/org/jboss/mq/security - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 02/03/06 09:27:50
Added: src/main/org/jboss/mq/security SecurityManager.java
SecurityManagerMBean.java SecurityMetadata.java
ServerSecurityInvoker.java SessionIDGenerator.java
Log:
Commit of JBossMQ new JAAS
User: pra
Date: 02/03/06 09:28:51
Added: src/etc/conf/default jbossmq-oldstate.xml
Log:
Old format state manager file
Revision ChangesPath
1.1 jbossmq/src/etc/conf/default/jbossmq-oldstate.xml
Index: jbossmq-oldstate.xml
User: pra
Date: 02/03/06 09:19:26
jbossmq/src/main/org/jboss/mq/sm/file - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 02/03/06 09:31:30
Modified:src/main/org/jboss/mq/il/ha HAServerIL.java
HAServerILService.java
Log:
Updated to support the new JMSServerInvoker interface
Revision ChangesPath
1.3 +4 -4
User: pra
Date: 02/03/06 09:32:35
Added: src/main/org/jboss/test/jbossmq MQBase.java
Log:
Added base class to make it easier to write JMS tests
Revision ChangesPath
1.1 jbosstest/src/main/org/jboss/test/jbossmq/MQBase.java
Index: MQBase.java
User: pra
Date: 02/03/06 09:29:23
Modified:src/etc/conf/default jbossmq-service.xml jbossmq-state.xml
jbossmq-testsuite-service.xml
Log:
Configuration updated to support new security architecture
Revision ChangesPath
1.20 +24 -6
User: pra
Date: 02/03/06 09:34:13
Modified:src/main/org/jboss/test/jbossmq/test
JBossMQUnitTestCase.java
Log:
Some small changes
Revision ChangesPath
1.10 +30 -14
User: pra
Date: 02/03/06 09:34:13
Modified:src/main/org/jboss/test/jbossmq/perf
JBossMQPerfStressTestCase.java
Log:
Some small changes
Revision ChangesPath
1.4 +8 -4
User: pra
Date: 02/03/06 09:33:31
Added: src/main/org/jboss/test/jbossmq/test SecurityTestCase.java
Log:
Added testcases to test the new security architecture
Revision ChangesPath
1.1
User: pra
Date: 02/03/06 09:41:41
Modified:src/etc/conf/default auth.conf
Log:
Added entry for new jbossmq security domain
Revision ChangesPath
1.9 +10 -1 jboss/src/etc/conf/default/auth.conf
Index: auth.conf
Maybe you aren't done here... but the naming convention to get your tests
run in the testsuite without any other code is to name them
xxxUnitTestCase
or
xxxStressTestCase
david jencks
On 2002.03.06 12:33:31 -0500 Peter Antman wrote:
User: pra
Date: 02/03/06 09:33:31
Added:
User: dsundstrom
Date: 02/03/06 10:56:15
Modified:src/main/org/jboss/ejb EntityContainer.java
Log:
Fixed fix to creatMethod patch. Will now correctly call createHome and
createLocalHome.
Revision ChangesPath
1.73 +2 -2
Done.
Adrian Brock wrote:
Doh!
Actually Dain's mod just reverts the behaviour to
1.1 create :-(
Could somebody with CVS access apply this change
in org.jboss.ejb.EntityContainer.setHomeMappingImpl
[pre]
else if (isEJB1x == false methodName.startsWith(create))
Bugs item #506914, was opened at 2002-01-22 03:36
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=506914group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Cesar Hernandez Fuente (chfuente)
Assigned
Cheers Dain,
I'm just about to commit the testsuite changes,
when I've quintuple checked I've not broken anything :-)
Regards,
Adrian
Done.
Adrian Brock wrote:
Doh!
Actually Dain's mod just reverts the behaviour to
1.1 create :-(
Could somebody with CVS access apply this
User: ejort
Date: 02/03/06 12:23:25
Modified:src/main/org/jboss/test/bmp/interfaces SimpleBMPHome.java
Log:
Tests for createMETHOD
Revision ChangesPath
1.3 +3 -0
jbosstest/src/main/org/jboss/test/bmp/interfaces/SimpleBMPHome.java
Index:
User: ejort
Date: 02/03/06 12:23:25
Modified:src/main/org/jboss/test/testbean/interfaces
EnterpriseEntityHome.java EntityBMPHome.java
EntityPKHome.java StatefulSessionHome.java
Log:
Tests for createMETHOD
Revision Changes
On 6 Mar, David Jencks wrote:
Maybe you aren't done here... but the naming convention to get your tests
run in the testsuite without any other code is to name them
Yea thanks, but all the other tests in JBossMQ appart from the JBoss...
is not names UnitTestCase either, and since jason even
User: ejort
Date: 02/03/06 12:23:24
Modified:src/main/org/jboss/test/bmp/beans SimpleBMPBean.java
Log:
Tests for createMETHOD
Revision ChangesPath
1.4 +58 -0 jbosstest/src/main/org/jboss/test/bmp/beans/SimpleBMPBean.java
Index: SimpleBMPBean.java
User: ejort
Date: 02/03/06 12:23:25
Modified:src/main/org/jboss/test/bmp/test BmpUnitTestCase.java
Log:
Tests for createMETHOD
Revision ChangesPath
1.6 +1 -1 jbosstest/src/main/org/jboss/test/bmp/test/BmpUnitTestCase.java
Index: BmpUnitTestCase.java
User: ejort
Date: 02/03/06 12:23:25
Modified:src/resources/testbean/META-INF ejb-jar.xml
Log:
Tests for createMETHOD
Revision ChangesPath
1.3 +4 -0 jbosstest/src/resources/testbean/META-INF/ejb-jar.xml
Index: ejb-jar.xml
User: ejort
Date: 02/03/06 12:23:25
Modified:src/main/org/jboss/test/testbean/bean
EnterpriseEntityBean.java EntityBMPBean.java
EntityPKBean.java StatefulSessionBean.java
Log:
Tests for createMETHOD
Revision ChangesPath
User: ejort
Date: 02/03/06 12:23:26
Modified:src/resources/testbean2/META-INF ejb-jar.xml
Log:
Tests for createMETHOD
Revision ChangesPath
1.3 +3 -2 jbosstest/src/resources/testbean2/META-INF/ejb-jar.xml
Index: ejb-jar.xml
User: ejort
Date: 02/03/06 12:23:25
Modified:src/main/org/jboss/test/testbean/test BeanUnitTestCase.java
Log:
Tests for createMETHOD
Revision ChangesPath
1.10 +29 -1
jbosstest/src/main/org/jboss/test/testbean/test/BeanUnitTestCase.java
Index:
User: ejort
Date: 02/03/06 12:23:26
Modified:src/resources/testbeancluster/META-INF ejb-jar.xml
Log:
Tests for createMETHOD
Revision ChangesPath
1.2 +4 -0 jbosstest/src/resources/testbeancluster/META-INF/ejb-jar.xml
Index: ejb-jar.xml
User: ejort
Date: 02/03/06 12:23:25
Modified:src/resources/bmp/META-INF ejb-jar.xml
Log:
Tests for createMETHOD
Revision ChangesPath
1.2 +2 -0 jbosstest/src/resources/bmp/META-INF/ejb-jar.xml
Index: ejb-jar.xml
User: chirino
Date: 02/03/06 13:03:04
Modified:.build.xml
Log:
Small mod to the build so that JavaCC places it's output into the proper directory
structure
Revision ChangesPath
1.26 +12 -4 jbossmq/build.xml
Index: build.xml
Change Notes item #526622, was opened at 2002-03-06 12:06
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=526622group_id=22866
Category: JBossMQ
Group: v3.0 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: Peter Antman (pra)
Assigned to:
Bugs item #526696, was opened at 2002-03-06 23:18
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=526696group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Kelly McTiernan (kellymct)
Assigned to:
Please rename it one way or the other. If it repeats something, call it a
stress test, these are run separately from unit tests.
IMNSHO a misnamed test that is not run automatically is almost worse than
no test at all, because the test writer is apt to think the feature is
getting tested when
MainDeployer was orginally slated to be an instance of DeployerMBean,
but someone refactored that interface such that it would not apply here
anymore...
--jason
David Jencks wrote:
After enthusiastically using mbean proxies for a while now I'm going to
turn around and agree with Andreas
So fix it to call them as attributes get/set... this is ridiculous
--jason
David Jencks wrote:
As further argument against mbean proxies... they encourage you to think
you can set attibutes by using the getter/setter methods directly rather
than using setAttribute[s]. This is enough to
On 2002.03.06 18:36:25 -0500 Jason Dillon wrote:
MainDeployer was orginally slated to be an instance of DeployerMBean,
but someone refactored that interface such that it would not apply here
anymore...
Maybe a really long time ago, but neither my proposed revision or marcs
rewrite would
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 497
Errors:4
Failures: 5
[time of test: 7 March 2002 0:30 GMT]
[java.version:
What does FarmDeployer actually do?
--jason
David Jencks wrote:
On 2002.03.06 18:36:25 -0500 Jason Dillon wrote:
MainDeployer was orginally slated to be an instance of DeployerMBean,
but someone refactored that interface such that it would not apply here
anymore...
Maybe a really long
User: jules_gosnell
Date: 02/03/06 16:50:30
Modified:jettyFAQ
Log:
clarify a little (for Greg)
Revision ChangesPath
1.4 +12 -12contrib/jetty/FAQ
Index: FAQ
===
RCS file:
User: jules_gosnell
Date: 02/03/06 16:53:50
Modified:jettyTODO
Log:
update
Revision ChangesPath
1.15 +6 -1 contrib/jetty/TODO
Index: TODO
===
RCS file:
so uh...
I actually went and read the DeploymentScanner and MainDeployer stuff, it is
actually good.
There I said it. It suffers from some jasonisms meaning the abstract
hello world, but all in all it is actually a pretty piece of work.
Yes the hardcode of MainDeployer is bad but then he DID
You'll either have to look at it or check with Andreas to be sure, but I
believe it deploys a file it finds on every server in the farm. It needs
reimplementing. I think it needs its own scanner, and just feeds the
results to all the MainDeployers in the farm. Kind of a
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 497
Errors:4
Failures: 5
[time of test: 7 March 2002 1:8 GMT]
[java.version: 1.3.0]
There seems to be some misconception about MBeanProxy, Java interfaces
and JMX with respect to coupling and flexibility.
MBeanProxy + Java inteface are client-side tools which make using JMX
easier to use. This is because the proxy will perform the required type
casting and will handle the
Kind of a
MainDeployerInterceptor;-)
Would be more appriopriate than a seperate MainDeployer for farm
functionality.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
There I said it. It suffers from some jasonisms meaning the abstract
hello world, but all in all it is actually a pretty piece of work.
I can see how that might appear now that DirectoryDeploymentScanner was
removed... though there was a reason for it when I wrote it. I don't
just
|Thanks for actually taking a look.
thanks it is actually good work :)
marcf
|
|--jason
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 498
Errors:4
Failures: 4
[time of test: 7 March 2002 1:46 GMT]
[java.version:
User: user57
Date: 02/03/06 17:50:52
Modified:src/main/org/jboss Main.java
Log:
o javadoc
Revision ChangesPath
1.5 +11 -7 jboss-system/src/main/org/jboss/Main.java
Index: Main.java
===
And --patch-dir to --patchdir
??
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Hi
There seems to be some misconception about MBeanProxy, Java interfaces
and JMX with respect to coupling and flexibility.
MBeanProxy + Java inteface are client-side tools which make using JMX
easier to use. This is because the proxy will perform the required type
casting and will handle
Hi
I don't want to create a separate MainDeployer but to be able to
intercept the deployment and manage it before the local deployment
is performed.
I never thought to be another part of the deployment. Can I add my
deployer to the MainDeployer to be notified that a file is going to
be deployed
What is the desired result which you are trying to achieve?
--jason
Andreas Schaefer wrote:
Hi
I don't want to create a separate MainDeployer but to be able to
intercept the deployment and manage it before the local deployment
is performed.
I never thought to be another part of the
There is absolutly NO coupling when using a Java interface and
MBeanProxy to invoke operations on a target MBean, as there is no
requirement that the target MBean implement that interface. At runtime
the interface only plays a role on the client side. BUT durring compile
time, it plays a role
JBoss daily test results
SUMMARY
Number of tests run: 506
Successful tests: 498
Errors:4
Failures: 4
[time of test: 7 March 2002 2:48 GMT]
[java.version:
Hi,
I am trying to deploy SAP Resource Adapter.. I am getting following exception.. I am
using JBOSS 2.4.3.
Any help would be greatly appreciated. Thanks in advance.
-Abhishek
AutoDeployer] Auto deploy of file:/C:/JBoss-2.4.3/deploy/lib/sapr3.rar
[RARDeployer] Attempting to deploy RAR at
Hi
But the MBean doesn't have too and for DynamicMBean you have
to rename them different as XXXMBean !!
Who said anything about using a MBean suffix?
StandardMBean requires that. You could (unlikely but possible) run into
a problem when the XXXMBean you need for a StandardMBean want
to
We should create a JCA forum just for you david.
For now sorry, no user questions on the dev list
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Abhishek Banerjee
|Sent: Wednesday, March 06, 2002 6:48 PM
|To: [EMAIL PROTECTED]
|Subject:
But the MBean doesn't have too and for DynamicMBean you have
to rename them different as XXXMBean !!
Who said anything about using a MBean suffix?
StandardMBean requires that. You could (unlikely but possible) run into
a problem when the XXXMBean you need for a StandardMBean want
to apply to
JBoss daily test results
SUMMARY
Number of tests run: 496
Successful tests: 487
Errors:5
Failures: 4
[time of test: 7 March 2002 4:0 GMT]
[java.version: 1.3.1]
Please repost to the persistence forum or the jboss-user list and include
the ra.xml from your adapter package. There may be a spec version
inconsistency.
Thanks
david jencks
On 2002.03.06 21:48:25 -0500 Abhishek Banerjee wrote:
Hi,
I am trying to deploy SAP Resource Adapter.. I am getting
On 2002.03.06 21:09:00 -0500 Andreas Schaefer wrote:
Hi
I don't want to create a separate MainDeployer but to be able to
intercept the deployment and manage it before the local deployment
is performed.
I never thought to be another part of the deployment. Can I add my
deployer to the
User: binaryfeed
Date: 02/03/06 20:19:39
Modified:src/main/org/jboss/util Tag: Branch_2_4
TimedCachePolicy.java
Log:
Fixed threadSafe flag usage!
Revision ChangesPath
No revision
No revision
User: binaryfeed
Date: 02/03/06 20:38:34
Modified:src/main/org/jboss/util TimedCachePolicy.java
Log:
Fixing threadSafe flag!
Revision ChangesPath
1.2 +3 -3 jboss-common/src/main/org/jboss/util/TimedCachePolicy.java
Index: TimedCachePolicy.java
snip
* * *
I believe that using MBeanProxy (perhaps a redesigned version to cache
handlers and correctly get/set attributes) will greatly improve the
maintainability of the system. It does this by adding compile time type
checking and reduces client side casting problems. When used for
JBoss daily test results
SUMMARY
Number of tests run: 496
Successful tests: 486
Errors:5
Failures: 5
[time of test: 7 March 2002 5:15 GMT]
[java.version:
My 2 cents: Keep the MBeanProxy, why?? CUZ i'm lazy. Are you going to force
me to do invoke(print, new Object[String.class] {}, new String[] {hi});
for a feaking print(hi); Get out of here.
If I know ahead of time that the object is going to have the method, why
can't I use an
Hi Geeks
After a simple test with direct JMX calls and MBeanProxy it seems
to be that both work without a considerably difference. So reflection
performance is out the door.
My 2 cents: Keep the MBeanProxy, why?? CUZ i'm lazy. Are you going to
force
me to do invoke(print, new
User: user57
Date: 02/03/06 21:53:56
newsite/src/docs/demo - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 02/03/06 21:56:09
Added: src/docs/demo index.jsp
Log:
o basic netboot demo docs... still needs some work
Revision ChangesPath
1.1 newsite/src/docs/demo/index.jsp
Index: index.jsp
User: user57
Date: 02/03/06 21:56:09
Added: src/docs/demo/netboot index.jsp
Log:
o basic netboot demo docs... still needs some work
Revision ChangesPath
1.1 newsite/src/docs/demo/netboot/index.jsp
Index: index.jsp
User: user57
Date: 02/03/06 21:54:05
newsite/src/docs/demo/netboot - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
So the only real issue is another interface when not using standardmbeans.
I think that is minor compaired to the benifits. Thanks for checking
the performance though. I was not sure how dyamic proxy performed anyways.
--jason
Andreas Schaefer wrote:
Hi Geeks
After a simple test with
User: user57
Date: 02/03/06 22:19:58
newsite/src/docs/demo/netboot/base - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 02/03/06 22:27:43
Modified:src/main/org/jboss Main.java
Log:
o Using Package for version info displayed from -V or --version
o --net-boot - --netboot
o --patch-dir - --patchdir
Revision ChangesPath
1.6 +12 -7
User: user57
Date: 02/03/06 23:15:11
Modified:src/docs/demo/netboot index.jsp
Log:
o Host file demo files on jboss.sf.net
Revision ChangesPath
1.2 +8 -8 newsite/src/docs/demo/netboot/index.jsp
Index: index.jsp
I think I understand the benefits... I'm not convinced yet that there are
no problems we haven't seen yet. I'm still thinking.
The only problem I could see was when a JMX exception was thrown... like
for no such method or whatever... which we would just translate into
some Error. Or could
1 - 100 of 101 matches
Mail list logo
