Scott,
I guess this is your answer.
Does exactly the same WAR deploy OK with Catalina - or experience the
same difficulty?
Jules
Greg Wilkins wrote:
>
> Jules,
>
> If I don't find a web.xml, I treat the webapp just as a docroot and
> will server files and JSPs OK.
>
> I think the problem is with JBoss's unpacking, because if Jetty does the
> unpacking, I take care of missing directories:
>
>
> /* ------------------------------------------------------------ */
> public static void extract(Resource resource, File directory,
> boolean deleteOnExit)
> throws IOException
> {
> Code.debug("Extract ",resource," to ",directory);
> JarInputStream jin = new JarInputStream(resource.getInputStream());
> JarEntry entry=null;
> while((entry=jin.getNextJarEntry())!=null)
> {
> File file=new File(directory,entry.getName());
> if (entry.isDirectory())
> {
> // Make directory
> if (!file.exists())
> file.mkdirs();
> }
> else
> {
> // make directory (some jars don't list dirs)
> File dir = new File(file.getParent());
> if (!dir.exists())
> dir.mkdirs();
>
> // Make file
> FileOutputStream fout = new FileOutputStream(file);
> IO.copy(jin,fout);
> fout.close();
> }
> if (deleteOnExit)
> file.deleteOnExit();
> }
> }
>
> cheers
>
>
>
> Jules Gosnell wrote:
>
>> Greg,
>>
>> Have you seen this thread ?
>>
>> If you fail to find the web.xml - is a deployment still valid ?
>>
>> Do you remember what the problem was here - I have seen similar
>> threads. They are always from people who have packaged something on
>> Windows and run on Linux, or vice-versa.
>>
>> It usually came down to file-system incompatibilities (case) (missing
>> directory defs) and the packaging tool used.
>>
>> Jules
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> [jboss-group] Problem with deployment of wars with Jetty in 3.0 and
>> 3.2 branches
>> From:
>> "Scott M Stark" <[EMAIL PROTECTED]>
>> Date:
>> Tue, 3 Sep 2002 13:33:54 -0400
>> To:
>> <[EMAIL PROTECTED]>
>>
>>
>> I am seeing a problem with Jetty not deploying wars from the deploy
>> directory in the current 3.0 and 3.2 branches. If you take the
>> default/deploy/jmx-console.war and repack this:
>>
>> deploy 414>ls -l jmx-console.war
>> -rw-r--r-- 1 starksm None 58165 Sep 3 13:17 jmx-console.war
>> deploy 415>jar -tf jmx-console.war
>> META-INF/
>> META-INF/MANIFEST.MF
>> WEB-INF/
>> WEB-INF/classes/
>> WEB-INF/classes/org/
>> WEB-INF/classes/org/jboss/
>> WEB-INF/classes/org/jboss/jmx/
>> WEB-INF/classes/org/jboss/jmx/adaptor/
>> WEB-INF/classes/org/jboss/jmx/adaptor/control/
>> WEB-INF/classes/org/jboss/jmx/adaptor/control/AttrResultInfo.class
>> WEB-INF/classes/org/jboss/jmx/adaptor/control/OpResultInfo.class
>> WEB-INF/classes/org/jboss/jmx/adaptor/control/Server.class
>> WEB-INF/classes/org/jboss/jmx/adaptor/html/
>> WEB-INF/classes/org/jboss/jmx/adaptor/html/HtmlAdaptorServlet.class
>> WEB-INF/classes/org/jboss/jmx/adaptor/model/
>> WEB-INF/classes/org/jboss/jmx/adaptor/model/DomainData.class
>> WEB-INF/classes/org/jboss/jmx/adaptor/model/MBeanData.class
>> WEB-INF/classes/roles.properties
>> WEB-INF/classes/users.properties
>> WEB-INF/web.xml
>> displayMBeans.jsp
>> displayOpResult.jsp
>> images/
>> images/head_blue.gif
>> index.jsp
>> inspectMBean.jsp
>> style_master.css
>>
>> Startup the default config and although Jetty says the war was deployed:
>>
>> 13:18:20,769 INFO [MainDeployer] Starting deployment of package:
>> file:/C:/usr/J
>> Boss3.2/jboss-all/build/output/jboss-3.2.0RC1/server/default/deploy/jmx-console.
>>
>> war
>> 13:18:21,340 INFO [jbossweb] Registered
>> jboss.web:Jetty=0,JBossWebApplicationCo
>> ntext=0,context=/jmx-console
>> 13:18:21,390 INFO [jbossweb] Checking Resource aliases
>> 13:18:21,490 INFO [jbossweb] Extract
>> jar:file:/C:/usr/JBoss3.2/jboss-all/build/
>> output/jboss-3.2.0RC1/server/default/tmp/deploy/server/default/deploy/jmx-consol
>>
>> e.war/61.jmx-console.war!/ to
>> C:\DOCUME~1\starksm\LOCALS~1\Temp\Jetty_0_0_0_0_80
>> 80__jmx-console\webapp
>> 13:18:22,312 INFO [jbossweb] Started
>> WebApplicationContext[/jmx-console,jar:fil
>> e:/C:/usr/JBoss3.2/jboss-all/build/output/jboss-3.2.0RC1/server/default/tmp/depl
>>
>> oy/server/default/deploy/jmx-console.war/61.jmx-console.war!/]
>> 13:18:22,392 INFO [jbossweb] successfully deployed
>> file:/C:/usr/JBoss3.2/jboss-
>> all/build/output/jboss-3.2.0RC1/server/default/tmp/deploy/server/default/deploy/
>>
>> jmx-console.war/61.jmx-console.war to /jmx-console
>> 13:18:22,392 INFO [MainDeployer] Deployed package:
>> file:/C:/usr/JBoss3.2/jboss-
>> all/build/output/jboss-3.2.0RC1/server/default/deploy/jmx-console.war
>> 13:18:22,402 INFO [URLDeploymentScanner] Started
>>
>> It is in fact not accessible:
>>
>> security 409>wget http://localhost:8080/jmx-console
>> --13:21:08-- http://localhost:8080/jmx-console
>> => `jmx-console'
>> Resolving localhost... done.
>> Connecting to localhost[127.0.0.1]:8080... connected.
>> HTTP request sent, awaiting response... 302 Moved Temporarily
>> Location: http://localhost:8080/jmx-console/ [following]
>> --13:21:08-- http://localhost:8080/jmx-console/
>> => `index.html'
>> Connecting to localhost[127.0.0.1]:8080... connected.
>> HTTP request sent, awaiting response... 404 /jmx-console/ Not Found
>> 13:21:08 ERROR 404: /jmx-console/ Not Found.
>>
>>
>> If the jmx-console.war is unpacked then the content is accessible:
>>
>> security 410>wget http://localhost:8080/jmx-console
>> --13:25:25-- http://localhost:8080/jmx-console
>> => `jmx-console'
>> Resolving localhost... done.
>> Connecting to localhost[127.0.0.1]:8080... connected.
>> HTTP request sent, awaiting response... 302 Moved Temporarily
>> Location: http://localhost:8080/jmx-console/ [following]
>> --13:25:25-- http://localhost:8080/jmx-console/
>> => `index.html'
>> Connecting to localhost[127.0.0.1]:8080... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: unspecified [text/html]
>>
>> [ <=> ] 46,675 735.18K/s
>>
>> 13:25:30 (735.18 KB/s) - `index.html' saved [46675]
>>
>> These messages are for the current 3.2 build. The 3.0 build actually
>> displays an
>> info message with a "Internal Error..." msg during deployment of the war:
>>
>> 12:57:23,161 INFO [MainDeployer] Starting deployment of package:
>> file:/C:/usr/S
>> akonnet/jboss-3.0.3RC1/server/default/deploy/jmx-console.war
>> 12:57:23,442 INFO [jbossweb] Registered
>> jboss.web:Jetty=0,JBossWebApplicationCo
>> ntext=1,context=/jmx-console
>> 12:57:23,472 INFO [jbossweb] Extract
>> jar:file:/C:/usr/Sakonnet/jboss-3.0.3RC1/s
>> erver/default/tmp/deploy/server/default/deploy/jmx-console.war/61.jmx-console.wa
>>
>> r!/ to
>> C:\DOCUME~1\starksm\LOCALS~1\Temp\Jetty_0_0_0_0_8080__jmx-console\webapp
>> 12:57:23,942 INFO [jbossweb] Started
>> WebApplicationContext[/jmx-console,jar:fil
>> e:/C:/usr/Sakonnet/jboss-3.0.3RC1/server/default/tmp/deploy/server/default/deplo
>>
>> y/jmx-console.war/61.jmx-console.war!/]
>> 12:57:23,942 INFO [jbossweb] Internal Error: File /WEB-INF/web.xml
>> not found
>> 12:57:23,942 INFO [jbossweb] successfully deployed
>> file:/C:/usr/Sakonnet/jboss-
>> 3.0.3RC1/server/default/tmp/deploy/server/default/deploy/jmx-console.war/61.jmx-
>>
>> console.war to /jmx-console
>> 12:57:23,942 INFO [MainDeployer] Deployed package:
>> file:/C:/usr/Sakonnet/jboss-
>> 3.0.3RC1/server/default/deploy/jmx-console.war
>>
>> but does claim that the war was deployed.
>>
>> xxxxxxxxxxxxxxxxxxxxxxxx
>> Scott Stark
>> Chief Technology Officer
>> JBoss Group, LLC
>> xxxxxxxxxxxxxxxxxxxxxxxx
>>
>> _______________________________________________
>> jboss-group mailing list
>> [EMAIL PROTECTED]
>> https://secure.jboss.org/mailman/listinfo/jboss-group
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
