struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parmar, Dipakkumar" <dpar...@cgmpsystems.com>
Subject RE: Latest Nightly build - corrupt Class-Path entry in manifest.m f
Date Fri, 19 Jul 2002 18:48:46 GMT
Hi Guys,

I could not able to run nightly build in WebLogic 6.1sp2 this is because of
manifest.mf file problem.  So i modified manifest.mf file (splitting the
class-path entry over two class-path entries) and now I'm getting
org/apache/struts/taglib/bean/MessageTag NoClassDeffoundError.

Here are the steps i followed to update manifest.mf file in struts.jar.

1. make a new directory TEMP
2. copy latest struts. jar into TEMP.
3. unjar it. jar -xf struts.jar
4. Copy manifest.mf into META-INF directory.
5. remove struts.jar from TEMP directory.
6. create new struts.jar.   jar -cfM struts.jar .

Am I missing something here?

Thanks
Deepak

-----Original Message-----
From: Jon.Ridgway [mailto:Jon.Ridgway@upco.co.uk]
Sent: Thursday, July 18, 2002 6:50 AM
To: 'Struts Users Mailing List'
Subject: RE: Latest Nightly build - corrupt Class-Path entry in
manifest.m f


Hi Graig,

As requested I have tried splitting the Class-Path entry over two Class-Path
entries in manifest.mf. This works fine in WebLogic 6.1sp2, I'll try on
JBoos 3.0, OC4J 9 & WebSphere 4.0.3 and let you know...

Jon Ridgway


-----Original Message-----
From: Craig R. McClanahan [mailto:craigmcc@apache.org]
Sent: 17 July 2002 16:18
To: Struts Users Mailing List
Subject: RE: Latest Nightly build - corrupt Class-Path entry in manifest.m f



On Wed, 17 Jul 2002, Jesse Alexander (KADA 11) wrote:

> Date: Wed, 17 Jul 2002 10:34:04 +0200
> From: "Jesse Alexander (KADA 11)" <alexander.jesse@csfs.com>
> Reply-To: Struts Users Mailing List <struts-user@jakarta.apache.org>
> To: 'Struts Users Mailing List' <struts-user@jakarta.apache.org>
> Subject: RE: Latest Nightly build - corrupt Class-Path entry in
>     manifest.m f
>
> Hi,
>
> I think somebody with deeper knowledge about the internals must look into
it.
> Either the problem is, that the documentation is out-of-date (maybe today
it
> is not necessary to split the class-path-entry anymore), or it is a
problem
> of the class-loaders used in the servlet-engines (WLS accepts
Class-path-entries
> that are up to 120+ characters line-length).
> Maybe somebody working on Tomcat (or at least knowing its code-base a bit)
> can enlighten us more on this...
> Meaning it might make sense to push BEA to check their class-loader and
> encourage somebody to take a look at the spec's and class-loaders on the
> Apache-side ==> open a problem at BEA and open a bug-report in BugZilla
>

This would be an issue with WebLogic's JVM implementation, and nothing to
do with Tomcat.

I can't see anything in the JDK docs about the "split at 68 characters"
thing someone mentioned.  Does someone have a pointer to that in the docs?
The Struts build process has this all on one line in the source, so it
seems to be Ant doing the modification ...

I do see that you can have more than one "Class-Path" element
<http://java.sun.com/j2se/1.4/docs/guide/extensions/spec.html>.  Could
someone try that and see if it works?

> regards
> Alexander

Craig


