on 03-28-2006 10:21 AM
Hello again,
I have a general question to Web Dynpro.
When I have programmed in the past with a J2EE-engine
I made jsp-sites for the presentation in the web-browser.
Now I want to know how Web Dynpro does the presentation?
I know that there will be built a ear-file at deploying and in it is a wda-file.
But in the wda file are only class-files and meta-infos.
Where are the files for the presentation like jsp-files?
Patrick
Ok, thank you very much.
I think I understand it now a bit better.
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok,
all informations are saved into xml-files
and when the client is a pc with windows
the server knows that the file will be a
html-file with css and js,
and the infos about the layout come from a
xml-file?
Is that right?
I only habe problem with that, that you
only have xml files and out of this there
will be crate the view?
Where are the infos where e.g. the buttons,
or textfields will be displayed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Patrick,
<i>and when the client is a pc with windows the server knows that the file will be a html-file with css and js,
and the infos about the layout come from a xml-file?
Is that right?</i>
Yes, with small correction. Not a server itself, but WebDynpro container (like classic J2EE Web container).
<i>Where are the infos where e.g. the buttons,
or textfields will be displayed.</i>
At least at design time this information is stored in this XML files (like *.wdview). Next, it could be either transformed in Java code via generation (like JSP compilation) or packed as is and then used directly at run-time. Whatever approach works best -- this judgement is up to WD team, WD developers are isolated from such details.
Valery Silaev
EPAM Systems
Ok, so far so good,
but what is the format of the file that is
shown at my browser.
Is it normal html-side with a css-file for the layout?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Patrick,
Actually, it depends (it == output).
Currently, in browser it is HTML + JS + CSS (and ad-hoc logic for flicker-free display)
In some mobile clients (PocketIE, for example) it is HTML (not sure about CSS, probably it is used too)
For Blackberry devices it is WML (heck, why they think that this device unnable to display HTML/CSS ???
For smart clients (like SAP GUI for Java) it is just an XML transfered between client rendering engine and server.
Valery Silaev
EPAM Systems
That's not quite correct. The .xlf files contain only the translatable texts, the view layout is stored in .wdview files.
You can find the .wdview files in your NWDS if you open the Navigator and go to folder src/packages/<packagename>/<ViewName>.wdview
Armin
Message was edited by: Armin Reichert
Patrick,
Mostly inside this WDA
Seriously, xml files are, up to ceratin extent, are description of UI (in terms of view layouts, panels, tables, combo-boxes) + declaration of context structures (unlike in JSP, this is formalized artifact).
Classes merely resembles controller code.
Having xml description of UI allows to produce output for multiple devices / clients (Smart client, hand-helds, browsers). This is what JSP has declaratively but fails to do in practice.
Valery Silaev
EPAM Systems
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.