[JBoss-user] [EJB3] NoSuchMethodError upon remote invocation
Hi, When attempting remote invocation of a stateless session bean... I'm getting the exception below. Has anyone seen this? Thanks, Sam Exception in thread main java.lang.NoSuchMethodError: org.jboss.aop.joinpoint.MethodInvocation.init([Lorg/jboss/aop/ advice/Interceptor;JLjava/lang/reflect/Method;Ljava/lang/reflect/ Method;Lorg/jboss/aop/Advisor;)V at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke (StatelessRemoteProxy.java:68) at $Proxy0.findAll(Unknown Source) at tetrahex.pistol.ui.PistolController.getNiches (PistolController.java:53) at tetrahex.pistol.ui.PistolApp.refreshNiches(PistolApp.java:94) at tetrahex.pistol.ui.PistolApp.init(PistolApp.java:84) at tetrahex.pistol.ui.PistolApp.main(PistolApp.java:239) --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] general deployment question
Concerning the ejb-link The EJB2.0 spec clearly states (20.3.2) that ...the target enterprise bean can be in any ejb-jar file in the same J2EE application as the referencing application component. Exactly the same is in J2EE 1.3 spec (J2EE.5.3.2) According to me this means, in the same EAR! This is exactly what I wanted for my application, but it doesn't seems to work in JBoss 3.0.0 (beta2) (see my posting on Friday)!!! Eric just mentioned he got it to work in JBoss (which version please?) and I'm very curious about it! So maybe you can give me a hint on how I can get it to work in JBoss? Feel sorry for you 'bout Borland ;-) Sam. From: Eric Kaplan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sun, 10 Mar 2002 11:46:39 -0500 Subject: [JBoss-user] general deployment question This is a multi-part message in MIME format. --=_NextPart_000_0004_01C1C829.3DCF61A0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit We have built a large number of session and bmp entity beans as part of our technology framework. For historical reasons we organized each entity bean (along with home and remote interfaces and primary key class) into a jar. Same with the session beans. In the deployment descriptors, we used the ejb-link tag to identify ejb references, even though the references were not in the same jar. Again, this was because the documentation at the time on all this stuff was not very good and we just had examples to go off of. Somehow, we get away with this in jboss, even though it's not correct to use ejb-link for references outside of a jar. Note, all the jar files, and there are about 30 now, are packaged into an ear. We then have a jboss.xml per jar which basically defines any jdbc references we may have as well as declares the jndi names for each of the beans in the ejb-jar.xml. We have a client who insists on using borland's app server (let's not get into why here...) and borland is choking, and i think rightly so, because the ejb-link references are to beans outside of the jar. My question is, why was i able to get away with this in jboss. In a related area, we have a fair number of helper classes that all these beans use (base classes for our beans, data structures to hold the data passed back to the client apps, etc.). Right now, we add jar files holding these classes, as well as third party jars, to the jboss classpath. Is this the right thing to do, or is the right thing to stuff these helper classes into each jar (or the ear file)... I apologize if this question seems basic, but we've spent more time just trying to make things work and less trying to understand every single aspect of this. Things are calming down a bit right now and I'd like to reexamine our approach here. Most of the documentation out there deals with relatively simple applications, or gets bogged down with discussions of war files, etc. (we're not a web app, at least not yet). Any help or suggestions would be much appreciated. As I've said, we've managed to get all this to work, though I think we have some configuration issues yet to deal with. Thanks Eric Kaplan Armanta, Inc. 55 Madison Ave. Morristown, NJ 07960 Phone: (973) 326-9600 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] ejb-local-ref from an MDB to an Entity in the same EAR, but diffe rent ejb jars (jboss 3.0.0beta2)
Indeed, I got it to work with ejb-ref and hence remote interfaces even in different jars, and as I recall that means the jboss.xml contained the JNDI name of the referenced remote home interface BUT... why do we have local interfaces for!? I tought to speed up intra-JVM calls and since my referencing and referenced beans are running in the same JBoss server, I want to use ejb-local-ref and that I still didn't get to work. Sam. -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: maandag 11 maart 2002 10:32 To: 'Sam De Backer'; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] ejb-local-ref from an MDB to an Entity in the same EAR, but diffe rent ejb jars (jboss 3.0.0beta2) Hello, everybody! To Sam: Have you figured it out? The cause could be the beans are in different jars and you use ejb-local-ref. It should work in case of remote interfaces and: ejb-ref in ejb-jar.xml and jboss.xml or place your beans in the same jar file and use ejb-local-ref. To all: Mastering EJB II says about ejb-link this: ... The ejb-name of the bean we're referring to. Note: You can also refer to beans in different jar file, by using a syntax such as ../products/product.jar#ProductEJB. How should it be applied to JBoss? If there is declaration of ejb-ref in ejb-jar.xml and neither of ejb-ref in jboss.xml and ejb-link in ejb-jar.xml is specified, jboss complains that either ejb-ref in jboss.xml or ejb-link in ejb-jar.xml must be specified. I've made to jar files each containing one SLSB with remote interfaces. ReferencingBean references ReferencedBean and calls its method. Declaring ejb-ref in ejb-jar.xml and jboss.xml it works. But when I tried to use ejb-link in ejb-jar.xml instead of ejb-ref in jboss.xml it said me this: 2002-03-11 11:17:10,207 DEBUG [org.jboss.ejb.StatelessSessionContainer] Binding an EJBReference ejb/Referenced 2002-03-11 11:17:10,207 DEBUG [org.jboss.ejb.StatelessSessionContainer] Binding ejb/Referenced to internal JNDI source: referenced-ejb.jar#ReferencedBean 2002-03-11 11:17:10,207 ERROR [org.jboss.ejb.StatelessSessionContainer] Exception in service lifecyle operation: create org.jboss.deployment.DeploymentException: Bean referenced-ejb.jar#ReferencedBean not found within this application. I guess I reference referenced-ejb.jar incorrectly. Could someone shed a light? Thanks in advance! alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sam De Backer Sent: Friday, March 08, 2002 5:10 PM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: [JBoss-user] ejb-local-ref from an MDB to an Entity in the same EAR, but diffe rent ejb jars (jboss 3.0.0beta2) I would like to call an Entity bean from within an MDB and added an ejb-local-ref in my MDB's ejb-jar.xml I also added an ejb-link inside that ejb-local-ref with the name of my Entity bean. Everything packed up in an EAR. When deploying to JBoss i get an org.jboss.deployment.DeploymentException (Bean Workplace not found within this application.) Isn't this supported in JBoss? Or am I overlooking things? Sam. The ear struct: -- lab04app.ear - META-INF - application.xml (containing modules lab03.jar and lab04.jar) - lab03.jar - lab04.jar --- lab03.jar - META-INF - ejb-jar.xml - jboss.xml - lab03 - ... (classes of lab03 package, including the Workplace Entity bean) lab04.jar - META-INF - ejb-jar.xml (containing ejb-local-ref+ejb-link to Workplace) - jboss.xml - lab04 - ... (classes of lab04 package calling Workplace bean through ref) the log: ... 2002-03-08 15:49:41,090 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying lab03.jar 2002-03-08 15:49:41,090 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/d eploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.la b04app.ear^/la b04.jar 2002-03-08 15:49:41,220 DEBUG [org.jboss.ejb.EJBDeployer] Verifying njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/d eploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.la b04app.ear^/la b04.jar 2002-03-08 15:49:41,230 DEBUG [org.jboss.ejb.EJBDeployer] Deploying: njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/d eploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.la b04app.ear^/la b04.jar 2002-03-08 15:49:41,230 INFO [org.jboss.ejb.EjbModule] Creating 2002-03-08 15:49:41,230 DEBUG [org.jboss.ejb.EjbModule] Application.start(), begin 2002-03-08 15:49:41,230 DEBUG [org.jboss.management.j2ee.EjbModule] EjbModule.create(), server name: J2EEServer=Single 2002-03-08 15:49:41,240 DEBUG
[JBoss-user] ejb-local-ref from an MDB to an Entity in the same EAR, but different ejb jars (jboss 3.0.0beta2)
I would like to call an Entity bean from within an MDB and added an ejb-local-ref in my MDB's ejb-jar.xml I also added an ejb-link inside that ejb-local-ref with the name of my Entity bean. Everything packed up in an EAR. When deploying to JBoss i get an org.jboss.deployment.DeploymentException (Bean Workplace not found within this application.) Isn't this supported in JBoss? Or am I overlooking things? Sam. The ear struct: -- lab04app.ear - META-INF - application.xml (containing modules lab03.jar and lab04.jar) - lab03.jar - lab04.jar --- lab03.jar - META-INF - ejb-jar.xml - jboss.xml - lab03 - ... (classes of lab03 package, including the Workplace Entity bean) lab04.jar - META-INF - ejb-jar.xml (containing ejb-local-ref+ejb-link to Workplace) - jboss.xml - lab04 - ... (classes of lab04 package calling Workplace bean through ref) the log: ... 2002-03-08 15:49:41,090 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying lab03.jar 2002-03-08 15:49:41,090 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/deploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.lab04app.ear^/la b04.jar 2002-03-08 15:49:41,220 DEBUG [org.jboss.ejb.EJBDeployer] Verifying njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/deploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.lab04app.ear^/la b04.jar 2002-03-08 15:49:41,230 DEBUG [org.jboss.ejb.EJBDeployer] Deploying: njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/deploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.lab04app.ear^/la b04.jar 2002-03-08 15:49:41,230 INFO [org.jboss.ejb.EjbModule] Creating 2002-03-08 15:49:41,230 DEBUG [org.jboss.ejb.EjbModule] Application.start(), begin 2002-03-08 15:49:41,230 DEBUG [org.jboss.management.j2ee.EjbModule] EjbModule.create(), server name: J2EEServer=Single 2002-03-08 15:49:41,240 DEBUG [org.jboss.management.j2ee.J2EEDeployedObject] File: njar:file:/C:/experimental/jboss-3.0.0beta2/server/mysql/tmp/deploy/C/experi mental/jboss-3.0.0beta2/server/mysql/deploy/lab04app.ear/70.lab04app.ear^/la b04.jar, descriptor: META-INF/ejb-jar.xml 2002-03-08 15:49:41,240 DEBUG [org.jboss.management.j2ee.EjbModule] Create EJB-Module, name: lab04.jar, application: jboss.management.single:J2EEDomain=Manager,J2EEServer=Single,name=lab04app.e ar,type=J2EEApplication, dd: ?xml version=1.0? !DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN http://java.sun.com/dtd/ejb-jar_2_0.dtd; ejb-jar enterprise-beans message-driven ejb-nameWorkplaceCreator/ejb-name ejb-classlab04.WorkplaceCreatorBean/ejb-class transaction-typeContainer/transaction-type message-driven-destination destination-typejavax.jms.Queue/destination-type /message-driven-destination ejb-local-ref ejb-ref-nameejb/local/Workplace/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type local-homelab03.WorkplaceLocalHome/local-home locallab03.WorkplaceLocal/local ejb-linkWorkplace/ejb-link /ejb-local-ref /message-driven /enterprise-beans /ejb-jar 2002-03-08 15:49:41,240 DEBUG [org.jboss.management.j2ee.J2EEManagedObject] getObjectName(), name: jboss.management.single:J2EEDomain=Manager,name=lab04.jar,J2EEServer=Single, J2EEApplication=lab04app.ear,type=EjbModule 2002-03-08 15:49:41,240 DEBUG [org.jboss.management.j2ee.J2EEManagedObject] postRegister(), parent: jboss.management.single:J2EEDomain=Manager,J2EEServer=Single,name=lab04app.e ar,type=J2EEApplication 2002-03-08 15:49:41,240 INFO [org.jboss.ejb.EjbModule] Deploying WorkplaceCreator 2002-03-08 15:49:41,261 DEBUG [org.jboss.ejb.MessageDrivenContainer] Begin java:comp/env for EJB: WorkplaceCreator 2002-03-08 15:49:41,261 DEBUG [org.jboss.ejb.MessageDrivenContainer] TCL: java.net.URLClassLoader@72be27 2002-03-08 15:49:41,261 DEBUG [org.jboss.ejb.MessageDrivenContainer] Binding an EJBLocalReference ejb/local/Workplace 2002-03-08 15:49:41,261 DEBUG [org.jboss.ejb.MessageDrivenContainer] Binding ejb/local/Workplace to bean source: Workplace 2002-03-08 15:49:41,261 ERROR [org.jboss.ejb.MessageDrivenContainer] Serious error in init: org.jboss.deployment.DeploymentException: Bean Workplace not found within this application. at org.jboss.ejb.Container.setupEnvironment(Container.java:982) at org.jboss.ejb.Container.create(Container.java:497) at org.jboss.ejb.MessageDrivenContainer.create(MessageDrivenContainer.java:159) at org.jboss.ejb.Container.invoke(Container.java:783
[JBoss-user] CMP2.0 - CMR-fields sometimes (reproduceable!) not persisted in DB (jboss3.0.0beta)?
: Rows affected = 1 What am I doing wrong? Sam ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Can jndi.properties be remote?
Hello JBoss, We are currently investigating whether or not we can abstract also the access to a remote naming server. Basically, we are looking for a way to load the JBoss system JNDI InitialContext() through a remote jndi.properties type file (or just its information). We are planning to have lots of different service from lots of different machines, and we are planning to keep everything straight through extensive use of jndi/jnp. This ability would allow lots of JBoss instances to point to a configurable common name space. Is it possible to refer to jndi.properties through URL? If so, how can this be configured? Our hopes are to avoid having to set system properties manually with the correct configuration prior to 'new InitialContext()'. Thanks in advance for your comments. Sam ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Anyone know how to federate across multiple jnp ...
I believe that I am close, but I still have no cigar. Having read most of the jnp code, I realize that JNP has implemented LinkRef and not Reference as I first thought. In looking through org.jnp.client.Mail, I see that LinkRef is supportted and that the use of it is to bind a LinkRef object with an embedded URL. This URL may start with jnp://somemachine:someport. So I run an experiment with 2 separate instances of JBoss running on the same machine and I have Naming enabled on two different ports (1099, 1098). I basically do a bind of: env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, org.jnp.interfaces.NamingContextFactory); env.put(Context.PROVIDER_URL, syan.zantaz.com:1099); env.put(Context.URL_PKG_PREFIXES, org.jnp.interfaces); InitialContext ic = new InitialContext(env); ... create a couple of intermediate levels of name foo ... ... create a NamingContext nc pointing to foo ... nc.bind(linksomewhere, new LinkRef(jnp://syan.zantaz.com:1098/foo1)); // this already exists ... later in the code I do ... Context ctx = ic.lookup(foo/linksomewhere); At this point, I am getting the following exception. Am I using this incorrectly? javax.naming.NameNotFoundException: foo1 not bound at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC all.java:245) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:298) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:282) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:370) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:282) at javax.naming.InitialContext.lookup(InitialContext.java:350) at com.zantaz.base.temp.Test6.run(Test6.java:89) at com.zantaz.base.temp.Test6.main(Test6.java:21) In walking through the code, it looks like env for the InitialContext is reapplied for LinkRef. This seems incorrect to me, but I don't claim to understand everything. Sam -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 06, 2001 11:41 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Anyone know how to federate across multiple jnp ... jnp is the name of the jndi provider used by JBoss and is the protocol url just as t3 is the weblogic's. The jnp.properties file is used as the default values. If you don't set the port values via the NamingService mbean attributes then the jnp.properties file is used. This jboss.jcml entry: mbean code=org.jboss.naming.NamingService name=DefaultDomain:service=Naming / along with this jnp.properties file: ### JNP server configuration jnp.port=1299 jnp.rmiPort=0 results in the naming service starting on port 1299: ... [Naming] Starting [Naming] Starting jnp server [Naming] Started jnpPort=1299, rmiPort=0 [Naming] Naming started on port 1299 [Naming] Started The - Original Message - From: Guy Rouillier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 07, 2001 10:53 AM Subject: Re: [JBoss-user] Anyone know how to federate across multiple jnp ... Properties env = new Properties(); env.setProperty(Context.INITIAL_CONTEXT_FACTORY, org.jnp.interfaces.NamingContextFactory); env.setProperty(Context.PROVIDER_URL, jnp://localhost:1099); env.setProperty(Context.URL_PKG_PREFIXES , org.jboss.naming:org.jnp.interfaces); InitialContext ctx = new InitialContext(env); I left this in jboss.jcml: !-- JNDI -- mbean code=org.jboss.naming.NamingService name=DefaultDomain:service=Naming attribute name=Port1099/attribute /mbean and changed jnp.properties to this: jnp.port=1299 jnp.log=true My client could connect with this in its jndi.properties file: java.naming.provider.url=w2k-pro OR java.naming.provider.url=w2k-pro:1099 but failed when I put this in jndi.properties: java.naming.provider.url=jnp://w2k-pro:1299 with the following error: Exception caught: javax.naming.ServiceUnavailableException: jnp [Root exception is java.net.UnknownHostException: jnp] Obviously, I'm confused. (1) What is the relationship between jnp and jndi? (2) When is jnp used? In the default configuration, I only see the naming service specified in the jboss.jcml mbean started, as follows: [Naming] Starting [Naming] [Naming] Started on port 1099 [Naming] Naming started on port 1099 [Naming] Started When does jnp come into play, and when does jnp.properties get used
[JBoss-user] Anyone know how to federate across multiple jnp ...
Has anyone tried creating a URL reference to bind in jnp such that it references another jnp on another instances of JBoss? I get confused when looking for a URL scheme name on a name space based on jnp (i.e. ldap would look like ldap:/machine/dc=root). All examples while using jnp don't require a scheme name. Does anyone know if jnp supports url references? Any help is appreciated! Sam ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] CORBA callbacks into JBoss
So why not RMI/IIOP and interoperate Corba objects as RMI objects? You get to keep EJB/RMI and you get to speak CORBA. JNDI, then can be your friend for publication and rendezvous of service. This is mho. Sam -Original Message- From: John Camelon [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 26, 2001 11:59 AM To: Jboss-User Subject: RE: [JBoss-user] CORBA callbacks into JBoss the unfortunate aspect of my situation is that the CORBA component is a) being developed concurrently (and thus not being legacy) and b) the more definite technology choice for the moment. CORBA is a given (in fact, its a standard for the piece i am integrating with); i need some sort of application server mechanism to be able to provide a hot-deploy run-time environment to interact with the CORBA piece. part of me considers writing a dumbed-down simple alternative to an EJB container as being the lesser of two evils compared to trying to implement N x N callback proxying. thank you for your help though. johnc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sam Sent: Thursday, April 26, 2001 1:52 PM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] CORBA callbacks into JBoss John, I believe that we may have similar problems to solve from your brief description below. Our original solution was completely CORBA based. I am also interested in others comments in the area. We are now rearchitecting and taking a serious look as to why CORBA and why RMI. The why RMI is not hard since EJB RI is based on this model. The harder question is RMI/JRMP or RMI/IIOP? But because CORBA can interoperate cross platform and language and that some environments (Microsoft Exchange; Lotus Domino) may not be friendly to a java based extension, we are forced into keeping both technologies alive and happy. We chose to divide and conquer. Corba based services that are not subject to rearchitecture can be made into MBean services instead of EJB. Legacy code that it is, it is still too daunting to rewrite everything to EJB all at once. It is not hard to make Corba services use RMI(through session beans) much the same way servlets do. The other way around, however, can be done, but it is not trivial. We also have leveraged greatly JNDI much the same way JBoss/EJB itself does in both exposure and rendezvous of services through an open Naming interface. Both Corba and RMI can do this at different levels based on what you actually require. A simple way of doing this is to use JNDI as a Naming Service for both RMI and Corba remote object. This may not get you everything you are looking for, however, you may not have to be forced into throwing out the baby with the bath water ;-) Sam -Original Message- From: John Camelon [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 26, 2001 9:05 AM To: Jboss-User Subject: [JBoss-user] CORBA callbacks into JBoss hello list: one of the reasons that i want to use an application server such as JBoss is to take advantage of the runtime environment that EJBs provide, particularly the pooling and scaling aspects of EJB. also, the hot deploy mechanism is much valued in the run-time scenarios i am looking at. however, one of the pieces that i wish to integrate with has a CORBA interface and supports a callback model. some CORBA calls will be synchronous, while others will have at least one (if not several) asynchronous callbacks into EJB land. this seems like a bit of a misfit, unfortunately. the only scenario that i can see possibly working is to proxy the external CORBA interface into some kind of layer that manages the EJB callbacks. at first glance i do not see, however, how this would allow for easy scaling the way that EJBs inherently allow. also, it appears to require a lot of knowledge about the EJBs trying to use the CORBA in order to resume the callbacks. does anyone have any suggestions for me? is this scenario too ill fit for EJB? johnc ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] jBoss-Multiple Instances-LDAP Sharing
I am interested in others comments as well. We have the same interest. I have had good luck in using the command line parameter settings for starting JBoss and I can actually get multiple instances running. Things get more complicated as one adds their own code. a) I found that the default in starting JBoss usings both conf and conf/default as the configuration directories. Simply start by making an exact copy of default using any other name (i.e. default2). Then you need to resolve all single global resources on the machine such that you don't collide with the first instance of JBoss (unless that is what you wanted). An example is the admin web page port. When starting JBoss, just add default2 as the first parameter. There is also a second parameter called the patchDir which I believe extends the classpath, however, I have not yet had a need for this nor have I figured this out yet. b) I am currently using iPlanet(Netscape) Directory Server 5.0beta. I can indeed share the same JNDI name space. The java.sun.com tutorial on JNDI covers LDAP setup. The examples all involve Netscape DirectoryServer so I was not surprized that everything I've tried works. Hope this helps. Sam -Original Message- From: K.V. Vinay Menon [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 19, 2001 7:24 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] jBoss-Multiple Instances-LDAP Sharing Hi, A couple of basic questions regarding running jBoss in a production environment a) Can I run multiple instances of jBoss on a single server? If so what changes are needed in the configuration? b) Can jBoss integrate with external LDAP products like ADS or Netcape LDAP? If this is possible can multiple jBoss servers share the same JNDI namespace? Would appreciate if anyone could some light on this. Regards, Vinay Menon ___ Get 100% private, FREE email for life from Excite UK Visit http://inbox.excite.co.uk/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] How can I use a properties file?
Hi, In ejb project(include .war file), Can i use a properties file? because I think properties file is convenient. if i can use a properties file, where can i put it? and how can i use it in a java file? thanks, Sam Liu. http://lists.sourceforge.net/lists/listinfo/jboss-user ,x%I,+-. aX( ~zwXb?,
RE: [JBoss-user] persistent JNDI
Title: RE: [JBoss-user] persistent JNDI Sylvia, This is very possible, however, I am struggling with this one myself. I have successfully hooked up JBoss 2.1 using iPlanet Directory Server 5.0beta. You can use LDAP as one means of persistence. I am able to do lookups through the External/Context, however, when trying to do bind (write), I currently get errors with LDAP schema. The same bind to jnp works. Another means is a database through JDBC. Go through the FAQ on JBoss site. Let me know if you choose LDAP. Sam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 10:12 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] persistent JNDI Hi All, Is it possible to make JNDI context naming persistent between server start ups? I created several subcontexts, and when I reboot the server, the information is gone. Is there any mechanism to persist the user contexts? Thank you Sylvia ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
re: [JBoss-user] Why can not I use my mySQL data source?
thanks to danch, when I use Jboss2.1 beta, all of things are OK. thanks to Ken Jenks. in addition: Perhaps it is a silly problem. I want to know why the file "jboss.conf" and other likewise ***.conf files use the format of XML? but when I comment this line in jboss.conf like this: MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar" CODEBASE="../../lib/ext/" !-- Comment by Sam Liu ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-3.2.1/lib/" -- ARG TYPE="java.lang.String" VALUE="../../../tomcat/lib/" ARG TYPE="java.lang.String" VALUE="Tomcat" /MLET i found that jboss can not start up tomcat. that is to say ***.conf do NOT support XML parsering. when I correct it like this: MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar" CODEBASE="../../lib/ext/" !-- ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-3.2.1/lib/" -- ARG TYPE="java.lang.String" VALUE="../../../tomcat/lib/" ARG TYPE="java.lang.String" VALUE="Tomcat" /MLET it is OK. So, if all of the files of "***.conf" can be parsered on html or xml format, perhaps is it better? --- origional info-- First, I assume you're running JBoss 2.0? If you're running 2.1/2.2, the config is a little different. ... ,ºÇ«¨¥x%ËI,ºÇ«+-²Ê.Ç¢¸ ëa¶ÚþX¬¶Ë(º· ~àzwþX¬¶ÏåËbú?º,²ë
re: [JBoss-user] Problem about Servlet calling ejb
thanks to Ken Jenks!
but I can still not run this Servlet.
In fact I have ever used the jndi name "interest/Interest"
just like that your article had refered to.
And after i run jndiView.jar, I can find that : "interest/Interest"
if I use client application to call the Interest bean, all OK.
When I use jboss2.0-final, the Servlet output correct result.
but the client application do not run rightly, however it is not
my concern.
I guess that the Interest Bean had been deployed rightly.
but the servlet can not find the ejb by the jndi name.
I hope your help again!
(I have download the JBoss_tomcat.zip, the instructions tell me no need to config.)
best regard,
Sam Liu
Your debugging string, sHome, indicates that you got an InitialContext(),
but that there was probably an exception when you tried to get a reference
to the Interest bean (because you never did get to the line which sets
sHome = "2"). I suspect that means that your Interest bean is not deployed,
or if it is deployed, it has a different name under JNDI namespace.
Change to the jboss/bin directory and run this command:
java -jar jndiView.jar | more
(You should put that in a script or batch file. In fact, this script/batch
file should be part of the standard distribution.)
If the Interest bean is deployed, you should see its name listed.
Check the jBoss log and see if there's an exception during deployment. If
you don't see one, you can change the logging MLET code in
jboss/conf/default/jboss.conf:
MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar"
CODEBASE="../../lib/ext/"
ARG TYPE="java.lang.String" VALUE="Information,Warning,Error"
ARG TYPE="java.lang.String" VALUE="[{2}] {4} {1} {3}"
/MLET
(See how I added {1} and {3}.)
MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar"
CODEBASE="../../lib/ext/"
ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error"
ARG TYPE="java.lang.String" VALUE="[{2}] {4} {1} {3}"
/MLET
(Again, I added {1} and {3}.)
Now look at the window from which you ran jBoss or file jboss/log/server.log.
-- Ken Jenks, http://abiblion.com/
Tools for reading.
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user$,²ë ®f¢)à+-$,²ë ®X¬¶Ë(º· ~àzwÛiÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèþ6è²Ë¬z
re: [JBoss-user] Problem about Servlet calling ejb
thanks to Ken! Oh, I have just find how to run the Servlet rightly. I am under windows 2000 If I run "run.bat " all is OK, but I always run "java -jar run.jar", so I can not get it. that is to say, we must put the "run.jar" in the CLASSPATH. Sam Liu. 2001/04/04 ,ºÇ«¨¥x%ËI,ºÇ«+-²Ê.Ç¢¸ ëa¶ÚþX¬¶Ë(º· ~àzwþX¬¶ÏåËbú?º,²ë
re: [JBoss-user] Problem about Servlet calling ejb
thanks, I have solved it ! Sam Liu === [EMAIL PROTECTED] origional mail- I guess that the Interest Bean had been deployed rightly. but the servlet can not find the ejb by the jndi name. Something I didn't cover in my original "Interest Bean" servlet article was how to map an EJB's name to a jBoss JNDI name using jboss.xml. You can change the names like this: ?xml version="1.0" encoding="ISO-8859-1"? jboss securefalse/secure container-configurations / resource-managers / enterprise-beans entity ejb-nameInterest/ejb-name jndi-nameinterest/Interest/jndi-name configuration-name/configuration-name /entity /enterprise-beans /jboss Name this file jboss.xml and put it in the same directory as ejb-jar.xml and you can call your beans anything you want. -- Ken Jenks, http://abiblion.com/ Tools for reading. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user$,²ë ®f¢)à+-$,²ë ®X¬¶Ë(º· ~àzwÛiÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèþ6è²Ë¬z
RE: [JBoss-user] iplanet
Title: RE: [JBoss-user] iplanet Just a warning if you plan on using Linux. Since AOL/Netscape formed their alliance with Sun, iplanet has been systematically dropping Linux support on all product lines. Notice that Directory Server 5.0beta does not have the Linux version. ;-) Sam -Original Message- From: Roman Seidl [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 29, 2001 1:00 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] iplanet Hello, Anyone of you know iplanet appserver? I'd like to know if it has troubles, disadvantages (besides the price) etc. Pls answer to my private email as this is rather off-topic (sorry for that). -- Best regards, Roman mailto:[EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
