Build failed in Jenkins: POI » POI-DSL-1.8 #321

2021-08-31 Thread Apache Jenkins Server 
See 

Changes:


--
[...truncated 439.82 KB...]
^
:401:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
:403:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
:89:
 warning: [deprecation] getCode() in org.apache.poi.ss.usermodel.CellType has 
been deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
   ^
:89:
 warning: [deprecation] getCachedResultType() in 
org.apache.poi.hssf.record.FormulaRecord has been deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
 ^
:212:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
15 warnings

> Task :poi:compileTest9 SKIPPED
> Task :poi:cacheTest9 NO-SOURCE
> Task :poi:processTestResources
> Task :poi:testClasses
> Task :poi:testJar
> Task :poi-integration:compileJava NO-SOURCE
> Task :poi-integration:processResources NO-SOURCE
> Task :poi-integration:classes UP-TO-DATE
> Task :poi-ooxml-lite-agent:compileJava
> Task :poi-ooxml-lite-agent:processResources NO-SOURCE
> Task :poi-ooxml-lite-agent:classes
> Task :poi-ooxml-lite-agent:jar

> Task :poi-scratchpad:compileTestJava
:64:
 warning: [deprecation] getParagraphStyle(int) in 
org.apache.poi.hwpf.model.StyleSheet has been deprecated
assertEquals(expectedStyleLvl, 
styleSheet.getParagraphStyle(par.getStyleIndex()).getLvl());
 ^
:186:
 warning: [deprecation] getParagraphText() in 
