[JBoss-dev] Support for application clients
Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
What are the advantages of it? It would require a client container. I wonder if any other vendor supports it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Igor Fedorenko Sent: Tuesday, March 04, 2003 11:24 AM To: [EMAIL PROTECTED] Sourceforge. Net (E-mail) Subject: [JBoss-dev] Support for application clients Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Support for application clients
Or maybe noone has implemented it. Every now and again someone asks. Unless it can be done really easily I'm not in favor of trying to add this to jb3.2. I think it can be done really easily in jb4 since we are (or will be) starting a jmx mbean server in the client so we can easily make the app client support using mbeans. I suspect the jmx remoting will also be useful. Are you interested in implementing it? david jencks On 2003.03.04 11:24 Igor Fedorenko wrote: Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
WebLogic 6+ has supported it (though not well documented at all!). Advantage is for GUI applications having access to the same JNDI environment that its web application cousin has - there is a potential to reuse alot of code between the two environments. Shared security mechanisms and client-side trx (not required by the spec, but supported by WLS) would be the other big ones. In the end, nothing huge - personally, I think it is cool that you could have multiple presentation layers bundled up in the EAR and then could run either one. JNLP support for J2EE app clients would rock - I don't think anyone does that yet and it should be (will be in future specs) done that way. B Original Message Follows From: Bill Burke [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Support for application clients Date: Tue, 4 Mar 2003 11:35:32 -0500 What are the advantages of it? It would require a client container. I wonder if any other vendor supports it. _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
Although I did not try it, both WebSphere 5.0 and WebLogic 7.0 both claim to support it. The main advantage that I see is java:comp/env JNDI namespace on the client side. This way it becomes possible to share a lot of code between EJB and non-EJB parts of the app. -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:36 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Support for application clients What are the advantages of it? It would require a client container. I wonder if any other vendor supports it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Igor Fedorenko Sent: Tuesday, March 04, 2003 11:24 AM To: [EMAIL PROTECTED] Sourceforge. Net (E-mail) Subject: [JBoss-dev] Support for application clients Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
i'd just like to toss in my 2 cents and say that it'd be really nice if my web start clients could use the java:comp/env namespace. then i could use the xdoclet util classes that were generated with the logical ejb reference and not the phyisical one. -Original Message- From: Igor Fedorenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:26 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Support for application clients Although I did not try it, both WebSphere 5.0 and WebLogic 7.0 both claim to support it. The main advantage that I see is java:comp/env JNDI namespace on the client side. This way it becomes possible to share a lot of code between EJB and non-EJB parts of the app. -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:36 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Support for application clients What are the advantages of it? It would require a client container. I wonder if any other vendor supports it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Igor Fedorenko Sent: Tuesday, March 04, 2003 11:24 AM To: [EMAIL PROTECTED] Sourceforge. Net (E-mail) Subject: [JBoss-dev] Support for application clients Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
-Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:45 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Support for application clients Or maybe noone has implemented it. Every now and again someone asks. Unless it can be done really easily I'm not in favor of trying to add this to jb3.2. I think it can be done really easily in jb4 since we are (or will be) starting a jmx mbean server in the client so we can easily make the app client support using mbeans. I suspect the jmx remoting will also be useful. The spec does not require clients to be executed in a separate JVM. We can configure application-client-container inside JBoss server. This looks like an easy and non-intrusive solution for 3.2. For 4.0 we can do something different. Are you interested in implementing it? I see your point. ;-) Seriously speaking this is something I am considering but I do not have any immediate plans to do that. david jencks On 2003.03.04 11:24 Igor Fedorenko wrote: Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Support for application clients
Quoting Igor Fedorenko [EMAIL PROTECTED]: -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:45 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Support for application clients Or maybe noone has implemented it. Every now and again someone asks. Unless it can be done really easily I'm not in favor of trying to add this to jb3.2. I think it can be done really easily in jb4 since we are (or will be) starting a jmx mbean server in the client so we can easily make the app client support using mbeans. I suspect the jmx remoting will also be useful. The spec does not require clients to be executed in a separate JVM. We can configure application-client-container inside JBoss server. This looks like an easy and non-intrusive solution for 3.2. For 4.0 we can do something different. I tried that some time ago. The problem is, that application clients have no means to control their life cycle. They cannot be stopped and undeployed. What behaviour would you expect? 1. the application client is deployed 2. the java:comp/env is set up 3. the main method (manifest) is called and thus the application is started. The main method will most probably return immediately. Now you don't have any control over the application anymore. You could run the main method once more but you cannot stop it. Then somebody is removing the application-client.jar, what would you expect to happen now? A possible solution is a blocking main method, that is waiting for a notify on the mainclass as the signal to stop. What you need would be kind of a mix of a service and an application-client. something, that has a life cycle and the configurability of an application-client. However, on the client the situation is different. The JBoss kernel would have a life span equal to that of the application. Holger Are you interested in implementing it? I see your point. ;-) Seriously speaking this is something I am considering but I do not have any immediate plans to do that. david jencks On 2003.03.04 11:24 Igor Fedorenko wrote: Hi, JBoss 3.2 does not seem to support application clients as specified in J2EE Spec, v1.3, section 9. Is there any reason why this is not supported other than nobody has asked it? Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
