When a module in application.xml can't be deployed, what's the expected action? I can see two possibilities:
- the ear isn't deployed - the module isn't deployed, but the ear is. A specification for j2ee deployment exist? Where can I find/read it? Thanks, Eduardo. On Fri, 02 Jul 2004 08:44:39 -0700, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > > Eduardo Piva wrote: > > > Hi Jeremy, > > > > I've found the error. I don't know where this .ear is used in the test > > tree, but it's broken. In the application.xml, there is a connectior > > module, but there isn't a connector rar file in the .ear. The .war > > file inside this .ear is also broken, it has some missing references > > in the web.xml, and has a file called geronimo-web.xml inside the > > WEB-INF, but the JettyModuleBuilder was expecting a file called > > geronimo-jetty.xml. I had to rename that. > > > > All those errors generated NPE. > > > > I'll list all of then, and try to fix those I'm able. I think that the > > correct error would be some DeploymentException, with some useful > > message inside it. I think NPE confuse users. A message like "Could > > not find file test-connector.ear, deploying connector module" is much > > more usefull... :) > > > > After making some organized list of NPE I could get deploying bogus > > .ear, I'll send it to the JITA and also to the list. > > > > Thanks - that's really appreciated. > > -- > Jeremy > > -- Eduardo Fernandes Piva [EMAIL PROTECTED]
