struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonios Gkogkakis <gkogk...@tcd.ie>
Subject Re: DateTimePicker not showing
Date Tue, 02 Jul 2013 08:29:12 GMT
Hi Fabian,

since you are migrating your application now, I would recommend not to use
the sx tags which are backed by the dojo plugin.
This plugin is based on a very old version of dojo (you will be having
problems with IE9) and I think that it's going to be deprecated in the next
struts major release.

For the calendar, I recommend the jquery datepicker http://jqueryui.com/
datepicker/ which you can either use directly (using s:textfield and js)
or via the struts2 jquery plugin.


Antonios




On 2 July 2013 09:20, Fabian Richter <frichter@mtg.de> wrote:

> Hi,
>
> I am still trying to migrate our application from Webwork to Strut2.
>
> The site uses sitemesh with freemarker templates and used a
> <ww:datepicker.../> from Webwork.
>
> This tag was replaced in struts2 with <sx:datetimepicker but doesnt show
> up in my application.
>
> I added <sx:head ... > in the <head> section of my jsp. I included the
> plugin in my WEB-INF/lib folder and changed my web.xml according to
>
> https://issues.apache.org/**jira/browse/WW-3296<https://issues.apache.org/jira/browse/WW-3296>
>
> Then I excluded
>
>         <pattern>/struts/dojo/*</**pattern>
>         <pattern>/struts/ajax/*</**pattern
>
> in decordators.xml and replaced the HTMLPageParsers in sitemesh.xml with
>
> <parser content-type="text/html" class="com.opensymphony.**
> module.sitemesh.parser.**FastPageParser"/>
>
> which was a hint for that issue on some website.
>
> But the Datetimepicker is still now rendered at my website. I dont get any
> errors in my tomcat logs, only 2 javascript errors when calling the website
> that has the DateTimePicker on it:
>
> TypeError: dojo.widget.manager is undefined @ https://.../struts/ajax/**
> dojoRequire.js:27
> TypeError: dojo.xml.Parse is not a constructor @ https://
> .../struts/dojo/dojo.**js:900
>
> Any idea if these are the critical errors? If not, what else could have
> been wrong?
>
> Thank you in advance
>
> Best
> Fabian
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message