Message:

   The following issue has been reopened.

   Reopener: Dain Sundstrom
       Date: Wed, 8 Sep 2004 12:23 PM

Reopen so I can edit the fixed in attribute
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-256

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-256
    Summary: org.apache.xmlbeans.XmlException: error: Document root element is 
missing.
       Type: Improvement

     Status: Reopened
   Priority: Major

    Project: Apache Geronimo
 Components: 
             deployment
   Fix Fors:
             1.0-M2
   Versions:
             1.0-M1

   Assignee: 
   Reporter: Shrek the Ogre

    Created: Sun, 27 Jun 2004 11:39 PM
    Updated: Wed, 8 Sep 2004 12:23 PM
Environment: Microsoft Windows XP [Wersja 5.1.2600]

CYGWIN_NT-5.1 Shrek 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown 
Cygwin

java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

Description:
Hi,

It's being attempted to deploy blojsom.war onto Geronimo (built from tonight's 
update). However, since almost 1 week either Geronimo changed or I made a 
mistake in the configuration. Although, I'm facing troubles with deployment the 
report pertains to the error message that's printed out. It say nothing about 
the broken file (I guess it's a file) and would need some improvements. See the 
attached files - geronimo-jetty.xml (it's taken by Geronimo as once deleted 
Geronimo reported the file was missing) and the stack trace.

The command line that's used is:

java -jar bin/deployer.jar --install --module D:/projekty/blojsom.war

CVS update command reported no changes in my local repository.

Cheers,
Yours Shrek


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to