You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Neale Rudd <ne...@metawerx.net> on 2012/03/06 10:19:57 UTC
Missing web.xml file causes UnknownModuleTypeException
Hi Guys,
One of the apps we're trying on TomEE 1.0.0-beta-2 throws an UnknownModuleTypeException when deploying, because it has no WEB-INF/web.xml file.
It's a simple static website (html, css, images).
The docs I've read seem to indicate that web.xml is optional, and it's definitely optional on Tomcat 7.
Is this a difference with TomEE or a pending issue?
I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira but it's marked as Fixed for 1.0.0-beta-2.
Best Regards,
Neale Rudd
Metawerx Pty Ltd
http://www.metawerx.net
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
hmm,
try to compile the maven plugins before openejb:
https://svn.apache.org/repos/asf/openejb/trunk/maven-plugins/
i'm not sure everything is up to adte in nexus
- Romain
2012/3/15 Neale Rudd <ne...@metawerx.net>
> Hi Romain,
>
> I followed your instructions for the build, thanks for that.
>
> However - I get part way then it crashes here in the Core target building
> plexus:
>
> [INFO] ------------------------------**------------------------------**
> ------------
> [INFO] Building OpenEJB :: Container :: Core
> [INFO] task-segment: [clean, install]
> [INFO] ------------------------------**------------------------------**
> ------------
> ...
> ...
> [INFO] [spi-helper:generate {execution: generate-scan-xml}]
> [INFO] using profile jee6
> Downloading: http://repository.apache.org/**snapshots//org/apache/openejb/
> **spi-helper-jee6-profile/0.0.1-**SNAPSHOT/spi-helper-jee6-**
> profile-0.0.1-20120308.214320-**6<http://repository.apache.org/snapshots//org/apache/openejb/spi-helper-jee6-profile/0.0.1-SNAPSHOT/spi-helper-jee6-profile-0.0.1-20120308.214320-6>
> [WARNING] can't find spi-helper-jee6-profile
> [INFO] using a file archive
> [FATAL ERROR] org.apache.openejb.maven.**plugin.spi.SpiMojo#execute()
> caused a linkage error (java.lang.**NoClassDefFoundError) and may be
> out-of-date. Check the realms:
> [FATAL ERROR] Plugin realm = app0.child-container[org.**
> apache.openejb:spi-helper-**maven-plugin:0.0.1-SNAPSHOT]
> urls[0] = file:/home/.m2/repository/org/**apache/openejb/spi-helper-**
> maven-plugin/0.0.1-SNAPSHOT/**spi-helper-maven-plugin-0.0.1-**SNAPSHOT.jar
> urls[1] = file:/home/.m2/repository/org/**apache/openejb/spi-helper-**
> jee6-profile/0.0.1-SNAPSHOT/**spi-helper-jee6-profile-0.0.1-**SNAPSHOT.jar
> urls[2] = file:/home/.m2/repository/org/**codehaus/plexus/plexus-utils/**
> 1.5.15/plexus-utils-1.5.15.jar
> urls[3] = file:/home/.m2/repository/org/**apache/xbean/xbean-finder-**
> shaded/3.10-SNAPSHOT/xbean-**finder-shaded-3.10-SNAPSHOT.**jar
> urls[4] = file:/home/.m2/repository/org/**apache/xbean/xbean-asm-shaded/**
> 3.10-SNAPSHOT/xbean-asm-**shaded-3.10-SNAPSHOT.jar
> [FATAL ERROR] Container realm = plexus.core
> urls[0] = file:/usr/share/maven2/lib/**maven-debian-uber.jar
> [INFO] ------------------------------**------------------------------**
> ------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------**------------------------------**
> ------------
> [INFO] javax/interceptor/**InvocationContext
> javax.interceptor.**InvocationContext
> [INFO] ------------------------------**------------------------------**
> ------------
> [INFO] Trace
> java.lang.**NoClassDefFoundError: javax/interceptor/**InvocationContext
> at java.lang.Class.**getDeclaredMethods0(Native Method)
> at java.lang.Class.**privateGetDeclaredMethods(**Class.java:2444)
> at java.lang.Class.**getDeclaredMethods(Class.java:**1808)
> at org.apache.xbean.finder.**AnnotationFinder.**
> findAnnotatedMethods(**AnnotationFinder.java:584)
> at org.apache.openejb.maven.**plugin.spi.SpiMojo.execute(**
> SpiMojo.java:217)
> at org.apache.maven.plugin.**DefaultPluginManager.**executeMojo(**
> DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**
> executeGoals(**DefaultLifecycleExecutor.java:**694)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**
> executeGoalWithLifecycle(**DefaultLifecycleExecutor.java:**556)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**
> executeGoal(**DefaultLifecycleExecutor.java:**535)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**
> executeGoalAndHandleFailures(**DefaultLifecycleExecutor.java:**387)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**
> executeTaskSegments(**DefaultLifecycleExecutor.java:**348)
> at org.apache.maven.lifecycle.**DefaultLifecycleExecutor.**execute(*
> *DefaultLifecycleExecutor.java:**180)
> at org.apache.maven.DefaultMaven.**doExecute(DefaultMaven.java:**
> 328)
> at org.apache.maven.DefaultMaven.**execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.**main(MavenCli.java:362)
> at org.apache.maven.cli.compat.**CompatibleMain.main(**
> CompatibleMain.java:60)
> at sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native Method)
> at sun.reflect.**NativeMethodAccessorImpl.**invoke(**
> NativeMethodAccessorImpl.java:**57)
> at sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
> DelegatingMethodAccessorImpl.**java:43)
> at java.lang.reflect.Method.**invoke(Method.java:616)
> at org.codehaus.classworlds.**Launcher.launchEnhanced(**
> Launcher.java:315)
> at org.codehaus.classworlds.**Launcher.launch(Launcher.java:**255)
> at org.codehaus.classworlds.**Launcher.mainWithExitCode(**
> Launcher.java:430)
> at org.codehaus.classworlds.**Launcher.main(Launcher.java:**375)
> Caused by: java.lang.**ClassNotFoundException: javax.interceptor.**
> InvocationContext
> at java.net.URLClassLoader$1.run(**URLClassLoader.java:217)
> at java.security.**AccessController.doPrivileged(**Native Method)
> at java.net.URLClassLoader.**findClass(URLClassLoader.java:**205)
> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**321)
> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**266)
> ... 24 more
>
> Any idea?
>
>
> Best Regards,
> Neale
>
> ----- Original Message ----- From: "Romain Manni-Bucau" <
> rmannibucau@gmail.com>
> To: <us...@openejb.apache.org>
> Sent: Tuesday, March 06, 2012 10:20 PM
>
> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>
>
> yep, the Apache one:
>>
>> to simply build tomee:
>>
>> svn co http://svn.apache.org/repos/**asf/openejb/trunk/openejb/<http://svn.apache.org/repos/asf/openejb/trunk/openejb/>
>> cd openjeb
>> mvn clean install -Dmaven.test.skip=true -pl tomee/apache-tomee -am
>>
>> then go to openejb/tomee/apache-tomee/**target, you'll find the zip you
>> are
>> looking for.
>>
>> - Romain
>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Romain,
I followed your instructions for the build, thanks for that.
However - I get part way then it crashes here in the Core target building
plexus:
[INFO] ------------------------------------------------------------------------
[INFO] Building OpenEJB :: Container :: Core
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
...
...
[INFO] [spi-helper:generate {execution: generate-scan-xml}]
[INFO] using profile jee6
Downloading:
http://repository.apache.org/snapshots//org/apache/openejb/spi-helper-jee6-profile/0.0.1-SNAPSHOT/spi-helper-jee6-profile-0.0.1-20120308.214320-6
[WARNING] can't find spi-helper-jee6-profile
[INFO] using a file archive
[FATAL ERROR] org.apache.openejb.maven.plugin.spi.SpiMojo#execute() caused a
linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check
the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.openejb:spi-helper-maven-plugin:0.0.1-SNAPSHOT]
urls[0] =
file:/home/.m2/repository/org/apache/openejb/spi-helper-maven-plugin/0.0.1-SNAPSHOT/spi-helper-maven-plugin-0.0.1-SNAPSHOT.jar
urls[1] =
file:/home/.m2/repository/org/apache/openejb/spi-helper-jee6-profile/0.0.1-SNAPSHOT/spi-helper-jee6-profile-0.0.1-SNAPSHOT.jar
urls[2] =
file:/home/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
urls[3] =
file:/home/.m2/repository/org/apache/xbean/xbean-finder-shaded/3.10-SNAPSHOT/xbean-finder-shaded-3.10-SNAPSHOT.jar
urls[4] =
file:/home/.m2/repository/org/apache/xbean/xbean-asm-shaded/3.10-SNAPSHOT/xbean-asm-shaded-3.10-SNAPSHOT.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/usr/share/maven2/lib/maven-debian-uber.jar
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] javax/interceptor/InvocationContext
javax.interceptor.InvocationContext
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError: javax/interceptor/InvocationContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
at java.lang.Class.getDeclaredMethods(Class.java:1808)
at
org.apache.xbean.finder.AnnotationFinder.findAnnotatedMethods(AnnotationFinder.java:584)
at
org.apache.openejb.maven.plugin.spi.SpiMojo.execute(SpiMojo.java:217)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.ClassNotFoundException:
javax.interceptor.InvocationContext
at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 24 more
Any idea?
Best Regards,
Neale
----- Original Message -----
From: "Romain Manni-Bucau" <rm...@gmail.com>
To: <us...@openejb.apache.org>
Sent: Tuesday, March 06, 2012 10:20 PM
Subject: Re: Missing web.xml file causes UnknownModuleTypeException
> yep, the Apache one:
>
> to simply build tomee:
>
> svn co http://svn.apache.org/repos/asf/openejb/trunk/openejb/
> cd openjeb
> mvn clean install -Dmaven.test.skip=true -pl tomee/apache-tomee -am
>
> then go to openejb/tomee/apache-tomee/target, you'll find the zip you are
> looking for.
>
> - Romain
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
Saw it yesterday i think and fix it in a different way. It should work but
i think the snapshot is not up to date on the apache repo because we need
to upgrade the jdk because of a bug in the version our ci platform uses.
I added a test where i deploy a webapp with only an index.html so i guess
the fix should be enough.
- Romain
Le 14 avr. 2012 07:06, "Neale Rudd" <ne...@metawerx.net> a écrit :
> Hi Romain,
>
> On beta-3 snapshot, I'm still getting UnknownModuleExceptions on sites
> with no WEB-INF folder, so not sure if the patch below worked or isn't it
> in beta-3?
>
> If I create an WEB-INF folder the app deploys, as with beta-2 behaviour.
>
> Best Regards,
> Neale
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Romain,
On beta-3 snapshot, I'm still getting UnknownModuleExceptions on sites with
no WEB-INF folder, so not sure if the patch below worked or isn't it in
beta-3?
If I create an WEB-INF folder the app deploys, as with beta-2 behaviour.
Best Regards,
Neale
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
yep, the Apache one:
to simply build tomee:
svn co http://svn.apache.org/repos/asf/openejb/trunk/openejb/
cd openjeb
mvn clean install -Dmaven.test.skip=true -pl tomee/apache-tomee -am
then go to openejb/tomee/apache-tomee/target, you'll find the zip you are
looking for.
- Romain
2012/3/6 Neale Rudd <ne...@metawerx.net>
> Hi Romain,
>
> That's great - thanks for that :-)
>
> Is there a public readonly SVN repository for TomEE so I can test any
> newer changes?
>
>
> Best Regards,
> Neale
>
> ----- Original Message ----- From: "Romain Manni-Bucau" <
> rmannibucau@gmail.com>
> To: <us...@openejb.apache.org>
> Sent: Tuesday, March 06, 2012 9:25 PM
>
> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>
>
> just pushed a test to be able to fallback more easily to webapp.
>>
>> it will probably need some enhancement but it should work.
>>
>> - Romain
>>
>>
>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>
>> Maybe if it has no WEB-INF and no META-INF either, it can be considered
>>> the same way as an empty WEB-INF folder?
>>>
>>> That would cater for ear but allow Tomcat-7 simple no web-xml apps to
>>> work
>>> immediately.
>>>
>>> What do you think?
>>>
>>>
>>> Best Regards,
>>> Neale
>>>
>>>
>>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>>> rmannibucau@gmail.com>
>>> To: <us...@openejb.apache.org>
>>> Sent: Tuesday, March 06, 2012 8:57 PM
>>>
>>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>>
>>>
>>> The problem with this is that for Tomcat everything is a webapp so
>>> that's
>>>
>>>> easy to guess which module typ eit is.
>>>>
>>>> TomEE can manage jar, war and ear so we need something to distinguish
>>>> them.
>>>>
>>>> The WEB-INF folder is enough (and i think the spec don't say it is
>>>> optional).
>>>>
>>>> - Romain
>>>>
>>>>
>>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>>
>>>> Hi Romain,
>>>>
>>>>>
>>>>> Yes - an empty WEB-INF folder works fine, and also it's no problem
>>>>> adding
>>>>> a simple web.xml anyway.
>>>>>
>>>>> I'm more concerned with whether it will stay this way and if it's part
>>>>> of
>>>>> the spec or not, as I'm making a list of differences for our customers
>>>>> if
>>>>> they want to try TomEE. Naturally the closer it is to Tomcat's
>>>>> behaviour,
>>>>> the easier it is for them to start using it.
>>>>>
>>>>> Best Regards,
>>>>> Neale
>>>>>
>>>>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>>>>> rmannibucau@gmail.com>
>>>>> To: <us...@openejb.apache.org>
>>>>> Sent: Tuesday, March 06, 2012 8:23 PM
>>>>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>>>>
>>>>>
>>>>>
>>>>> Did you try putting an emtpy WEB-INF folder?
>>>>>
>>>>>
>>>>>> - Romain
>>>>>>
>>>>>>
>>>>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>>>>
>>>>>> Hi Guys,
>>>>>>
>>>>>>
>>>>>>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>>>>>>> UnknownModuleTypeException when deploying, because it has no
>>>>>>> WEB-INF/web.xml file.
>>>>>>>
>>>>>>> It's a simple static website (html, css, images).
>>>>>>>
>>>>>>> The docs I've read seem to indicate that web.xml is optional, and
>>>>>>> it's
>>>>>>> definitely optional on Tomcat 7.
>>>>>>>
>>>>>>> Is this a difference with TomEE or a pending issue?
>>>>>>>
>>>>>>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira
>>>>>>> but
>>>>>>> it's marked as Fixed for 1.0.0-beta-2.
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Neale Rudd
>>>>>>> Metawerx Pty Ltd
>>>>>>> http://www.metawerx.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Romain,
That's great - thanks for that :-)
Is there a public readonly SVN repository for TomEE so I can test any newer
changes?
Best Regards,
Neale
----- Original Message -----
From: "Romain Manni-Bucau" <rm...@gmail.com>
To: <us...@openejb.apache.org>
Sent: Tuesday, March 06, 2012 9:25 PM
Subject: Re: Missing web.xml file causes UnknownModuleTypeException
> just pushed a test to be able to fallback more easily to webapp.
>
> it will probably need some enhancement but it should work.
>
> - Romain
>
>
> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>
>> Maybe if it has no WEB-INF and no META-INF either, it can be considered
>> the same way as an empty WEB-INF folder?
>>
>> That would cater for ear but allow Tomcat-7 simple no web-xml apps to
>> work
>> immediately.
>>
>> What do you think?
>>
>>
>> Best Regards,
>> Neale
>>
>>
>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>> rmannibucau@gmail.com>
>> To: <us...@openejb.apache.org>
>> Sent: Tuesday, March 06, 2012 8:57 PM
>>
>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>
>>
>> The problem with this is that for Tomcat everything is a webapp so
>> that's
>>> easy to guess which module typ eit is.
>>>
>>> TomEE can manage jar, war and ear so we need something to distinguish
>>> them.
>>>
>>> The WEB-INF folder is enough (and i think the spec don't say it is
>>> optional).
>>>
>>> - Romain
>>>
>>>
>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>
>>> Hi Romain,
>>>>
>>>> Yes - an empty WEB-INF folder works fine, and also it's no problem
>>>> adding
>>>> a simple web.xml anyway.
>>>>
>>>> I'm more concerned with whether it will stay this way and if it's part
>>>> of
>>>> the spec or not, as I'm making a list of differences for our customers
>>>> if
>>>> they want to try TomEE. Naturally the closer it is to Tomcat's
>>>> behaviour,
>>>> the easier it is for them to start using it.
>>>>
>>>> Best Regards,
>>>> Neale
>>>>
>>>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>>>> rmannibucau@gmail.com>
>>>> To: <us...@openejb.apache.org>
>>>> Sent: Tuesday, March 06, 2012 8:23 PM
>>>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>>>
>>>>
>>>>
>>>> Did you try putting an emtpy WEB-INF folder?
>>>>
>>>>>
>>>>> - Romain
>>>>>
>>>>>
>>>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>>>
>>>>> Hi Guys,
>>>>>
>>>>>>
>>>>>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>>>>>> UnknownModuleTypeException when deploying, because it has no
>>>>>> WEB-INF/web.xml file.
>>>>>>
>>>>>> It's a simple static website (html, css, images).
>>>>>>
>>>>>> The docs I've read seem to indicate that web.xml is optional, and
>>>>>> it's
>>>>>> definitely optional on Tomcat 7.
>>>>>>
>>>>>> Is this a difference with TomEE or a pending issue?
>>>>>>
>>>>>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira
>>>>>> but
>>>>>> it's marked as Fixed for 1.0.0-beta-2.
>>>>>>
>>>>>> Best Regards,
>>>>>> Neale Rudd
>>>>>> Metawerx Pty Ltd
>>>>>> http://www.metawerx.net
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
just pushed a test to be able to fallback more easily to webapp.
it will probably need some enhancement but it should work.
- Romain
2012/3/6 Neale Rudd <ne...@metawerx.net>
> Maybe if it has no WEB-INF and no META-INF either, it can be considered
> the same way as an empty WEB-INF folder?
>
> That would cater for ear but allow Tomcat-7 simple no web-xml apps to work
> immediately.
>
> What do you think?
>
>
> Best Regards,
> Neale
>
>
> ----- Original Message ----- From: "Romain Manni-Bucau" <
> rmannibucau@gmail.com>
> To: <us...@openejb.apache.org>
> Sent: Tuesday, March 06, 2012 8:57 PM
>
> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>
>
> The problem with this is that for Tomcat everything is a webapp so that's
>> easy to guess which module typ eit is.
>>
>> TomEE can manage jar, war and ear so we need something to distinguish
>> them.
>>
>> The WEB-INF folder is enough (and i think the spec don't say it is
>> optional).
>>
>> - Romain
>>
>>
>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>
>> Hi Romain,
>>>
>>> Yes - an empty WEB-INF folder works fine, and also it's no problem adding
>>> a simple web.xml anyway.
>>>
>>> I'm more concerned with whether it will stay this way and if it's part of
>>> the spec or not, as I'm making a list of differences for our customers if
>>> they want to try TomEE. Naturally the closer it is to Tomcat's
>>> behaviour,
>>> the easier it is for them to start using it.
>>>
>>> Best Regards,
>>> Neale
>>>
>>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>>> rmannibucau@gmail.com>
>>> To: <us...@openejb.apache.org>
>>> Sent: Tuesday, March 06, 2012 8:23 PM
>>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>>
>>>
>>>
>>> Did you try putting an emtpy WEB-INF folder?
>>>
>>>>
>>>> - Romain
>>>>
>>>>
>>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>>
>>>> Hi Guys,
>>>>
>>>>>
>>>>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>>>>> UnknownModuleTypeException when deploying, because it has no
>>>>> WEB-INF/web.xml file.
>>>>>
>>>>> It's a simple static website (html, css, images).
>>>>>
>>>>> The docs I've read seem to indicate that web.xml is optional, and it's
>>>>> definitely optional on Tomcat 7.
>>>>>
>>>>> Is this a difference with TomEE or a pending issue?
>>>>>
>>>>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira
>>>>> but
>>>>> it's marked as Fixed for 1.0.0-beta-2.
>>>>>
>>>>> Best Regards,
>>>>> Neale Rudd
>>>>> Metawerx Pty Ltd
>>>>> http://www.metawerx.net
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Neale Rudd <ne...@metawerx.net>.
Maybe if it has no WEB-INF and no META-INF either, it can be considered the
same way as an empty WEB-INF folder?
That would cater for ear but allow Tomcat-7 simple no web-xml apps to work
immediately.
What do you think?
Best Regards,
Neale
----- Original Message -----
From: "Romain Manni-Bucau" <rm...@gmail.com>
To: <us...@openejb.apache.org>
Sent: Tuesday, March 06, 2012 8:57 PM
Subject: Re: Missing web.xml file causes UnknownModuleTypeException
> The problem with this is that for Tomcat everything is a webapp so that's
> easy to guess which module typ eit is.
>
> TomEE can manage jar, war and ear so we need something to distinguish
> them.
>
> The WEB-INF folder is enough (and i think the spec don't say it is
> optional).
>
> - Romain
>
>
> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>
>> Hi Romain,
>>
>> Yes - an empty WEB-INF folder works fine, and also it's no problem adding
>> a simple web.xml anyway.
>>
>> I'm more concerned with whether it will stay this way and if it's part of
>> the spec or not, as I'm making a list of differences for our customers if
>> they want to try TomEE. Naturally the closer it is to Tomcat's
>> behaviour,
>> the easier it is for them to start using it.
>>
>> Best Regards,
>> Neale
>>
>> ----- Original Message ----- From: "Romain Manni-Bucau" <
>> rmannibucau@gmail.com>
>> To: <us...@openejb.apache.org>
>> Sent: Tuesday, March 06, 2012 8:23 PM
>> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>>
>>
>>
>> Did you try putting an emtpy WEB-INF folder?
>>>
>>> - Romain
>>>
>>>
>>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>>
>>> Hi Guys,
>>>>
>>>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>>>> UnknownModuleTypeException when deploying, because it has no
>>>> WEB-INF/web.xml file.
>>>>
>>>> It's a simple static website (html, css, images).
>>>>
>>>> The docs I've read seem to indicate that web.xml is optional, and it's
>>>> definitely optional on Tomcat 7.
>>>>
>>>> Is this a difference with TomEE or a pending issue?
>>>>
>>>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira
>>>> but
>>>> it's marked as Fixed for 1.0.0-beta-2.
>>>>
>>>> Best Regards,
>>>> Neale Rudd
>>>> Metawerx Pty Ltd
>>>> http://www.metawerx.net
>>>>
>>>>
>>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
The problem with this is that for Tomcat everything is a webapp so that's
easy to guess which module typ eit is.
TomEE can manage jar, war and ear so we need something to distinguish them.
The WEB-INF folder is enough (and i think the spec don't say it is
optional).
- Romain
2012/3/6 Neale Rudd <ne...@metawerx.net>
> Hi Romain,
>
> Yes - an empty WEB-INF folder works fine, and also it's no problem adding
> a simple web.xml anyway.
>
> I'm more concerned with whether it will stay this way and if it's part of
> the spec or not, as I'm making a list of differences for our customers if
> they want to try TomEE. Naturally the closer it is to Tomcat's behaviour,
> the easier it is for them to start using it.
>
> Best Regards,
> Neale
>
> ----- Original Message ----- From: "Romain Manni-Bucau" <
> rmannibucau@gmail.com>
> To: <us...@openejb.apache.org>
> Sent: Tuesday, March 06, 2012 8:23 PM
> Subject: Re: Missing web.xml file causes UnknownModuleTypeException
>
>
>
> Did you try putting an emtpy WEB-INF folder?
>>
>> - Romain
>>
>>
>> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>>
>> Hi Guys,
>>>
>>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>>> UnknownModuleTypeException when deploying, because it has no
>>> WEB-INF/web.xml file.
>>>
>>> It's a simple static website (html, css, images).
>>>
>>> The docs I've read seem to indicate that web.xml is optional, and it's
>>> definitely optional on Tomcat 7.
>>>
>>> Is this a difference with TomEE or a pending issue?
>>>
>>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira but
>>> it's marked as Fixed for 1.0.0-beta-2.
>>>
>>> Best Regards,
>>> Neale Rudd
>>> Metawerx Pty Ltd
>>> http://www.metawerx.net
>>>
>>>
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Romain,
Yes - an empty WEB-INF folder works fine, and also it's no problem adding a
simple web.xml anyway.
I'm more concerned with whether it will stay this way and if it's part of
the spec or not, as I'm making a list of differences for our customers if
they want to try TomEE. Naturally the closer it is to Tomcat's behaviour,
the easier it is for them to start using it.
Best Regards,
Neale
----- Original Message -----
From: "Romain Manni-Bucau" <rm...@gmail.com>
To: <us...@openejb.apache.org>
Sent: Tuesday, March 06, 2012 8:23 PM
Subject: Re: Missing web.xml file causes UnknownModuleTypeException
> Did you try putting an emtpy WEB-INF folder?
>
> - Romain
>
>
> 2012/3/6 Neale Rudd <ne...@metawerx.net>
>
>> Hi Guys,
>>
>> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
>> UnknownModuleTypeException when deploying, because it has no
>> WEB-INF/web.xml file.
>>
>> It's a simple static website (html, css, images).
>>
>> The docs I've read seem to indicate that web.xml is optional, and it's
>> definitely optional on Tomcat 7.
>>
>> Is this a difference with TomEE or a pending issue?
>>
>> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira but
>> it's marked as Fixed for 1.0.0-beta-2.
>>
>> Best Regards,
>> Neale Rudd
>> Metawerx Pty Ltd
>> http://www.metawerx.net
>>
>
Re: Missing web.xml file causes UnknownModuleTypeException
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Did you try putting an emtpy WEB-INF folder?
- Romain
2012/3/6 Neale Rudd <ne...@metawerx.net>
> Hi Guys,
>
> One of the apps we're trying on TomEE 1.0.0-beta-2 throws an
> UnknownModuleTypeException when deploying, because it has no
> WEB-INF/web.xml file.
>
> It's a simple static website (html, css, images).
>
> The docs I've read seem to indicate that web.xml is optional, and it's
> definitely optional on Tomcat 7.
>
> Is this a difference with TomEE or a pending issue?
>
> I found another mail on the list from 9-Oct-2011 and TOMEE-27 on Jira but
> it's marked as Fixed for 1.0.0-beta-2.
>
> Best Regards,
> Neale Rudd
> Metawerx Pty Ltd
> http://www.metawerx.net
>