org.apache.poi.hwpf.extractor.Word6Extractor has been deprecated
for (String p : ex.getParagraphText()) {
  ^
:203:
 warning: [deprecation] getParagraphText() in 
org.apache.poi.hwpf.extractor.Word6Extractor has been deprecated
for (String p : ex.getParagraphText()) {
  ^
:240:
 warning: [deprecation] getParagraphText() in 
org.apache.poi.hwpf.extractor.Word6Extractor has been deprecated
for (String p : ex.getParagraphText()) {
  ^
:50:
 warning: [deprecation] 
writeTo(org.apache.poi.hwpf.model.io.HWPFFileSystem,int) in 
org.apache.poi.hwpf.model.SectionTable has been deprecated
sectionTable.writeTo(fileSys, 0);
^
:47:
 warning: [deprecation] writeTo(org.apache.poi.hwpf.model.io.HWPFFileSystem) in 
org.apache.poi.hwpf.model.FontTable has been deprecated
_fontTable.writeTo(fileSys);
  ^
:53:
 warning: [deprecation] 
writeTo(org.apache.poi.hwpf.model.io.HWPFFileSystem,int,org.apache.poi.hwpf.model.CharIndexTranslator)
 in org.apache.poi.hwpf.model.CHPBinTable has been deprecated
_cHPBinTable.writeTo(fileSys, 0, fakeTPT);
^
:77:
 warning: [deprecation] getParagraphStyle(int)

[jira] [Commented] (XMLBEANS-495) StackOverflowError when parsing a large number of characters in an XML element

2021-08-31 Thread PJ Fanning (Jira) 


[ 
https://issues.apache.org/jira/browse/XMLBEANS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407689#comment-17407689
 ] 

PJ Fanning commented on XMLBEANS-495:
-

I'm looking at the possibility of copying the xerces code - but the code while 
it started out the same, it has diverged a lot.

> StackOverflowError when parsing a large number of characters in an XML element
> --
>
> Key: XMLBEANS-495
> URL: https://issues.apache.org/jira/browse/XMLBEANS-495
> Project: XMLBeans
>  Issue Type: Bug
>  Components: Validator
>Affects Versions: Version 2.6
> Environment: All
>Reporter: Mandy Warren
>Assignee: PJ Fanning
>Priority: Major
>
> When XMLBeans validates a very long XML String (4000 or so chars), it 
> generates a StackOverFlowError as shown below. In the schema for this element 
> I have defined a pattern and a min/max length but XMLBeans is applying the 
> pattern first before checking the length. The solution is the fix applied to 
> the class RegularExpression in xerces - see 
> https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 
> 2.11. 
>   
>   
>   
>   
>   
>   
>   
> Exception in thread "main" java.lang.StackOverflowError
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)



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

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

[jira] [Assigned] (XMLBEANS-495) StackOverflowError when parsing a large number of characters in an XML element

2021-08-31 Thread PJ Fanning (Jira) 


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

PJ Fanning reassigned XMLBEANS-495:
---

Assignee: PJ Fanning

> StackOverflowError when parsing a large number of characters in an XML element
> --
>
> Key: XMLBEANS-495
> URL: https://issues.apache.org/jira/browse/XMLBEANS-495
> Project: XMLBeans
>  Issue Type: Bug
>  Components: Validator
>Affects Versions: Version 2.6
> Environment: All
>Reporter: Mandy Warren
>Assignee: PJ Fanning
>Priority: Major
>
> When XMLBeans validates a very long XML String (4000 or so chars), it 
> generates a StackOverFlowError as shown below. In the schema for this element 
> I have defined a pattern and a min/max length but XMLBeans is applying the 
> pattern first before checking the length. The solution is the fix applied to 
> the class RegularExpression in xerces - see 
> https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 
> 2.11. 
>   
>   
>   
>   
>   
>   
>   
> Exception in thread "main" java.lang.StackOverflowError
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)



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

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

[jira] [Commented] (XMLBEANS-566) Configuration property "quiet" in the maven plugin is spelled wrong

2021-08-31 Thread PJ Fanning (Jira) 


[ 
https://issues.apache.org/jira/browse/XMLBEANS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407653#comment-17407653
 ] 

PJ Fanning commented on XMLBEANS-566:
-

I tried to keep the 'quite' param while also supporting 'quiet'. 
[https://github.com/apache/xmlbeans/commit/6422ec6b8b20328d811d7cbc6483f23525995a73]
 has a bug that was fixed in 
https://github.com/apache/xmlbeans/commit/003dd33d1390e7ce3c96285a6378bdd20f544829

> Configuration property "quiet" in the maven plugin is spelled wrong
> ---
>
> Key: XMLBEANS-566
> URL: https://issues.apache.org/jira/browse/XMLBEANS-566
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.0, Version 5.0.1
>Reporter: Travis Schneeberger
>Assignee: PJ Fanning
>Priority: Minor
> Fix For: Version 5.0.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The configuration property "quiet" is spelled as "quite" in the new maven 
> plugin introduced in version 5.0.0.
> {code:java}
> 
>   org.apache.xmlbeans
>   xmlbeans
>   5.0.1
>   
>     false
>   
> {code}



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

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

[jira] [Updated] (XMLBEANS-566) Configuration property "quiet" in the maven plugin is spelled wrong

2021-08-31 Thread PJ Fanning (Jira) 


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

PJ Fanning updated XMLBEANS-566:

Fix Version/s: Version 5.0.2

> Configuration property "quiet" in the maven plugin is spelled wrong
> ---
>
> Key: XMLBEANS-566
> URL: https://issues.apache.org/jira/browse/XMLBEANS-566
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.0, Version 5.0.1
>Reporter: Travis Schneeberger
>Assignee: PJ Fanning
>Priority: Minor
> Fix For: Version 5.0.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The configuration property "quiet" is spelled as "quite" in the new maven 
> plugin introduced in version 5.0.0.
> {code:java}
> 
>   org.apache.xmlbeans
>   xmlbeans
>   5.0.1
>   
>     false
>   
> {code}



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

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

[jira] [Assigned] (XMLBEANS-566) Configuration property "quiet" in the maven plugin is spelled wrong

2021-08-31 Thread PJ Fanning (Jira) 


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

PJ Fanning reassigned XMLBEANS-566:
---

Assignee: PJ Fanning

> Configuration property "quiet" in the maven plugin is spelled wrong
> ---
>
> Key: XMLBEANS-566
> URL: https://issues.apache.org/jira/browse/XMLBEANS-566
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.0, Version 5.0.1
>Reporter: Travis Schneeberger
>Assignee: PJ Fanning
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The configuration property "quiet" is spelled as "quite" in the new maven 
> plugin introduced in version 5.0.0.
> {code:java}
> 
>   org.apache.xmlbeans
>   xmlbeans
>   5.0.1
>   
>     false
>   
> {code}



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

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

Re: Next release of POI

2021-08-31 Thread Dominik Stadler 
Similar for me,

a) good time roll the next release

b) whatever is easier right now, we can also use Ant once again if Gradle
needs a bit more work

c) I'd also opt for 5.1.0, it does not feel like big enough changes for a
major release

Dominik.


On Tue, Aug 31, 2021 at 5:08 PM Alain FAGOT BÉAREZ 
wrote:

