struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <>
Subject Re: PlanetStruts has a "Proxy Error"
Date Sun, 24 Dec 2006 23:51:15 GMT

I just did a quick build with 2.0.1 and got
2006-12-24 18:40:10,718 ERROR [] : Unable to render XSLT Template, 'nofile.xsl'
javax.xml.transform.TransformerException: Stylesheet nofile.xsl not found in resources

Which distro has nofile.xsl ?
Martin --
This e-mail message (including attachments, if any) is intended for the use of the individual
or entity to which it is addressed and may contain information that is privileged, proprietary
, confidential and exempt from disclosure. If you are not the intended recipient, you are
notified that any dissemination, distribution or copying of this communication is strictly
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant)
s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé
ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il
est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message ----- 
From: "Dale Newfield" <>
To: "Struts Users Mailing List" <>
Sent: Sunday, December 24, 2006 3:46 PM
Subject: Re: PlanetStruts has a "Proxy Error"

> Ted Husted wrote:
>> Change to the showcase source directory and run mvn install
> That was the trick I was missing!  Thanks!
>> There's an open issue that suggest reverting the 2.0.2 datepicker,
>> which I may try to apply today.
>> *
> with the right mvn command I can now finally get the showcase working, 
> and it appears (at first glance--I'll need to do a little more testing) 
> that the datepicker and timepicker are working in there w/o this 
> patch...  (But with my one character change--I'll have to see if it 
> works w/o that.)
>> Actually, we'd prefer people did make changes to Struts to make it
>> work or make it work better, and then donate back the patches. :)
>> We're all working-stiffs here, just like you.
> I have a feeling the broken-ness may be in my app rather than struts. 
> Now I at least have a baseline against which to compare my app so I can 
> find the problems (whether they be in my code or in struts).   If I can 
> figure out for sure that it's in struts, I'll definitely submit issues 
> and patches.
>> If the datepickers works better for your with the trwithout the
>> trailing slash, then post a patch. It does seem to be broken in the
>> 2.0.1 beta, since the picker doesn't go away after selecting a field.
> Without that trailing slash none of the dojo based tools work for me 
> (not just the datepicker), so I doubt this is the showstopper you're 
> looking for.
>> It is not our intention for people to treat Struts like a
>> blackbox and use only whatever happens to be in the distribution.
> I know I can add in other tools, but I would like to be able to add them 
> in later as spit and polish.  This project is still in the (not very 
> rapid right now) prototyping phase, and in order to make reasonable 
> progress I need to be using a framework powerful enough to provide some 
> fairly complex tools out of the box.  The fact that struts integrates an 
> ajax toolkit to provide these is a major point in its favor.  (Of 
> course, on top of the fact that is a first class framework that should 
> help yield a maintainable application.)  But, there are other 
> frameworks, and I need to start making progress again soon.  I hope I am 
> able to stick with struts.  Time will tell.
>> And, honestly, if someone doesn't fix the datepicker tag soon, it's
>> not going to be in the GA distirbution anyway.
> While I recognize this is not a key component of an MVC framework, it is 
> a key datatype that lots of applications need to ask users to specify, 
> so would be a shame to have to exclude it.  Here's hoping that we can 
> get it working in time.
> Thanks,
> -Dale
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
View raw message