>
> -----Original Message-----
> From: Jon.Ridgway [mailto:Jon.Ridgway@upco.co.uk]
> Sent: Dienstag, 16. Juli 2002 16:17
> To: 'Struts Users Mailing List'
> Subject: RE: Latest Nightly build - corrupt Class-Path entry in
> manifest.m f
>
>
> Hi James,
>
> I may have jumped the gun here; someone else has pointed out that the
> Class-Path entry should break to a new line after 68 chars. It's just that
> WebLogic 6.1 (not sure about 7) can't handle this.
>
> So I guess I should eat some humble pie and WebLogic should sort things
out
> at their end...
>
> Jon Ridgway
>
>
> -----Original Message-----
> From: James Holmes [mailto:jholmes612@yahoo.com]
> Sent: 16 July 2002 15:09
> To: Struts Users Mailing List
> Subject: RE: Latest Nightly build - corrupt Class-Path entry in manifest.m
f
>
> This probably started happening as of nightly build
> 20020616 since that is when the Class-Path: entry got
> added to the MANIFEST.MF file in CVS.
>
> If you open a bug for this in Bugzilla I'll get it
> taken care of tonight.  Make sure to include all the
> info from this thread.
>
> http://nagoya.apache.org/bugzilla
>
> -james
> james@jamesholmes.com
> http://www.jamesholmes.com/struts/
>
>
> --- "Jesse Alexander (KADA 11)"
> <alexander.jesse@csfs.com> wrote:
> > Good and thanks for searching it,
> >
> > the problem with the manifest.mf and the class-path
> > is, that according to the
> > official docs the class-path-manifest-entry MUST be
> > split at the 68th character
> > and that theoretically it should be reassembled on
> > the fly.
> >
> > Relaity shows that some servlet-engines (or is the
> > JVM's or the class-loaders; I don't know)
> > do not make it correctly. And at least WLS (or its
> > class-loaders or the underlaying JVM's)
> > is among the problematic issues.
> >
> > Alexander Jesse
> >
> > -----Original Message-----
> > From: Jon.Ridgway [mailto:Jon.Ridgway@upco.co.uk]
> > Sent: Dienstag, 16. Juli 2002 13:17
> > To: 'Struts Users Mailing List'
> > Subject: RE: Latest Nightly build - corrupt
> > Class-Path entry in
> > manifest.m f
> >
> >
> > Hi All,
> >
> > The advice was spot on. The manifest.mf in the
> > latest nightly builds is
> > corrupt. The Class-Path entry is split over several
> > lines, the break occurs
> > half way through several referenced jar names.
> >
> > Jon Ridgway
> >
> >
> > -----Original Message-----
> > From: Jon.Ridgway [mailto:Jon.Ridgway@upco.co.uk]
> > Sent: 16 July 2002 12:08
> > To: 'Struts Users Mailing List'
> > Subject: RE: Latest Nightly build
> >
> > Hi Jesse,
> >
> > I'll give that ago and let you know what the problem
> > is if I can track it
> > down, thanks for the advice...
> >
> > Jon Ridgway
> >
> >
> > -----Original Message-----
> > From: Jesse Alexander (KADA 11)
> > [mailto:alexander.jesse@csfs.com]
> > Sent: 16 July 2002 11:52
> > To: 'Struts Users Mailing List'
> > Subject: RE: Latest Nightly build
> >
> > Hi,
> >
> > try to remove the manifest-file from the struts.jar.
> > WLS is very precise...
> >
> > If you have lots of time, then you could try to
> > remove
> > line by line from the manifest-file if step one
> > yields
> > a workable jar-file, until you find the true
> > culprit...
> >
> > hope this helps
> > Alexander
> >
> > -----Original Message-----
> > From: Jon.Ridgway [mailto:Jon.Ridgway@upco.co.uk]
> > Sent: Dienstag, 16. Juli 2002 12:40
> > To: 'struts-user@jakarta.apache.org'
> > Subject: Latest Nightly build
> >
> >
> > Hi All,
> >
> > Further to my previous post I have just enabled all
> > debugging/logging in
> > Struts/WebLogic and download the very latest build.
> > I'm still getting an
> > exception when attempting to deploy a web app that
> > works fine with the 1.1b1
> > release. The exception is :
> >
> > <16-Jul-02 11:33:25 BST> <Debug> <HTTP> <Exception
> > thrown while loading spf:
> > java.lang.StringIndexOutOfBoundsException: String
> > index out of range: -1
> > java.lang.StringIndexOutOfBoundsException: String
> > index out of range: -1
> >       at
> > java.lang.String.substring(String.java:1525)
> >       at
> >
> weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
> >       at
> >
> weblogic.utils.jars.Manifest.stream(Manifest.java:78)
> >       at
> >
>
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java
> > :398)
> >
> > etc..
> >
> > This is caused by something in struts.jar. If I
> > replace the jar with the
> > 1.1b1 jar the app deploys. Any ideas, suggestions
> > much appreciated.
> >
> > Jon Ridgway
> >
> >
> >
> > The contents of this email are intended only for the
> > named addressees and
> > may contain confidential and/or privileged material.
> > If received in error
> > please contact UPCO on +44 (0) 113 201 0600 and then
> > delete the entire
> > e-mail from your system. Unauthorised review,
> > distribution, disclosure or
> > other use of this information could constitute a
> > breach of confidence. Your
> > co-operation in this matter is greatly appreciated.
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:struts-user-help@jakarta.apache.org>
> >
> >
> > The contents of this email are intended only for the
> > named addressees and
> > may contain confidential and/or privileged material.
> > If received in error
> > please contact UPCO on +44 (0) 113 201 0600 and then
> > delete the entire
> > e-mail from your system. Unauthorised review,
> > distribution, disclosure or
> > other use of this information could constitute a
> > breach of confidence. Your
> > co-operation in this matter is greatly appreciated.
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:struts-user-help@jakarta.apache.org>
> >
> >
> > The contents of this email are intended only for the
> > named addressees and
> > may contain confidential and/or privileged material.
> > If received in error
> > please contact UPCO on +44 (0) 113 201 0600 and then
> > delete the entire
> > e-mail from your system. Unauthorised review,
> > distribution, disclosure or
> > other use of this information could constitute a
> > breach of confidence. Your
> > co-operation in this matter is greatly appreciated.
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:struts-user-help@jakarta.apache.org>
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:struts-user-help@jakarta.apache.org>
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes
> http://autos.yahoo.com
>
> --
> To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
>
>
> The contents of this email are intended only for the named addressees and
> may contain confidential and/or privileged material. If received in error
> please contact UPCO on +44 (0) 113 201 0600 and then delete the entire
> e-mail from your system. Unauthorised review, distribution, disclosure or
> other use of this information could constitute a breach of confidence.
Your
> co-operation in this matter is greatly appreciated.
>
> --
> To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>


The contents of this email are intended only for the named addressees and
may contain confidential and/or privileged material. If received in error
please contact UPCO on +44 (0) 113 201 0600 and then delete the entire
e-mail from your system. Unauthorised review, distribution, disclosure or
other use of this information could constitute a breach of confidence. Your
co-operation in this matter is greatly appreciated.

--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message