[
https://issues.apache.org/jira/browse/TRB-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg updated TRB-91:
---------------------
Attachment: fulcrum-parser-update-bugfix.patch
With this patch covering the update to newest fulcrum-parser/upload with
dependencies and bugfixes
compilation with
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
was successfull for turbine-4.0-M2-SNAPSHOT.
A form with upload field was handled properly.
> urlfolding configuration value never read in fulcrum DefaultParserService
> --------------------------------------------------------------------------
>
> Key: TRB-91
> URL: https://issues.apache.org/jira/browse/TRB-91
> Project: Turbine
> Issue Type: Bug
> Components: Fulcrum
> Affects Versions: Core 4.0-M1
> Environment: fulcrum pool version: 1.0.4, windows 64bit, intel.
> Reporter: Georg Kallidis
> Priority: Minor
> Attachments: fulcrum-parser-update-bugfix.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> I followed the example
> http://wiki.apache.org/turbine/Turbine4/Turbine4.0M1/Migrate233.
> I set in componentConfiguration.xml for the parser element
> <urlCaseFolding>lower</urlCaseFolding>, but activating DEBUG, I get always
> urlCaseFolding = 1, i.e.
> org.apache.fulcrum.parser.ParserService.URL_CASE_FOLDING_NONE.
> Solution:
> In org.apache.fulcrum.parser.DefaultParserService.configure(Configuration)
> urlCaseFolding is only read from configuration
> if (folding == URL_CASE_FOLDING_UNSET). But folding is initialized with
> /** The folding from the configuration */
> private int folding = URL_CASE_FOLDING_NONE;
> As a consequence the configuraiton is never read (there is no setter), at
> least if I am not missing some hidden introspection!
> At least I could get to work only if I set private int folding to
> URL_CASE_FOLDING_UNSET; (or change the condition in configure to ..NONE).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
