You know, after a lot of fighting on getting a war file to work with
WebLogic 10.3 I finally was a able to make it work. I did have to create the
weblogic.xml on the WEB-INF directory:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application
8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd";>
<weblogic-web-app>
  <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
  </container-descriptor>
</weblogic-web-app>

But it still is incredibly annoying that I have to send the war file with
all libraries to make it to work.

Regards,

Néstor Boscán

On Wed, Oct 7, 2009 at 11:34 AM, Jim Collings <[email protected]> wrote:

> Not so much.  Take Weblogic for example. You really can't deploy a
> Struts2 based WAR file to it because of library conflicts. It would be
> cool if I could specify somehow, somewhere that this is a Weblogic
> project.  Then it would always build as an ear and would include a
> weblogic-application.xml with the excludes/prefers set so that the
> conflicts don't happen. Also Weblogic insists on APP-INF rather than
> WEB-INF. Perhaps that is related to the fact that it is now an *.ear
> file though, I don't know.
>
> On Wed, Oct 7, 2009 at 3:59 AM, Brett Randall <[email protected]> wrote:
> > On Wed, Oct 7, 2009 at 11:21 AM, Jim C. <[email protected]> wrote:
> >
> >> Are there archetypes or something else out there that will differentiate
> >> between application servers?  We try to write cross platform Java and it
> >> seems like our app server vendors are fighting us tooth and nail. I
> >> suppose that is the reason for GlassFish but our shop isn't allowed to
> >> use it.
> >>
> >>
> >> Jim C.
> >>
> >>
> > What types of issue/differences are you facing? Are they compile/deploy
> or
> > runtime issues?
> >
> > Brett
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to