Eduardo Piva | 2 Jul 2004 17:39
Picon

Re: Deploying .ear

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.

Maybe tomorrow I'll have this list, right now I have to work a
little... (Geronimo is a hobby right now. :D)

[]s

Eduardo

On Thu, 01 Jul 2004 11:27:37 -0700, Jeremy Boynes <jboynes@...> wrote:
> 
(Continue reading)

Jeremy Boynes | 2 Jul 2004 17:44

Re: Deploying .ear

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

(Continue reading)

Eduardo Piva | 2 Jul 2004 19:32
Picon

Re: Deploying .ear

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
<jeremy@...> 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
(Continue reading)

Jeremy Boynes | 2 Jul 2004 20:19

Re: Deploying .ear

Eduardo Piva wrote:

> 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.
> 

The ear itself should not be deployed.

> A specification for j2ee deployment exist? Where can I find/read it?
> 

JSR-88 http://jcp.org/en/jsr/detail?id=88

Our provider implementation is in o.a.g.deployment.plugin.factories

--
Jeremy


Gmane