facebook

name of the war-container resetted

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #255366 Reply

    SER
    Member

    This message has not been recovered.

    #255421 Reply

    Riyad Kalla
    Member

    This message has not been recovered.

    #255546 Reply

    SER
    Member

    OK. You’re right. The deployments are completely correct. The only astonishing what I had a look for, was that the setting of the archive-attribute within the configuration-file .mymetadata is set to somewhat else (“TestWeb.war” instead of “TestWebTwo.war”).
    While having a look on that file, I hoped, to configure my deployment-types (exploded or packaged) individually.

    Here is what the file looks for after your project configuration:

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <project-module
    type=”WEB”
    name=”TestWeb”
    id=”myeclipse.1153896286674″
    context-root=”/TestWebTwo
    j2ee-spec=”1.4″
    archive=”TestWeb.war”>
    <attributes>
    <attribute name=”webrootdir” value=”/WebRoot” />
    </attributes>
    </project-module>

    So, shouldn’t the highlighted words be the same?

    Thanks.

    #255568 Reply

    Riyad Kalla
    Member

    Technically yes, but the weird part is that we don’t use the “archive” property for anything right now. There is a filed enhancement to expose this to the user and allow them to specify what the name of the resulting archive of the file is *without* guessing it for them based on the context. This will also help with customizing EAR deployments, we just haven’t done it yet.

    So everything is working as is, even though the unmatching archive value seems strange.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: name of the war-container resetted

You must be logged in to post in the forum log in