[opencms-dev] OpenCms 6.0 beta 3 released

Stephan Hartmann hartmann at metamesh.de
Fri Apr 29 11:42:07 CEST 2005 

Hi Alex,
> 
>>1. Isn't it a bug, when the cmscontentload tag evaluates its 
>>body always at least one time, even if there are no (zero) 
>>xml files (bug 604)? 
> 
> No this is not a bug, since the evaluation is required to trigger an
> embedded "cms:contentinfo" tag which can be used to find out if there's
> content collected or not, and then e.g. print a line "there are no
> articles".

This is really not intuitive. You enforce one to use the 
"cms:contentinfo" tag to check if there is content at all and build some 
additional condition code around the body of the contentload tag, even 
if you don't need the info bean and paging information.
Then it would be better to split the funktionality of the contentload 
tag into two tags, one that loads the contents and one to iterate over it.

>>2. Isn't it a bug when a plain text resource that in the vfs 
>>has the file extension .txt is exported with a name like 
>>"file.txt_122334.html
> 
> If the resouce is a "plain" resoruce in OpenCms this won't happen. 

sorry for being unclear, i meant jsps generating plain text

> Since this is true most of the time the isse can be reduced to OpenCms
> resources that are in fact a JSP that generates a .txt (or .pdf). Writing
> this as .html is maybe bug. However, my solution would be to check the mime
> type header of the response stream to make sure the extension is applied
> correctly _and_ in the same way it is when not exporting the resource. 

what could be more correct than the choice of the file creator? Your 
suggestion would create a .txt extension for plain text even if i call 
my file config.properties. In other words, many file types share the 
same mime type but users certainly would prefer them to have their own 
file extension.

Regards,
Stephan

> This
> may relate to an issue in
> org.opencms.flex.CmsFlexResponse#setContentType(String) which is long left
> unsolved and which I am not certain of what the current status is, but I if
> the issue is to be fixed it should be done correctly.
> 
> Best Regards,
> Alex.
> 
> Alexander Kandzior
> Alkacon Software - The OpenCms Experts
> http://www.alkacon.com
> 
>  
> 
> 
>>-----Original Message-----
>>From: opencms-dev-bounces at opencms.org 
>>[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Stephan Hartmann
>>Sent: Friday, April 29, 2005 10:20 AM
>>To: The OpenCms mailing list
>>Subject: Re: [opencms-dev] OpenCms 6.0 beta 3 released
>>
>>Sorry Alex,
>>
>>you have to explain your definitons of a bug.
>>
>>1. Isn't it a bug, when the cmscontentload tag evaluates its 
>>body always at least one time, even if there are no (zero) 
>>xml files (bug 604)? This brings up code in the resulting 
>>html page that must not be there.
>>Example: you have a list view of events that have an expire 
>>date. When all events have expired, in the page there will be 
>>still one phantom event left but with out correct data. For 
>>me it is a bug.
>>
>>2. Isn't it a bug when a plain text resource that in the vfs 
>>has the file extension .txt is exported with a name like 
>>"file.txt_122334.html" 
>>so that tomcat accidently sets the mime type to text/html 
>>(bug 595)? It is really annoying to discuss why you would 
>>like to have the file extension to be the same in vfs and in 
>>rfs, when you would expect it as standard.
>>Example: you generate pdf files on the fly. Their content 
>>depends on one requesst parameter, so their export names 
>>become translated. But the name will be 
>>"somename.pdf_45346463.html". For me it is a bug.
>>
>>Surely, these are both no show stoppers, but definitely they 
>>are bugs. 
>>And the patches i posted are really not hardly to understand 
>>(604 is one single line of code). So better integrate them 
>>now instead of waiting until they won't work anymore because 
>>the code has changed (like the patches i made to JSTL-ize the 
>>contenload / contenshow tags :-( ).
>>
>>Regards,
>>Stephan
>>
>>Alexander Kandzior schrieb:
>>
>>>Stephan,
>>>
>>>It's better to have these in the bugzilla. We have schduled time 
>>>between May in June where we will try to work through all 
>>
>>open issues in bugzilla.
>>
>>>Of course, if there's a particular "show stopper" bug that we can 
>>>reproduce it will get fixed ASAP. However, we reserve the right to 
>>>define what a "show stopper bug" or even a "bug" in OpenCms is ;-)
>>>
>>>Your two entries in particular are both not bugs (according to our 
>>>definition), but enhancements to the current core 
>>
>>functionality with 
>>
>>>potential unknown and untested side effects on other 
>>
>>functions. So we 
>>
>>>will certainly look into your patches, but I can't promise if they 
>>>will make it to the release version or not.
>>>
>>>Best Regards,
>>>Alex.
>>>
>>>Alexander Kandzior
>>>Alkacon Software - The OpenCms Experts http://www.alkacon.com
>>>
>>> 
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: opencms-dev-bounces at opencms.org 
>>>>[mailto:opencms-dev-bounces at opencms.org] On Behalf Of 
>>
>>Stephan Hartmann
>>
>>>>Sent: Thursday, April 28, 2005 7:46 PM
>>>>To: The OpenCms mailing list
>>>>Subject: Re: [opencms-dev] OpenCms 6.0 beta 3 released
>>>>
>>>>Am Donnerstag 28 April 2005 18:27 schrieb Alexander Kandzior:
>>>>
>>>>
>>>>>Any help in developing the OpenCms 6.0 "final" version is greatly 
>>>>>appreciated. If you want to contribute, please contact me
>>>>
>>>>directly, or
>>>>
>>>>
>>>>>send a mail to this mailing list.
>>>>>
>>>>
>>>>Hi Alex,
>>>>
>>>>i reported some bugs with patches some weeks ago (595, 604).
>>>>Is it better to post them here in the list, too?
>>>>
>>>>Regards,
>>>>Stephan
>>>>
>>>>
>>>>
>>>>>Best Regards,
>>>>>Alex.
>>>>>
>>>>>Alexander Kandzior
>>>>>Alkacon Software - The OpenCms Experts http://www.alkacon.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>This mail is send to you from the opencms-dev mailing list 
>>
>>To change 
>>
>>>>>your list options, or to unsubscribe from the
>>>>
>>>>list, please visit
>>>>
>>>>
>>>>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>>>
>>>>
>>>>_______________________________________________
>>>>This mail is send to you from the opencms-dev mailing list 
>>
>>To change 
>>
>>>>your list options, or to unsubscribe from the list, please visit 
>>>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>This mail is send to you from the opencms-dev mailing list 
>>
>>To change 
>>
>>>your list options, or to unsubscribe from the list, please visit 
>>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>>
>>
>>_______________________________________________
>>This mail is send to you from the opencms-dev mailing list To 
>>change your list options, or to unsubscribe from the list, 
>>please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
> 
> 
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev

More information about the opencms-dev mailing list