let me jump in here quickly... I've sent quite a few "bug" reports to bugs@,
as well as to support@. As far as I remember (I do remeber quite well) I
never received an answer, which makes one wonder where those channels really
lead...
-----Original Message-----
From: Karl Avedal <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Donnerstag, 24. August 2000 02:30
Subject: Re: load-on-startup moving around and breaking things
>Hello Duane,
>
>Please send suspected bugs to [EMAIL PROTECTED], it's much safer than
hoping
>that someone will pick it up and forward it. I'll forward this one.
>Orion-interest is for public community discussions, so all of us don't read
>every mail sent to the list.
>
>Regards,
>Karl Avedal
>
>Duane Fields wrote:
>
>> Ok, in my expanded war's web.xml I have...
>>
>> <servlet>
>> <servlet-name>mcInit</servlet-name>
>> <display-name>mcInit</display-name>
>> <servlet-class>uo.mc.MissionControlInitServlet</servlet-class>
>> <init-param>
>> <param-name>verifyApplication</param-name>
>> <param-value>true</param-value>
>> </init-param>
>> <load-on-startup>1</load-on-startup>
>> </servlet>
>>
>> which works great, as expected. However, when I startup orion, it changes
it
>> to
>>
>> <servlet>
>> <servlet-name>mcInit</servlet-name>
>> <display-name>mcInit</display-name>
>> <servlet-class>uo.mc.MissionControlInitServlet</servlet-class>
>> <load-on-startup>1</load-on-startup>
>> <init-param>
>> <param-name>verifyApplication</param-name>
>> <param-value>true</param-value>
>> </init-param>
>> </servlet>
>>
>> It moves the load-on-startup around.... then when I try to start orion
the
>> next time, with validatexml on, I get
>>
>> Auto-deploying /usr/local/orion/default-web-app...
>> Error initializing site Default Orion WebSite: Error loading web-app
>> 'mc-public' at /home/dfields/dev/splashdown/src/mc/mc-public: Error
parsing
>> WEB-INF/web.xml in /home/dfields/dev/splashdown/src/mc/mc-public: Error
at
>> line 12: Element "servlet" does not allow "init-param" here.
>>
>> Which seems to indicate that the load-on-startup must be first, which of
>> course isn't true....
>>
>> --
>> Duane Fields
>> [EMAIL PROTECTED]
>> Managing Engineer, Web Development
>> (512) 744-1012
>
>
