Comments are in between the files.
These are obviously against the 2.4.3 branch, but I have checked against cvs
HEAD, and there is nothing there like these changes.
I have a few more patches, but am still working on the debification, so am not
ready to send those off yet.
--- jboss-2.4.3.orig/j
On 2001.11.13 00:13:54 -0500 Hiram Chirino wrote:
>
> Hi Loren!
>
> >From: Loren Rosen <[EMAIL PROTECTED]>
> >To: "[EMAIL PROTECTED]"
> ><[EMAIL PROTECTED]>
> >Subject: [JBoss-dev] jbossmq: persistance implementation questions
> >Date: Mon, 12 Nov 2001 20:22:27 -0800
> >
> >I've been looking a
I looked too.
On 2001.11.12 23:22:27 -0500 Loren Rosen wrote:
> I've been looking a bit at the jboss mq persistance code, and I have
> some questions. I'll state some of them from a user perspective, but my
> motivation is as a developer; that is, to address some of the 'problems'
> or 'limitatio
JBoss daily test results
SUMMARY
Number of tests run: 192
Successful tests: 155
Errors:23
Failures: 14
[time of test: 13 November 2001 5:59 GMT]
[java.version:
Hi Loren!
>From: Loren Rosen <[EMAIL PROTECTED]>
>To: "[EMAIL PROTECTED]"
><[EMAIL PROTECTED]>
>Subject: [JBoss-dev] jbossmq: persistance implementation questions
>Date: Mon, 12 Nov 2001 20:22:27 -0800
>
>I've been looking a bit at the jboss mq persistence code, and I have
>some questions. I'll
JBoss daily test results
SUMMARY
Number of tests run: 182
Successful tests: 145
Errors:23
Failures: 14
[time of test: 13 November 2001 4:56 GMT]
[java.version:
I've been looking a bit at the jboss mq persistance code, and I have
some questions. I'll state some of them from a user perspective, but my
motivation is as a developer; that is, to address some of the 'problems'
or 'limitations' these questions may uncover.
* Different DBMS system support: I re
I'm happy to try to fix this problem along these lines, especially if
someone will tell me which mbeans need to be synchronized(?right word?)
1. in ClusterPartition, include
JBossCluster:service=HANaming
...
2. A new mbean interface, ClusterRegistration having the method
registerCluster(Clu
JBoss daily test results
SUMMARY
Number of tests run: 192
Successful tests: 155
Errors:23
Failures: 14
[time of test: 13 November 2001 3:52 GMT]
[java.version:
> This won't do any good. If all required beans are present, the order will
> be
>
> create
> configure
> call before start
> start
> call after start
>
> with no opportunity for anything else to happen. Might as well put
> everything in start.
I don't understand. The problem we have here is th
This won't do any good. If all required beans are present, the order will
be
create
configure
call before start
start
call after start
with no opportunity for anything else to happen. Might as well put
everything in start.
Unfortunately Hirams suggestion of "after server is started" doesn't
JBoss daily test results
SUMMARY
Number of tests run: 192
Successful tests: 153
Errors:24
Failures: 15
[time of test: 13 November 2001 3:8 GMT]
[java.version: 1
On 2001.11.12 20:37:24 -0500 Hiram Chirino wrote:
> >It looks to me as if
> >"Because of quirkiness of JavaGroups, services cannot ask for
> > > state-synchronization once the Group connection has been initiated."
> >means exactly that the ClusterPartition HAS to know EXACTLY which
> services
> >a
>Hi Geeks
>
>To keep Davids changes and to make Clustering working I remember a
>suggestion long ago to add a method-call to the arguments of a MBean.
>
>I would suggest the following:
>- a can contain a attribute
>- attribute supports the call of a non-argument method and
>the time can be
Hi Geeks
To keep Davids changes and to make Clustering working I remember a
suggestion long ago to add a method-call to the arguments of a MBean.
I would suggest the following:
- a can contain a attribute
- attribute supports the call of a non-argument method and
the time can be specified
>It looks to me as if
>"Because of quirkiness of JavaGroups, services cannot ask for
> > state-synchronization once the Group connection has been initiated."
>means exactly that the ClusterPartition HAS to know EXACTLY which services
>are using it. If you do this, the mbean-ref-list will give you
On 2001.11.12 18:08:14 -0500 Bill Burke wrote:
>
>
> > -Original Message-
> > From: David Jencks [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, November 12, 2001 5:40 PM
> > To: Bill Burke
> > Cc: Andreas Schaefer; Sacha Labourey;
> > [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] RE: Depl
> -Original Message-
> From: Hiram Chirino [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 6:47 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] RE: Deployment exception on Clustering
>
>
>Services requiring state-transfer like HA-JNDI must register with an object
>created by the ClusterPartition. The ClusterPartition cannot complete
>JavaGroups connections until the all these HA services have registered with
>the ClusterPartition. The ClusterPartition should not know about who
>
You're right. But you don't have to have everything in jboss-service.xml.
Everything has to be in one service.xml file though (i.e.
cluster-service.xml). Of course, this is only a problem if somebody writes
their own custom HA services that need state-synchronization.
Bill
> -Original Mess
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Maplesden
> Sent: Monday, November 12, 2001 6:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> From what I can follow of this conversation
> -Original Message-
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 5:40 PM
> To: Bill Burke
> Cc: Andreas Schaefer; Sacha Labourey;
> [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> What are the mbean dependenc
Hi Bill
I don't think this works. When you use dependencies feature just wait until
the MBean is available. But when your services is deployed on another thread
then the init() and start() sequence runs out of order and you can fail.
Only when
all the services are deployed by the same thread (Dep
I answered this in David Jencks' email, but, unfortunately, right now, you
cannot hot-deploy HA services that require state transfer. You can
hot-deploy clustered SLSBs, and EBs, but I'm not sure about SFSBs. Sacha
will have to answer that.
Also, you do NOT have to add everything to jboss-servic
>From what I can follow of this conversation I think what Bill needs is a
bunch of mbeans to be initialised before any of them are started i.e.
mbean1.init();
mbean2.init();
mbean3.init();
mbean1.start();
mbean2.start();
mbean3.start();
as opposed
Hi
Looks like I am asleep here, sorry. Of course, you are
right.
Andy
> Hey,
>
> > Hi
> >
> > postRegister() is a callback method issued by the MBeanServer
> > before the
> > MBean gets finally registered. You then can save the
> > MBeanServer you are
> > connected to and change the MBean O
|Whether you call it init() or postRegister() I don't care. At least for
|clustering and it's dependent services right now we need 2 stage
|initialization init() (or equivalent API call) and start().
wow, an actual example of a 2 stage initialization. Rickard is right afair
the reason for remov
To do this, subclass ServiceMbeanSupport, descend your classes from this
subclass, and override PostRegister to call your init method, after
super.postRegister:
public void postRegister(Boolean registrationDone)
{
super.postRegister(registrationDone);
if (registrationDone.boole
Hi Bill
I see another problem with your approach. With JBoss 3.0
we can deploy services after the application server is started.
Now is it the case that all components registering on a HAPartition
must be started when the JBoss is started ?
Therefore it means that all parts of the cluster must be
You will not see the problems introduced by removing init unless you setup
HA-JNDI on one node, bind a bunch of stuff, then bring up a second node.
The second node will not get state-transfer from the first if you have
removed init. Again. This clustering stuff needs a 2 stage startup. Please
do
Hey,
> Hi
>
> postRegister() is a callback method issued by the MBeanServer
> before the
> MBean gets finally registered. You then can save the
> MBeanServer you are
> connected to and change the MBean ObjectName before it is set.
This is done in preRegister, not in postRegister.
Simon
> I
Hi Bill
postRegister() is NOT an option because it is called after
the MBean is created (Constructor is called) but BEFORE
any attributes are set by the ServiceController.
And I see that you use PartitionProperties and PartitionName
which would not be available except you only use defaults.
Andy
What are the mbean dependencies here? Is it possible to add a service to a
running cluster? How is it synchronized? (what does synchronized mean here,
anyway?).
If it is not possible to add a service to a started cluster, you should
document the contents of the cluster with an mbean-ref-list tag
> -Original Message-
> From: Andreas Schaefer [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 5:17 PM
> To: Bill Burke
> Cc: Sacha Labourey; [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> Hi
>
> postRegister() is a callback method i
I'm trying to eliminate init and destroy because they were getting called
like this from ServiceController:
init();
start();
and
stop();
destroy();
. If there are problems left after combining init and start, or if you
would like me to do this, let me know. Is there any way to test the
clust
It is a method of the MBeanRegistration interface that is called after the
MBean has been registered with the server. You could override it to
use it as a hook in place of init:
public void postRegister(java.lang.Boolean registrationDone)
{
if( registrationDone.booleanValue() == true
Hi
postRegister() is a callback method issued by the MBeanServer before the
MBean gets finally registered. You then can save the MBeanServer you are
connected to and change the MBean ObjectName before it is set.
I am still puzzled why you need a 2 stage startup process.
The only reason I can ass
Rickard talked about something called postRegister?
> -Original Message-
> From: Andreas Schaefer [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 4:50 PM
> To: David Jencks
> Cc: Sacha Labourey; [EMAIL PROTECTED]; Bill Burke
> Subject: Re: [JBoss-dev] RE: Deployment exception
Hi David
You hear it. How can be use init() again for Clustering ?
Andy
- Original Message -
From: "Bill Burke" <[EMAIL PROTECTED]>
To: "Andreas Schaefer" <[EMAIL PROTECTED]>
Cc: "Sacha Labourey" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 1:10 PM
Subject: [
Whether you call it init() or postRegister() I don't care. At least for
clustering and it's dependent services right now we need 2 stage
initialization init() (or equivalent API call) and start().
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> R
Why are we doing
this? Some services, clustering for example, depend on init and
start. Can we not do this?
Bill Burke wrote:
> Why are we doing this? Some services, clustering for example, depend on
> init and start. Can we not do this?
Note that taking init() out of Service is not a big deal, whereas taking
it out of ServiceSupport is. init() can be done as a side-effect of
postRegister anyway
Yes this a very serious problem and it wouldn't show up with your Farm
stuff. THis is my fault because I didn't document the code very well, but
can we please switch this back?
In the init phase, all services register with the cluster (HAPartition) for
cluster events that want to listen to and a
marc fleury wrote:
> |Yes, we do. Something developed for jboss will not run on other providers.
>
> No offense to your co-worker and Rickard but it is a dumb rhetoric point :)
>
> If we offer this feature we do not break the compatibility of the J2EE
> platform specification.
>
> The spec do
Hi Bill
I added all the code from init() into start(). Is this a problem ?
At least when I use the Farm it works like a charm.
Andy
- Original Message -
From: "Bill Burke" <[EMAIL PROTECTED]>
To: "David Jencks" <[EMAIL PROTECTED]>; "Andreas Schaefer"
<[EMAIL PROTECTED]>
Cc: "Sacha Labo
Guys,
The clustering stuff is dependent on init and start both being there. Can
we put back the init? Otherwise you break our stuff. Why are you doing
this anyways?
Bill
> -Original Message-
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 2:33 PM
> T
> yOn Mon, 12 Nov 2001, marc fleury wrote:
>
> > |A coworker just brought up a good point. If we do this, we suddenly
become
> > |incompatible with other J2EE providers(I do know we don't have to
> >
> > no we don't
>
> Yes, we do. Something developed for jboss will not run on other
providers.
Hi Geeks
The first complete Farm Service is finished for JBoss 3.
You can now deploy and undeploy files on any node and
all the other remote nodes do the same. Therefore when
you deploy a service on one node you can undeploy it
on another node when you delete the file in its /deploy/farm
directo
|Yes, we do. Something developed for jboss will not run on other providers.
No offense to your co-worker and Rickard but it is a dumb rhetoric point :)
If we offer this feature we do not break the compatibility of the J2EE
platform specification.
The spec doesn't specify portability in feature
User: schaefera
Date: 01/11/12 11:59:18
Removed: src/main/org/jboss/system FarmAutoDeployer.java
FarmAutoDeployerMBean.java
Log:
Finished 1. Version of the JBoss Farm. Now it uses the AutoDeployer and
therefore FarmAutoDeployer became obsolete. The Farm now
User: schaefera
Date: 01/11/12 11:59:17
Modified:src/main/org/jboss/ha/framework/server ClusterPartition.java
FarmMemberService.java
Log:
Finished 1. Version of the JBoss Farm. Now it uses the AutoDeployer and
therefore FarmAutoDeployer became obsolete. The
User: schaefera
Date: 01/11/12 11:59:16
Modified:etc farm-service.xml
Log:
Finished 1. Version of the JBoss Farm. Now it uses the AutoDeployer and
therefore FarmAutoDeployer became obsolete. The Farm now support also
undeployment, copies a deployed file back to /deploy/farm
User: schaefera
Date: 01/11/12 11:59:18
Modified:src/main/org/jboss/deployment AutoDeployer.java
AutoDeployerMBean.java
Log:
Finished 1. Version of the JBoss Farm. Now it uses the AutoDeployer and
therefore FarmAutoDeployer became obsolete. The Farm now sup
yOn Mon, 12 Nov 2001, marc fleury wrote:
> |A coworker just brought up a good point. If we do this, we suddenly become
> |incompatible with other J2EE providers(I do know we don't have to
>
> no we don't
Yes, we do. Something developed for jboss will not run on other providers.
_
|Likewise. If JBoss is generating remote/home interfaces at runtime, then
|you won't be able to use these beans as you would other beans, i.e.
|you'd use properietary ways of accessing them that would break when you
|try to use the same beans in another container.
not in webservices approach, no
|> A coworker just brought up a good point. If we do this, we
|suddenly become
|> incompatible with other J2EE providers
|
|
|True, if you deploy on JBoss using this technique your project will be
|unportable.
wtf are you talking about? we don't break the jar format, if you give us a
jar we stil
User: starksm
Date: 01/11/12 11:32:56
Modified:src/main/org/jboss/web Tag: Branch_2_4
AbstractWebContainer.java
AbstractWebContainerMBean.java
Log:
Add support for resource-env-ref to WebMetaData and AbstractWebContainer.
Added an e
User: starksm
Date: 01/11/12 11:31:07
Modified:src/main/org/jboss/configuration Tag: Branch_2_4
ConfigurationService.java
Log:
Add support for a mbean/config element that allows an mbean to import an
arbitrary XML configuration tree if it implements the im
Bugs item #475156, was opened at 2001-10-25 19:33
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=475156&group_id=22866
Category: CatalinaBundle
Group: v2.4 (stable)
Status: Closed
Resolution: Duplicate
Priority: 5
Submitted By: Jason Vasquez (jpvasquez)
marc fleury wrote:
> |> A coworker just brought up a good point. If we do this, we
> |suddenly become
> |> incompatible with other J2EE providers
> |
> |
> |True, if you deploy on JBoss using this technique your project will be
> |unportable.
>
> wtf are you talking about? we don't break the ja
On 2001.11.12 14:05:03 -0500 Juha-P Lindfors wrote:
>
>
> On Mon, 12 Nov 2001, marc fleury wrote:
>
> > |It is very similar to GLUE
> > |(http://www.themindelectric.com/products/glue/glue.html).
> >
> > there you go, let's do it then...
>
> the problem with glue is we can't distribute the lib
User: starksm
Date: 01/11/12 11:32:56
Modified:src/main/org/jboss/metadata Tag: Branch_2_4
BeanMetaData.java ResourceRefMetaData.java
WebMetaData.java
Log:
Add support for resource-env-ref to WebMetaData and AbstractWebContainer.
Ad
|A coworker just brought up a good point. If we do this, we suddenly become
|incompatible with other J2EE providers(I do know we don't have to
no we don't
marcf
|make _stub
|objects, which is already an incompatiblity).
|
|Is this something that s/b considered?
|
___
User: starksm
Date: 01/11/12 11:29:44
Modified:catalina/src/build Tag: Branch_2_4 build.properties build.sh
build.xml
Log:
Update to use Tomcat-4.0.1
Revision ChangesPath
No revision
No revision
Adam Heath wrote:
> A coworker just brought up a good point. If we do this, we suddenly become
> incompatible with other J2EE providers
True, if you deploy on JBoss using this technique your project will be
unportable.
> (I do know we don't have to make _stub
> objects, which is already an i
Thanks, must have missed that one.
I generally copied the init[Service] code and put it in start[Service] at
the beginning, similarly for destroy.
As far as I could tell, everything covered by the testsuite works as well
after the changes as before.
Please let me know of other problems.
The Se
yOn Mon, 12 Nov 2001, marc fleury wrote:
> |It is very similar to GLUE
> |(http://www.themindelectric.com/products/glue/glue.html).
>
> there you go, let's do it then...
>
> marcf
A coworker just brought up a good point. If we do this, we suddenly become
incompatible with other J2EE providers(I
On Mon, 12 Nov 2001, marc fleury wrote:
> |the problem with glue is we can't distribute the lib with jboss
> |it will require each user to go and download it individually
>
> ok let's stop this, who said we wanted to distribute the libraries from
> glue?
I would want to, cause its a very good l
User: starksm
Date: 01/11/12 11:23:56
Added: lib Tag: Branch_2_4 ant.jar
Removed: lib Tag: Branch_2_4 ant-1.3.jar
Log:
Switch to ant 1.4.1
Revision ChangesPath
No revision
No revision
1.5.2.1 +1598
User: starksm
Date: 01/11/12 11:21:19
Modified:catalina/src/main/org/jboss/web/catalina Tag: Branch_2_4
EmbeddedCatalinaServiceSX.java
EmbeddedCatalinaServiceSXMBean.java
Added: catalina/src/main/org/jboss/web/catalina Tag: Branch
User: starksm
Date: 01/11/12 11:21:19
Modified:catalina/src/main/org/jboss/web/catalina/security Tag:
Branch_2_4 SSLServerSocketFactory.java
Log:
Add support for setting the catalina Engine class and additional
Connectors using the new mbean/config element
I've used GLUE and I think that they do it right. They make web services
seem like if it was just RMI.
Regards,
Hiram
>From: Rickard Oberg <[EMAIL PROTECTED]>
>To: jBoss Developer <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev] [research] a home/remote generator
>Date: Mon, 12 Nov 2001 19:28:57
Hi David
The ClusterPartition.java class is not started correctly
because now init() is not called anymore and therefore
the JavaGroups JChannel are not initialized.
I will go ahead and fix it but maybe there are other MBeans
out there which needs attention, too.
Thanx
x
Andrea
|the problem with glue is we can't distribute the lib with jboss
|it will require each user to go and download it individually
ok let's stop this, who said we wanted to distribute the libraries from
glue?
I was talking about doing similar functionality
marcf
|
|-- Juha
|
|
___
On Mon, 12 Nov 2001, marc fleury wrote:
> |It is very similar to GLUE
> |(http://www.themindelectric.com/products/glue/glue.html).
>
> there you go, let's do it then...
the problem with glue is we can't distribute the lib with jboss
it will require each user to go and download it individually
Bugs item #475156, was opened at 2001-10-25 19:33
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=475156&group_id=22866
Category: CatalinaBundle
Group: v2.4 (stable)
Status: Closed
Resolution: Duplicate
Priority: 5
Submitted By: Jason Vasquez (jpvasquez)
Bugs item #474134, was opened at 2001-10-23 09:21
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=474134&group_id=22866
Category: JBossSX
Group: v2.4 (stable)
Status: Closed
Resolution: Fixed
Priority: 8
Submitted By: Michael Hussey (mhussey)
Assigned to:
|It is very similar to GLUE
|(http://www.themindelectric.com/products/glue/glue.html).
there you go, let's do it then...
marcf
|
|/Rickard
|
|--
|Rickard Öberg
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net
Change Notes item #480996, was opened at 2001-11-12 10:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=480996&group_id=22866
Category: None
Group: v3.0 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: David Jencks (d_jencks)
Assigned to: Nobody/Ano
User: d_jencks
Date: 01/11/12 10:35:18
Modified:src/main/org/jboss/pool ObjectPool.java PoolParameters.java
Log:
Updated the manual to show mbean refs: simplified the pool configuration. The pool
changes are a bit of a hack, but do expose what I think is a better interface.
Bloc
User: d_jencks
Date: 01/11/12 10:35:18
Modified:src/xdocs resource.xml
Log:
Updated the manual to show mbean refs: simplified the pool configuration. The pool
changes are a bit of a hack, but do expose what I think is a better interface.
Blocking is always on, idle timeout is al
User: d_jencks
Date: 01/11/12 10:35:19
Modified:src/etc/conf/default hsqldb-default-service.xml
jms-service.xml
Log:
Updated the manual to show mbean refs: simplified the pool configuration. The pool
changes are a bit of a hack, but do expose what I think i
User: d_jencks
Date: 01/11/12 10:35:17
Modified:src/main/org/jboss/resource/connectionmanager
PoolManager.java
Log:
Updated the manual to show mbean refs: simplified the pool configuration. The pool
changes are a bit of a hack, but do expose what I think is
User: d_jencks
Date: 01/11/12 10:35:18
Modified:src/main/org/jboss/resource/connectionmanager/jboss
MinervaNoTransCMFactory.java
MinervaSharedLocalCMFactory.java
MinervaXACMFactory.java
Log:
Updated the manual t
marc fleury wrote:
> If I get webservices in 10 seconds, I think we are in a very SWEET position,
> we don't want to know about the EJB packaging and home and remote and
> blablabla, screw all that, I DON'T CARE. We just drop the *CLASS* in the
> deploy directory and voila! webservice for you si
I am not sure I understand the create issue... Do you mean that with this
kind of client, a SFSB would be, semantically, more appropriate?
> -Message d'origine-
> De : marc fleury [mailto:[EMAIL PROTECTED]]
> Envoye : lundi, 12 novembre 2001 19:23
> A : Sacha Labourey; Aaron Mulder; jBoss
Sacha Labourey wrote:
> Yes, but one of the important point (I think) is that *the developer is able
> to write the client code directly by referencing the bean code without
> waiting for a code generator to generate the home and remote. The developer
> modifies the bean? no problem, he can direc
|I would certainly not build a online banking system on this solution, but I
|am sure this tool would reach its audience.
even integrating my previous serious breaking of ejb contract (say the
finders/create) it is a point, that it would reach its audience.
Again I would satisfied with the .net
actually the one problem I see with this is that we seriously break the
client contract as the API of the bean is really not a match with the
remote, think "create".
Again I think the advantage is on the server bean saving space and allowing
for extremelly simple deployment of webservices.
As a
Yes, but one of the important point (I think) is that *the developer is able
to write the client code directly by referencing the bean code without
waiting for a code generator to generate the home and remote. The developer
modifies the bean? no problem, he can directly uses the new methods in its
FWIW, Bluestone did this. I tried to get them to stop.
Aaron Mulder wrote:
> How do you compile the client code if the home/remote exists only
> in the VM of the running server?
>
> Aaron
>
> On Mon, 12 Nov 2001, marc fleury wrote:
>
>>I know there are many tools out there that do almo
|Just an idea...
Your $20 worth ...
:)
|Why not providing a helper class that would build smart proxies.
|
|The client code is implemented like if it was acting against the source
|class but it would need to use the helper factory to create the
|bean instead
|of using the new operator. The help
Hello Rickard,
Yes I know what you mean, I even read your book when it just came out... So
I certainly cannot be a bad boy ;)
My goal was just to follow the basic intended scheme: EJB access in 10
seconds.
My goal was certainly not to start a fight "should remote methods raise a
subclass of jav
Sacha Labourey wrote:
> Just an idea...
>
> Why not providing a helper class that would build smart proxies.
>
> The client code is implemented like if it was acting against the source
> class but it would need to use the helper factory to create the bean instead
> of using the new operator. Th
Once the classes are generated (written to file) they can be included in
client code ? ... or did I miss something here ? ...
The Together IDE as a ex. "hides/Autogenerates" from the implementation Bean
code ... since it is only stubs ! ...
/peter_f
on 1-11-12 18.16, Aaron Mulder at [EMAIL PROT
a one stop shop
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Rickard Oberg
|Sent: Monday, November 12, 2001 12:39 PM
|To: jBoss Developer
|Subject: Re: [JBoss-dev] [research] a home/remote generator
|
|
|marc fleury wrote:
|
|> well the poin
Just an idea...
Why not providing a helper class that would build smart proxies.
The client code is implemented like if it was acting against the source
class but it would need to use the helper factory to create the bean instead
of using the new operator. The helper factory would access JNDI, g
|What about client code that needs to use those interfaces? Which
For EJB client:
at deployment it is ok.
at compilation he needs the classes (aaron's point)
You still save the bean empty implementation (ejbPassivate etc), jar
generation, xml generation
For webservices client:
You save everythi
marc fleury wrote:
> well the point is more for webservices and the additional invokers.
>
> Axis does this, in a clumsy way.
What would this technique bring you that XDoclet does not?
/Rickard
--
Rickard Öberg
___
Jboss-development mailing lis
What about client code that needs to use those interfaces? Which may be in
the same project or required by another?
Can't a developer write a HelloBean impl with a few xdoclet tags (cut and
pasted from an example) and have a working bean?
--jason
On Mon, 12 Nov 2001, marc fleury wrote:
> I
1 - 100 of 109 matches
Mail list logo
