Difference between jspui and xmlui

[Natalia Queiroz]

Hello Goup,

i'm new on Dspace and I could not understand the difference between jspui and xmlui web applicaton.

Are they the samething?

Regards,
Natália

[Peter Dietz]

Hi Natalia,

For somewhat recent information on JSPUI, be sure to look at the slides Cineca presented at OR14 in Helsinki.

http://www.doria.fi/bitstream/handle/10024/97721/JSPUI-reborn.pdf?sequence=1

It is probably best to just look at all the slides, but they provide their opinion on page 92/93.

Basically, both UI's are supported by a faction of committers and the community. They don't have full parity of features (one might have something the other doesn't), but are pretty close. To an end user or administrator they have similar feature sets. 

JSPUI has made some very impressive improvements in the past year or so. It has a lot of administrative buttons, and its Batch Import from the UI works better as it runs as a background thread. But some statistics viewers aren't available in JSPUI.

XMLUI, for developers, relies on cocoon, pipelines, and xslt transformations, which has a pretty steep learning curve. To change a piece of content on a page will involve checking a dozen possible generators, sitemaps, xsl stylesheets, and then you might still be limited, unless you want to tackle a big project. XMLUI seems to have the most currently active user base at the moment. To an end user or administrator it has a lot of features.

JSPUI, for developers, uses JSPs, which mix html and java into the view. It could be better arranged such that less Java logic happened in the views. However, JSPUI is much much simpler to work with than XMLUI.

Not relevant at the current moment, but the DSpace developer community is looking at plans for a "next UI" that picks a best new technology framework to build a new user interface from. One that can hopefully replace both xmlui and jspui, and have users adopt that new UI in the future, and not have the decision to make about which UI, or splitting the user community. There are some prototype UI's built on top of the REST API.

________________
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[Bram Luyten]

In addition to this, here is where you can see both user interfaces in action:

XMLUI (Mirage 2 theme): http://demo.dspace.org/xmlui/

JSPUI: http://demo.dspace.org/jspui/

Bram

-- 

Bram Luyten  250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com

[Natalia Queiroz]

Hello Peter and Bram, thanks for the answers.

I tried to change some css values on /dspace/webapps/jspui/static/css/bootstrap directory and also changed the jsp pages on /dspace/webapps/jspui/layout without success. The changes are not showing

How to change the layout (css and jsp pages)? Is it necessary to re-compile code?

I tried it but it overwrites the code on dspace/webapps/jspui/ folder.

--

Natália Oliveira

[Natalia Queiroz]

Anyone?

--

Natália Oliveira

[Bram Luyten]

Hi Natalia,

in general it's recommended to make these changes in the src folder, so that the recompiling has the desired effect, e.g. that your new changes are not lost because you've applied them in the source folder.

But normally, if your tomcat looks at  /dspace/webapps/ for your deployed webapps, changing it in this folder directly should take effect after a tomcat restart.

hope this helps!

Bram

-- 

Bram Luyten  250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com