What happens if you rip the manifest file out of the jar?
On Mar 11, 4:19 pm, Chris Watkins <[email protected]> wrote:
> Hi All,
>
> Many moons ago, I decided to leverage some in-house Java expertise and
> deploy some servlets and JSPs under CF. In hindsight, this was a bad
> decision for many reasons, but that is another story.
>
> The upshot is this: I'm maintaining some of the codebase, and am seeing some
> very perplexing behavior.
>
> The original Java files were deployed as a JAR in the WEB-INF/lib directory.
> Opening the JAR up, however, shows that there is no manifest and it's only
> the class files bundled together into an archive with a JAR extension. I am
> under the impression that JAR files are supposed to have manifests.
>
> I can make changes to the code in Eclipse and export as a JAR. However, it
> does include a manifest; however, while the CF service starts, I get the
> following error:
>
> Either the Macromedia application server is unreachable or it does not have
> a mapping to process this request.
>
> If I just grab the classes and drop them into the WEB-INF/classes directory,
> everything works.
>
> So, here are my questions:
>
> What exactly is this existing JAR file that works with no manifest file?
> Why doesn't a regular JAR file made by Eclipse cause CF to crash, but the
> unarchived classes work fine?
>
> I'm hoping this is a n00b question that we can all laugh about.
>
> Thanks!
> Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Houston ColdFusion
Users' Group" discussion list.
To unsubscribe, send email to [email protected]
For more options, visit http://groups.google.com/group/houcfug?hl=en
-~----------~----~----~----~------~----~------~--~---
