MDB using iBus JMS provider
Hi Help please: I've configured iBus//MessageServer to run as Orion's JMS provider, have no problem sending messages from my EJBs clients, but none of them reach my MDB's. In my client, when accessing the topic from the iBus TopicConnectionFactory I specify only the topic name (MyTopic), in the orion-ejb-jar.xml I specify the full location (destination-location=java:comp/resource/MessageServer/MyTopic). Is this correct? Any help much appreciated! udi
Orion's Port?
I need to get orion's port number during to initialization phase. I have an initialization servlet, which is loaded on start-up. It is supposed to get the machine's domain name and the port number, orion is listening to. The servlet is not invoked by the client so I can't use the request info. Even if it ware, the request might have the proxy's port (not orion's) which is not what I need. My fail over architecture depends on the solution to this seemingly simple problem. Does anybody have any suggestions? Roman _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
RE: RE Orion on Macintosh OSX setup
Hmm - I don't know much about aliases, I'm a UNIX head that just happened to have helped a friend get Orion running under OSX. :) Glad to know that works for ya! -Original Message- From: Pauline McNamara To: Orion-Interest Sent: 12/30/01 1:27 PM Subject: Re: RE Orion on Macintosh OSX setup Thanks Aaron, just got a bunch of practice with symlinks along the way to getting Orion set up ;) Not quite sure that what I did is actually the key, nor if I did it exactly right, but here's the story in case others might benefit from it: Located in the orion directory, I used the ln -s command like this: ln -s System/Library/Frameworks/JavaVMFramework/Versions/CurrentJDK/Classes/cl asses.jar tools.jar This created not a file, but an alias folder named tools.jar in the orion directory. In the OS's Finder program, double clicking on the folder gave an error message stating that it couldn't be opened because the original item could not be found. I put this folder in the trash. Afterwards Orion worked, but it may have been for other reasons. Could it be that the symlink still exists, even if there isn't an alias for it? Thanks for the tips, it's encouraging just to know that these kinds of things are being done successfully with OSX (didn't have to go out and buy a PC, yet). Regards, Pauline --- Aaron Tavistock wrote: I've gotten Orion setup on OSX and there are definately some nuances to it because of Apple's wacky implementation of things. On the tools.jar - you'll need to symlink the apple version of the tools.jar into the Orion directory. THough I can't remeber what apple called the file, I know this worked fine when I found the file (it might be classes.zip?). On the permission denied - its definately because you are trying to access a priveledged port (e.g. port 80). The change you made to the configuration file will work if you make sure to follow standard XML syntax and put the value in quotes (port=8080). -Original Message- From: Pauline McNamara [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 27, 2001 5:57 AM To: Orion-Interest Subject: Orion on Macintosh OSX setup Patience with a newbie please... I'm setting up Orion on a Mac with OSX 10.1 (so J2SE 1.3.1) and have come upon 2 stumbling blocks. Any advice is much appreciated. First: According to the installation instructions, the JDK's tools.jar file should be copied into the Orion directory. On the OSX the JDK is structured differently and the tools in the form of a .jar file are not to be found. Any hints? Second: I went ahead and started orion with and get the following error message: Error starting HTTP-Server: Permission denied Orion/1.5.2 initialized I understand that I can't access port 80 when not logged in at the root, and that I probably have to alter the web.xml file to change the port (to a port over 1024). I tried adding this: but got the same message. Could someone please point me in the right direction? Thanks in advance, Pauline __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com
RE: CMP Entity Bean Craziness
Mike - If I intentionally bundle an orion-ejb-jar.xml file in with my EJBs, thats effectively saying that these are the parameters I care about and should not be derived by Orion. I would presume that since these are being bundled with my EJB package they are values that are somewhat global to begin with otherwise they probably shouldn't be bundled in the package. So I would maintain that changes should be incorporated immediately without having to manually remove the old file. I can certainly see where there might be places where a deployment specific change has been hand edited in and how that would get nuked. But it still seems like it strips away the ability to drop a jar and run. Maybe the solution is what Morten suggested, a configuration file for specific deployment that is included in each overwrite. It also seems like 'always overwriting' would make rapid development easier (without using XDoclet). Magnus and Karl - theres a fat feature request here. :P Aaron -Original Message- From: Mike Cannon-Brookes To: Orion-Interest Sent: 12/30/01 4:35 AM Subject: RE: CMP Entity Bean Craziness On Sun, 2001-12-30 at 07:50, Ed Brown wrote: Quoting Aaron Tavistock [EMAIL PROTECTED]: Mike - Since this is a generated file in a deployment directory shouldn't it always be overwritten if there is a change in one of the package deployment descriptors? The only reason it would be a pain in the ass is if you changed the generated file to suit your needs and did not change the one you bundle with your package. Which is my thought as well. Apologies but that's not really the way I see it. The deployment files are specific to _each_ deployment - for example if you deploy the same EAR on multiple machines (ie in a cluster) you would want different deployment files on each machine. Thus changing the one in the EAR would overwrite all deployment files. As Hani (I think) mentioned, it's easy to get XDoclet to generate your deployment file, and Ant to remove the old one - if you're concerned about development speed. If this is intended behavior, IMHO it is significantly less intuitive. Its kind of like saying a class should only be recompiled if you delete the class before recompiling, where one would expect that changing the source would be enough. Just my two cents. Agreed. In fact, I believe that implementation stinks. Why go through the hassle of writing the orion-ejb-jar.xml file and specifying the fields if the server re-writes the file as it sees fit? There are some misconceptions here - the server will not 'rewrite deployment files as it sees fit', in fact it takes any settings in orion-ejb-jar.xml and builds ontop of those. The easiest way to build an orion-ejb-jar.xml file for deployment is to: - deploy your EAR without it - copy the created orion-ejb-jar.xml into your source tree - remove any sections you don't want to customise (thereby letting Orion autogenerate them - for example it's usually nicest to specify a default datasource in orion-application.xml and let Orion take care of the datasources in orion-ejb-jar.xml automatically) - customise any you do (ie field names, table names etc) - delete the deployed orion-ejb-jar.xml - redeploy This process only really needs to be done once. At all other times the deployed file should work, except when you modify the orion-ejb-jar.xml then you delete it before redeployment (as above this is usually rare occurrence, if not - use XDoclet to generate and Ant to delete it every build if you want). As for the class analogy it's very different. Classes are compiled once, and 100% autogenerated, deployment files are created and altered by the server continually and are not fully autogenerated (see J2EE spec roles definitions). Also compiled classes are the same in all occurrences (or should be ;)) whereas deployment files are certainly not. Hope this helps clear things up - I do like this healthy debate on the topic though, please tell me if the above sounds unreasonable. Cheers, Mike -- Mike Cannon-Brookes :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World
RE: MDB using iBus JMS provider
you have to write resource wrapper around the external jms implementions factory. see the mail archive for an example -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of udi h bauman Sent: Tuesday, January 01, 2002 12:51 PM To: Orion-Interest Subject: MDB using iBus JMS provider Hi Help please: I've configured iBus//MessageServer to run as Orion's JMS provider, have no problem sending messages from my EJBs clients, but none of them reach my MDB's. In my client, when accessing the topic from the iBus TopicConnectionFactory I specify only the topic name (MyTopic), in the orion-ejb-jar.xml I specify the full location (destination-location=java:comp/resource/MessageServer/MyTopi c). Is this correct? Any help much appreciated! udi
