Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 63991 invoked from network); 3 Oct 2007 04:50:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 04:50:44 -0000 Received: (qmail 46517 invoked by uid 500); 3 Oct 2007 04:50:27 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 46489 invoked by uid 500); 3 Oct 2007 04:50:27 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 46478 invoked by uid 99); 3 Oct 2007 04:50:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2007 21:50:27 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.147.95.83] (HELO smtp120.plus.mail.sp1.yahoo.com) (69.147.95.83) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 03 Oct 2007 04:50:28 +0000 Received: (qmail 72535 invoked from network); 3 Oct 2007 04:50:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=B84tQ9z4fItyxGH+juOXzRe7KPYvMBmR8oH4xybi5oVdjVvq//ZgZSD7Q+eJOGeVDSfzmbhZvw6Ad4V7EHMrgzDlLvqZ/pPRHMxWSl7c0IGq62YWKdHBh65xYzSwHKNAnrNLwS5LHomykEY9sYYiKSrNd+Ry7dvPHonsj1hQxko= ; Received: from unknown (HELO ?192.168.1.101?) (david_jencks@67.102.173.8 with plain) by smtp120.plus.mail.sp1.yahoo.com with SMTP; 3 Oct 2007 04:50:07 -0000 X-YMail-OSG: opt0ESEVM1k9Wr6Uwb01irqH6nKVkWkT9hnanGfUfGOgwUAmxytPhEyVpZNAn4AGVkRJKAe4Xg-- Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2AA58B55-8D5B-4975-9D1D-8B56DBF71E69@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: Q: MDB Application cannot find Interface defined in RAR file Date: Tue, 2 Oct 2007 21:50:10 -0700 To: user@geronimo.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Hi Ed, I'm sorry you've been having such a hard time getting this to work. Email is not always the most efficient form for dialog :-). If you can get on IRC sometime when I am around I can probably help sort things out more quickly or if IRC is unavailable to you but you have some time to work through this more continuously we could try that.... having a couple days between emails its difficult to remember exactly what the context of your questions is. One of the things I don't like much about the console deployer is that it tends to conceal the causes of errors and sometimes the fact of errors :-). I generally get better feedback from the command line deployer -- also a transcript shows unambiguously what you tried to do. I noticed a couple o things in the stuff you sent some of which might be causing problems. 1. There are a lot of jar dependencies in your geronimo plan for the rar... does this mean all these jars are needed by the rar but are not included in it? If the jars are included in the rar they should not be needed as dependencies. Knowing exactly what is in the rar would be helpful 2. The resource adapter has no outbound connectors and all the ResourceAdapter properties are set to their defaults from ra.xml.... this is as intended? 3. the openejb-jar.xml has a dependency on a rar. That would be a dependency on a rar that is deployed separately, not the one in the ear. If this is really the openejb-jar.xml from the ear attempt you should remove that dependency. 4. the resource-link in the mdb config does not appear to be pointing to the resource adapter you configured in the geronimo- application.xml.... maybe its pointing to the one in the standalone rar that the openejb-jar.xml is depending on? IIUC you would want TreEventBean InboundSVEvents 5. There is no additional configuration of the inbound ra in the openejb-jar.xml so this must mean that all the necessary properties (including what the message-listener interface is) is set in the ejb- jar.xml or in annotations? BTW standalone should be just about the same as non-standalone except for needing a dependency from the ejb plan to the rar plan.... but then, in theory, theory and practice are the same... thanks david jencks On Oct 2, 2007, at 8:18 PM, Ed Hillmann wrote: > Ok, I've given up on trying to deploy the RAR stand-alone. I can't > figure out how to get the classloader to include classes from all of > the JAR files in the RAR file. I've tried adding Class-Path: entries > to various Manifests, with no luck. And I don't seem to be able to > find any documentation about how to customise the class loading for > v2. > > So, I'm trying to deploy the RAR file with the EAR file, simply > because it looks like there is documentation for it. So, I'm trying > to deploy a single EAR file, with a JAR file (containing the MDB) and > the RAR file (containing the adapter) contained within the EAR file. > I"ve got an application.xml and geronimo-application.xml file > contained within the EAR file, and an openejb-jar.xml file in the JAR > file (attached to this message). > > Now, it appears to deploy, in that the console doesn't report any > errors. But, I can't find the application in the list of installed > application EARs. If I look at the server.log, there's the exception > > org.apache.geronimo.common.DeploymentException: > com.intecbilling.svevents.geronimo/SVEventsDemo-Geronimo/1.0/ear does > not appear to be a the name of a module available on the selected > server. Perhaps it has already been stopped or undeployed? If you're > trying to specify a TargetModuleID, use the syntax > TargetName|ModuleName instead. If you're not sure what's running, try > the list-modules command. > > So, the SVEventsDemo-Geronimo is the name of the module, as defined in > the openejb-jar.xml file. > > So, how does an application get stopped immediately after it's > deployed? > > I have to ask it. Should I be using version 2 of Geronimo? Everytime > I try to run my adapter in Geronimo, it's an absolute trainwreck. > I've already gotten to the point, where I use another container to get > my adapter functionality working, and then just try to get the same > thing deployed in Geronimo. I appreciate the support that I have > gotten from this mailing list, but that's about the only positive I've > had from this process. I can get about an hour's worth of work done, > before I come across another Geronimo error for which there is no > existing documentation. Then, back to spamming the mailing list. So, > is 2.0.1 not ready for prime time yet? Should I be using an earlier > release? > > As far as my experience so far, Geronimo isn't meeting its first > guiding principle (Easy to use), certainly when in comparison to other > offerings. I'm just very frustrated from this exercise so far. > > > >