[jira] [Commented] (CONFIGURATION-671) Empty ini section occurs NPE while save to writer
[
https://issues.apache.org/jira/browse/CONFIGURATION-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151983#comment-16151983
]
yankai zhang commented on CONFIGURATION-671:
That's very nice of you.
> Empty ini section occurs NPE while save to writer
> -
>
> Key: CONFIGURATION-671
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-671
> Project: Commons Configuration
> Issue Type: Bug
> Components: File reloading, Format
>Affects Versions: 2.1.1
> Environment: OS: OS X 10.12
> JDK: 1.8
>Reporter: yankai zhang
>Priority: Minor
> Fix For: 2.2
>
>
> Run following code:
> {code:java}
> import org.apache.commons.configuration2.INIConfiguration;
> import java.io.*;
> public class Demo {
>public static void main(String[] args) throws Exception {
> INIConfiguration ini = new INIConfiguration();
> ini.read(new StringReader("[emptySection]"));
> ini.write(new StringWriter());
> }
> }
> {code}
> Result:
> {noformat}
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.commons.configuration2.INIConfiguration.writeProperty(INIConfiguration.java:458)
> at
> org.apache.commons.configuration2.INIConfiguration.write(INIConfiguration.java:309)
> at Demo.main(Demo.java:8)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (JCS-119) replace synchronized blocks by java locks or concurrenhashmap
[ https://issues.apache.org/jira/browse/JCS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-119: --- Fix Version/s: (was: jcs-2.2) jcs-2.3 > replace synchronized blocks by java locks or concurrenhashmap > - > > Key: JCS-119 > URL: https://issues.apache.org/jira/browse/JCS-119 > Project: Commons JCS > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Thomas Vandahl > Fix For: jcs-2.3 > > > A cache is typically used in a concurrent environment. Since Java 6 using a > ReentrantLock is faster than synchronized so can be interesting to replace > synchronized blocks by a lock. > Places i'm thinking about: > * CompositeCache > * AbstractDoubleLinkedListMemoryCache > * LHMLRUMemoryCache > * DoubleLinkedList > * LRUMap > * SingleLinkedList > * SortedPreferentialArray > Some places where replacing a HashMap by a ConcurrentHashMap can allow to get > rid of synchronized without needing a lock: > * CacheEventQueue > * AbstractDiskCache > * CacheWatchRepairable > There are other places but this is the main I saw. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-122: --- Fix Version/s: (was: jcs-2.2) jcs-2.3 > rework logging? > --- > > Key: JCS-122 > URL: https://issues.apache.org/jira/browse/JCS-122 > Project: Commons JCS > Issue Type: Improvement >Reporter: Romain Manni-Bucau > Fix For: jcs-2.3 > > > currently JCS relies on [logging] > Would be great to get rid of this dependency. > Solutions I see: > 1) use JUL (with extensibility like in > http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/log/logger/) > 2) write a little factory with a jcs.Logger to be able to switch > Goal is to be able to adapt to frameworks and users. Guess first will be > often JUL (TomEE), second SLF4J, [logging]... > I'm for 1) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TEXT-101) Move RandomStringUtils to Commons-text
[ https://issues.apache.org/jira/browse/TEXT-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amey Jadiye updated TEXT-101: - Fix Version/s: 1.2 > Move RandomStringUtils to Commons-text > -- > > Key: TEXT-101 > URL: https://issues.apache.org/jira/browse/TEXT-101 > Project: Commons Text > Issue Type: Task >Reporter: Amey Jadiye > Fix For: 1.2 > > > This task contains not just moving but , > 1. Keep RandomStringUtils deprecated in commons-lang. > 2. Move RandomStringUtils class to commons-text. > 3. Remove all existing code from methods of RandomStringUtils and call our > brand new RandomStringGenerator in them. to return respective values i.e. > randomNumeric, randomAlphabetic, randomAlphanumeric etc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TEXT-101) Move RandomStringUtils to Commons-text
Amey Jadiye created TEXT-101: Summary: Move RandomStringUtils to Commons-text Key: TEXT-101 URL: https://issues.apache.org/jira/browse/TEXT-101 Project: Commons Text Issue Type: Task Reporter: Amey Jadiye This task contains not just moving but , 1. Keep RandomStringUtils deprecated in commons-lang. 2. Move RandomStringUtils class to commons-text. 3. Remove all existing code from methods of RandomStringUtils and call our brand new RandomStringGenerator in them. to return respective values i.e. randomNumeric, randomAlphabetic, randomAlphanumeric etc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
