It is solved now, but what happend?
o I used UPSDK41 from OW and the remote PC as well.
o Today a colleague installed the new Version 5 WML SDK of OW
This didn't work eiter, as well as a different Browser also did not work
o Then I installed the new Version 5 SDK and *it didn't work*
That was really strange.
Than I looked into the directory psml/anon/wml and compared the file default.psml with
that in the directory psml/anaon/wml/en and gotcha: there where different and could
not render properly. That means: my UP41 on the local machine got returned the
psml/anon/wml/default.psml, where as the remote and the new UP5 got returned the
psml/anon/wml/EN/default.psml.
After making both of them right I could also access remotely to the WML stuff. Now I
know what it did: per default jetspeed is configured english, my UP41 is configured
german. The colleagues browser are also configured englisch. What does it all?
Obviously the languages properties work!
Thanks for your help
Juergen
> -----Urspr> �ngliche Nachricht-----
> Von: David Sean Taylor [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Mittwoch, 26. September 2001 21:13
> An: [EMAIL PROTECTED]
> Betreff: Re: lokally OK, remotely NOT OK
>
> Which browser are you using (remotely)?
>
> ----- Original Message -----
> From: "Riedl Juergen" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 26, 2001 2:48 AM
> Subject: WML: lokally OK, remotely NOT OK
>
>
> Hi,
>
> using jetspeed 1.3a2/tomcat 3.2.3 I started to enable WML output. Accessing
> jetspeed anonymously with the OpenWave WML simulator lokally works so far,
> however, when I access it from remote, an error will be reported:
>
> ----------------- DATA SIZE ------------------------
> Uncompiled data from HTTP is 225 bytes.
> ...found Content-Type: text/vnd.wap.wml.
>
> ======================= WML Errors =====================
> WML translation failed.
> (14) : error: Element 'wml' is not complete. Expected elements 'card'
>
>
> ======================= End Errors =====================
>
> ************************ Current WML
> ******************************************
> <?xml version="1.0" ?>
> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
> "http://www.wapform.org/DTD/wml_1.1.xml";>
>
> <wml>
> <template>
> <do type="accept" label="Back">
> <prev/>
> </do>
> </template>
>
>
>
> </wml>
> ****************************************************************************
> ****
>
> Translation failed for content-type: text/vnd.wap.wml
>
>
> As you can see, the <card> element is missing, which is output from the
> default.vm ($screen_placeholder). The <template> statements are the output
> from wml/top.wml.
>
> This is strange, as $screen_placeholder is correctly inserted accessing the
> WML locally. Any clues? On the other hand, enabling all the debugging of the
> server.xml of tomcat, it gives for the remote access:
>
> 2001-09-26 11:28:00 - ContextManager: No handler for request R( /jetspeed +
> /compile-error.wml + null) 404
> 2001-09-26 11:28:00 - Ctx( /jetspeed ): 404 R( /jetspeed +
> /compile-error.wml + null) null
> 2001-09-26 11:28:00 - Ctx( /jetspeed ): Handler
> tomcat.notFoundHandler(null/null) tomcat.notFoundHandler
>
> Is there any further debuging level possible to trace down where jetspeed
> forgets to insert "$screen_placeholder -> default.psml"
>
>
> Gr�sse/Best Regards
>
> J�rgen
>
> *
> Juergen Riedl
>
> SIEMENS ICM S CP PE
> Geisenhausenerstr. 15, 81379 Muenchen, Germany
> Site: MchH/Ge15, Building 18600, Room 440
> Solutions Architect, Customer Projects, mtroop
> voice: (+49)-(0)89-722-42004 / fax: (+49)-(0)89-722-54725
> mobile:(+49)-(0)170-63 23 413 / email: [EMAIL PROTECTED]
> *
> "The future masters of technology will have to be lighthearted and
> intelligent. The machine easily masters the grim and the dumb.">
> -- Marshall McLuhan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
