Saturday, December 17, 2011

ATG - runAssembler Document root element is missing

Problem
    Are you getting an error "Document root element is missing" while building an EAR or deploying an application ? I got that when I was bundling ATG modules using runassembler :)

CAUGHT AT:CONTAINER:atg.appassembly.ApplicationAssemblerException
Document root element is missing

Solution
    Guess which XML its trying to read, mine was application.xml inside the META-INF folder. Open it in an editor delete the first character and retype it usually it be the less than sign (<). Save the file and try redoing what you did more chance that it would work :)

5 comments:

  1. Thanks.. This was very useful for me..
    In my case I got the following error...

    Location: line 23
    CAUGHT AT:CONTAINER:atg.appassembly.ApplicationAssemblerException; SOURCE:org.xml.sax.SAXParseException: unexpected root element application

    So I got to resolve it by modifying the XML file '/Storefront/j2ee-apps/Storefront/META-INF/application.xml'

    ReplyDelete
  2. Hi Bro,
    Im getting somewhat same issue. The error is pasted below.

    atg.appassembly.ApplicationAssemblerException: Could not open an input stream from D:\Dev\ATG\ATG11.1\store\j2ee-apps\store/METAError(s) occurred : Could not open an input stream from D:\Dev\ATG\ATG11.1\store\j2ee-apps\store/META-INF/application.xml

    ReplyDelete
  3. You saved my life !! Got the following error:

    CAUGHT AT:CONTAINER:atg.appassembly.ApplicationAssemblerException; SOURCE:org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed.
    at atg.appassembly.util.MetaInfGeneratorImpl.createUnmarshallerHandler(MetaInfGeneratorImpl.java:578)

    Just opened and edited the application.xml, wow! it works!! :-p

    ReplyDelete
  4. This comment has been removed by the author.

    ReplyDelete
  5. 30 years old post. still its usefull Naga.........:) ApplicationAssemblerException: Error: There is no installed ATG platform or application faced this issue and manifest.mf file of an dependant module was invalid.

    ReplyDelete