> Hi,
>
> a) many changes deserve to be released
>
> b) up to you to estimate the benefits or the burden
>
> c) I don't think we introduced API breaking changes, so 5.1.0 would
> encompass the logging changes
>
> Best regards,
> Alain FAGOT BÉAREZ
>
>
> ⁣Obter o BlueMail para Android ​
>
> Em 29 de ago de 2021 21:11, em 21:11, PJ Fanning
>  escreveu:
> >Hi Andi,
> >
> >a) I think we need a new release
> >
> >b) I don't think we need to solve all the build issues before the next
> >release
> >
> >c) I'd prefer to call the next release 6.0.0 or failing that 5.1.0. The
> >log4j change makes calling next release 5.0.1 problematic for me.
> >
> >
> >
> >
> >
> >
> >On Sunday 29 August 2021, 18:57:42 IST, Andreas Beeker
> > wrote:
> >
> >
> >
> >
> >
> >Hi Devs,
> >
> >a) what's your opinion about rolling the next release?
> >
> >From my side, only the distsource build is not implemented in gradle
> >and a few of the release task need to be done manually.
> >
> >b) Now that the gradle dist plugin picks up all the dependencies, how
> >important is the distsource check?
> >
> >c) what's our next release version? 5.0.1,  5.1 or 6.0
> >
> >Andi
> >
> >
> >-
> >To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> >For additional commands, e-mail: dev-h...@poi.apache.org
> >
> >
> >-
> >To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> >For additional commands, e-mail: dev-h...@poi.apache.org
>

[jira] [Commented] (XMLBEANS-562) java.lang.ClassCastException: org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl cannot be cast to org.apache.xmlbeans.SchemaTypeLoader

2021-08-31 Thread PJ Fanning (Jira) 


[ 
https://issues.apache.org/jira/browse/XMLBEANS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407633#comment-17407633
 ] 

PJ Fanning commented on XMLBEANS-562:
-

This appears to be specific to how weblogic works - I think you'll need to 
bring this Weblogic support.

