[prev in list] [next in list] [prev in thread] [next in thread] 

List:       poi-dev
Subject:    [jira] [Updated] (XMLBEANS-546) These classes (org.apache.xmlbeans.impl.store.Locale,
From:       "Xiao Yuan (Jira)" <jira () apache ! org>
Date:       2019-09-23 1:56:00
Message-ID: JIRA.13258195.1569202126000.30208.1569203760230 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/XMLBEANS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Xiao Yuan updated XMLBEANS-546:
-------------------------------
    Description: 
Is there a dead loop in the exit() method of class \
org.apache.xmlbeans.impl.store.Locale?

public void exit()
    {
        // assert _numTempFramesLeft >= 0;
        //asserts computed frame fits between 
        //0 and _tempFrames.length
        assert _numTempFramesLeft >= 0 &&
            (_numTempFramesLeft <= _tempFrames.length - 1):
            " Temp frames mismanaged. Impossible stack frame. Unsynchronized: " + \
noSync();

        int frame = _tempFrames.length - ++_numTempFramesLeft;

        while (_tempFrames[frame] != null)
            _tempFrames[frame].release();
    }


 The process(String[], String[], boolean, boolean, boolean) method of class
org.apache.xmlbeans.impl.tool.BaseSchemaResourceManager has a bug. Here's the code \
snippet for the fix: for (int i = 0; i < filenames.length; i++)
 {
      SchemaResource resource = \
(SchemaResource)_resourceForFilename.get(filenames[i]);  if (resource != null)
                starterset.add(resource);
 }


In the class org.apache.xmlbeans.impl.tool.SchemaCodeGenerator, does that thread not \
need to be started in the tryToDeleteLater(File) method?



  was:
Is there a dead loop in the exit() method of class \
org.apache.xmlbeans.impl.store.Locale?

public void exit()
    {
        // assert _numTempFramesLeft >= 0;
        //asserts computed frame fits between 
        //0 and _tempFrames.length
        assert _numTempFramesLeft >= 0 &&
            (_numTempFramesLeft <= _tempFrames.length - 1):
            " Temp frames mismanaged. Impossible stack frame. Unsynchronized: " + \
noSync();

        int frame = _tempFrames.length - ++_numTempFramesLeft;

        while (_tempFrames[frame] != null)
            _tempFrames[frame].release();
    }

 The process(String[], String[], boolean, boolean, boolean) method of class
org.apache.xmlbeans.impl.tool.BaseSchemaResourceManager has a bug. Here's the code \
snippet for the fix: for (int i = 0; i < filenames.length; i++)
 {
      SchemaResource resource = \
(SchemaResource)_resourceForFilename.get(filenames[i]);  if (resource != null)
                starterset.add(resource);
 }

In the class org.apache.xmlbeans.impl.tool.SchemaCodeGenerator, does that thread not \
need to be started in the tryToDeleteLater(File) method?




> These classes (org.apache.xmlbeans.impl.store.Locale, \
> org.apache.xmlbeans.impl.tool.BaseSchemaResourceManager and \
>                 org.apache.xmlbeans.impl.tool.SchemaCodeGenerator) have bugs??
> ------------------------------------------------------------------------------------ \
> --------------------------------------------------------------------------------------------
>  
> Key: XMLBEANS-546
> URL: https://issues.apache.org/jira/browse/XMLBEANS-546
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 3.1.0
> Reporter: Xiao Yuan
> Priority: Major
> 
> Is there a dead loop in the exit() method of class \
> org.apache.xmlbeans.impl.store.Locale? public void exit()
> {
> // assert _numTempFramesLeft >= 0;
> //asserts computed frame fits between 
> //0 and _tempFrames.length
> assert _numTempFramesLeft >= 0 &&
> (_numTempFramesLeft <= _tempFrames.length - 1):
> " Temp frames mismanaged. Impossible stack frame. Unsynchronized: " + noSync();
> int frame = _tempFrames.length - ++_numTempFramesLeft;
> while (_tempFrames[frame] != null)
> _tempFrames[frame].release();
> }
> The process(String[], String[], boolean, boolean, boolean) method of class
> org.apache.xmlbeans.impl.tool.BaseSchemaResourceManager has a bug. Here's the code \
> snippet for the fix: for (int i = 0; i < filenames.length; i++)
> {
> SchemaResource resource = (SchemaResource)_resourceForFilename.get(filenames[i]);
> if (resource != null)
> starterset.add(resource);
> }
> In the class org.apache.xmlbeans.impl.tool.SchemaCodeGenerator, does that thread \
> not need to be started in the tryToDeleteLater(File) method?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]