> java.lang.ClassCastException: 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl cannot be cast to 
> org.apache.xmlbeans.SchemaTypeLoader
> -
>
> Key: XMLBEANS-562
> URL: https://issues.apache.org/jira/browse/XMLBEANS-562
> Project: XMLBeans
>  Issue Type: Bug
>  Components: XmlObject
>Affects Versions: Version 4.0.0
>Reporter: Annapurna Theerthala
>Priority: Critical
> Fix For: Version 5.0.1
>
>
> I am getting the below error when exporting excel using POI 5 with xmlbeans 4.
>  
> `at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:348)
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.build(SchemaTypeLoaderImpl.java:161)
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.(SchemaTypeSystemImpl.java:168)
>  at 
> org.apache.xmlbeans.metadata.system.sXMLSCHEMA.TypeSystemHolder.(TypeSystemHolder.java:41)
>  Truncated. see log file for complete stacktrace
> Caused By: org.apache.xmlbeans.XmlRuntimeException: 
> java.lang.ClassCastException: 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl cannot be cast to 
> org.apache.xmlbeans.SchemaTypeLoader
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.build(SchemaTypeLoaderImpl.java:164)
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.(SchemaTypeSystemImpl.java:168)
>  at 
> org.apache.xmlbeans.metadata.system.sXMLTOOLS.TypeSystemHolder.(TypeSystemHolder.java:41)
>  at 
> org.apache.xmlbeans.metadata.system.sXMLTOOLS.TypeSystemHolder.(TypeSystemHolder.java:44)
>  at java.lang.Class.forName0(Native Method)
>  Truncated. see log file for complete stacktrace
> Caused By: java.lang.ClassCastException: 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl cannot be cast to 
> org.apache.xmlbeans.SchemaTypeLoader
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.build(SchemaTypeLoaderImpl.java:162)
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.(SchemaTypeSystemImpl.java:168)
>  at 
> org.apache.xmlbeans.metadata.system.sXMLTOOLS.TypeSystemHolder.(TypeSystemHolder.java:41)
>  at 
> org.apache.xmlbeans.metadata.system.sXMLTOOLS.TypeSystemHolder.(TypeSystemHolder.java:44)
>  at java.lang.Class.forName0(Native Method)
>  Truncated. see log file for complete stacktrace
> I have checked that my `xmlbeans` come from `xmlbeans-4.0.0.jar` and the 
> `ooxml-schema` has been removed and replaced with `poi-ooxml-full-5.0.0.jar`
> {{Tried with poi-ooxml-schemas-5.0.0.jar as well. still the same issue.}}
>  



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

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

[jira] [Commented] (XMLBEANS-561) XPath support for namespace prefix to URI mappings

2021-08-31 Thread PJ Fanning (Jira) 


[ 
https://issues.apache.org/jira/browse/XMLBEANS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407617#comment-17407617
 ] 

PJ Fanning commented on XMLBEANS-561:
-

Could you provide a test case for the xpath namespace declaration not working? 
There are test cases that show that it does work at least in some cases - eg 
https://github.com/apache/xmlbeans/blob/trunk/src/test/java/xmlcursor/checkin/GetDocChangeStampTest.java

 

 

> XPath support for namespace prefix to URI mappings
> --
>
> Key: XMLBEANS-561
> URL: https://issues.apache.org/jira/browse/XMLBEANS-561
> Project: XMLBeans
>  Issue Type: Improvement
>  Components: XPath
>Affects Versions: Version 5.0.0
>Reporter: Dimitrios Lagkouvardos
>Priority: Major
>
> 5.0.0 supports Saxon and an XmlBeans xpath engine. I don't see a way to 
> configure or supply at runtime namespace prefix to URI mappings.
> *Suggestions*:
> 1) One solution is to enhance XmlObject.selectPath(String,XmlOptions) to use 
> the namespaces returned by XmlOptions.getLoadAdditionalNamespaces (or perhaps 
> add a new method if this is deemed inappropriate).
> 2) An alternative is to add an extension to retrieve the mappings to be 
> passed to the xpath engine (instead of passing it on each call to selectPath).
> *Note*: Adding the namespace declaration to the xpath expression as 
> documented in [http://xmlbeans.apache.org/guide/XPathXQuery.html] does NOT 
> work:
> ```
> java.lang.RuntimeException: net.sf.saxon.trans.XPathException: Namespace 
> prefix 'table' has not been declared
>  at 
> org.apache.xmlbeans.impl.xpath.saxon.SaxonXPath.selectNodes(SaxonXPath.java:128)
>  at 
> org.apache.xmlbeans.impl.xpath.saxon.SaxonXPath.selectPath(SaxonXPath.java:133)
>  at 
> org.apache.xmlbeans.impl.xpath.saxon.SaxonXPathEngine.next(SaxonXPathEngine.java:60)
>  at org.apache.xmlbeans.impl.store.Cursor._toSelection(Cursor.java:749)
>  at org.apache.xmlbeans.impl.store.Cursor._toNextSelection(Cursor.java:736)
>  at org.apache.xmlbeans.impl.store.Cursor._hasNextSelection(Cursor.java:728)
>  at org.apache.xmlbeans.impl.store.Cursor.syncWrapHelper(Cursor.java:2520)
>  at org.apache.xmlbeans.impl.store.Cursor.syncWrap(Cursor.java:2451)
>  at org.apache.xmlbeans.impl.store.Cursor.hasNextSelection(Cursor.java:2022)
>  at 
> org.apache.xmlbeans.impl.values.XmlObjectBase.selectPath(XmlObjectBase.java:496)
> ```
>  



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

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

Re: Next release of POI

2021-08-31 Thread Alain FAGOT BÉAREZ 
Hi,

a) many changes deserve to be released

b) up to you to estimate the benefits or the burden

c) I don't think we introduced API breaking changes, so 5.1.0 would encompass 
the logging changes

Best regards,
Alain FAGOT BÉAREZ


⁣Obter o BlueMail para Android ​

Em 29 de ago de 2021 21:11, em 21:11, PJ Fanning  
escreveu:
>Hi Andi,
>
>a) I think we need a new release
>
>b) I don't think we need to solve all the build issues before the next
>release
>
>c) I'd prefer to call the next release 6.0.0 or failing that 5.1.0. The
>log4j change makes calling next release 5.0.1 problematic for me. 
>
>
>
>
>
>
>On Sunday 29 August 2021, 18:57:42 IST, Andreas Beeker
> wrote:
>
>
>
>
>
>Hi Devs,
>
>a) what's your opinion about rolling the next release?
>
>From my side, only the distsource build is not implemented in gradle
>and a few of the release task need to be done manually.
>
>b) Now that the gradle dist plugin picks up all the dependencies, how
>important is the distsource check?
>
>c) what's our next release version? 5.0.1,  5.1 or 6.0
>
>Andi
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>For additional commands, e-mail: dev-h...@poi.apache.org
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

--- Comment #5 from PJ Fanning  ---
LinkVideoToPptx in poi-examples may also be useful for ideas

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

--- Comment #4 from PJ Fanning  ---
there is an answer on
https://stackoverflow.com/questions/48141061/apache-poi-putting-hyperlink-in-images
that shows how this might be done using POI for Excel but you might be able to
gain some insights that help you solve this for Powerpoint

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

--- Comment #3 from PJ Fanning  ---
var rel = slide.getPackagePart()
.addRelationship(uri, TargetMode.EXTERNAL,
XSLFRelation.HYPERLINK.getRelation());

the uri in this call is not for adding mailto addresses - this is for accessing
files with the pptx zip file.

Using the CTPicture class like that is not a directly supported part of POI.
Those classes are generated from the Microsoft XML schemas. Many people can
work out how to do custom code using them but it is basically the wild west.
People generally start by producing a pptx in Powerpoint and then unzipping it
to look at the XML they need to produce.

XLSFHyperlink is the supported POI class. I am not sure if it can be used to
associate a hyperlink to a picture.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

--- Comment #2 from Henry Iguaro  ---
Hi Nick, thank you for looking into this!

I'm afraid we won't be able to provide such a file as we are trying to generate
the presentation dynamically from code, and because of the exception, the file
is never created.

Is there anything else we could try in order to help?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

Nick Burch  changed:

   What|Removed |Added

 OS||All
 Status|NEW |NEEDINFO

--- Comment #1 from Nick Burch  ---
Would you be able to generate a file like this using Microsoft Office, unzip
it, and post the XML parts for the image and the relationships?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65530] New: Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a NullPointerException.

2021-08-31 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65530

Bug ID: 65530
   Summary: Adding an opaque URI hyperlink (e.g., 'mailto', 'tel')
to an image triggers a NullPointerException.
   Product: POI
   Version: unspecified
  Hardware: Macintosh
Status: NEW
  Severity: normal
  Priority: P2
 Component: XSLF
  Assignee: dev@poi.apache.org
  Reporter: he...@canva.com
  Target Milestone: ---

Adding an opaque URI hyperlink (e.g., 'mailto', 'tel') to an image triggers a
NullPointerException.

var uri = toUri("mailto:foo@bar;);
System.out.println("Is URI opaque? " + uri.isOpaque());
var nvPicPr = ((CTPicture) picture.getXmlObject()).getNvPicPr();
var cNvPr = nvPicPr.getCNvPr() != null ? nvPicPr.getCNvPr() :
nvPicPr.addNewCNvPr();
var hyperlink = cNvPr.addNewHlinkClick();
//
// Here is where the NullPointerException is thrown
// 
var rel = slide.getPackagePart()
.addRelationship(uri, TargetMode.EXTERNAL,
XSLFRelation.HYPERLINK.getRelation());
hyperlink.setId(rel.getId())

We tracked it down to file PackagingURIHelper.java, method
`isRelationshipPartURI`:

public static boolean isRelationshipPartURI(URI partUri) {
if (partUri == null)
throw new IllegalArgumentException("partUri");

// 
// !! Here, calling partUri.getPath() when the URI is opaque returns null !!
//
return partUri.getPath().matches(
".*" + RELATIONSHIP_PART_SEGMENT_NAME + ".*"
+ RELATIONSHIP_PART_EXTENSION_NAME + "$");
}  

Part of the stack trace:

java.lang.NullPointerException
at
org.apache.poi.openxml4j.opc.PackagingURIHelper.isRelationshipPartURI(PackagingURIHelper.java:169)
at
org.apache.poi.openxml4j.opc.PackagePart.addRelationship(PackagePart.java:337)
at
org.apache.poi.openxml4j.opc.PackagePart.addRelationship(PackagePart.java:293)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[jira] [Created] (XMLBEANS-568) threadsafe

2021-08-31 Thread Delany (Jira) 
Delany created XMLBEANS-568:
---

 Summary: threadsafe
 Key: XMLBEANS-568
 URL: https://issues.apache.org/jira/browse/XMLBEANS-568
 Project: XMLBeans
  Issue Type: Improvement
  Components: Tools
Affects Versions: Version 5.0.1
Reporter: Delany


Can the Maven plugin be marked as threadsafe?

Is this addressed in the latest? 
https://issues.apache.org/jira/browse/XMLBEANS-388?focusedCommentId=12663801=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12663801

 



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

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