[Bug 59268] New: Work on providing an updated version of XMLBeans

classic Classic list List threaded Threaded
41 messages Options
123
Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #15 from PJ Fanning <[hidden email]> ---
I added a fix for the duplicate classes in
https://github.com/pjfanning/xmlbeans - I will publish a 2.6.2 jar in the
coming days if there are no other xmlbeans issues to fix.

Feel free to highlight any issues from XMLBeans in the issue tracker for the
github fork.
https://issues.apache.org/jira/browse/XMLBEANS-513?jql=project%20%3D%20XMLBEANS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22)

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #16 from Dominik Stadler <[hidden email]> ---
Thanks for the work, I have tested it a bit and so far it looks quite good.

One thing we could try is to remove the stax-api dependency from the Maven
deployment, I don't think this is still necessary with Java 6 or newer.

As far as I see the other most pressing items are in place now and I would
rather release a first piece instead of adding more aggressive stuff, we can
always do this later in a second release.

Should we start discussion on [hidden email] on required next steps
for publishing an official bugfix-release of xmlbeans?

In fact with your release on Maven Central we could even technically switch to
this without a release from the attic, but it would probably require some due
diligence on licensing of the additional patches, ...

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #17 from Nick Burch <[hidden email]> ---
I think best practice would be to speak with the Attic PMC about this

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #18 from PJ Fanning <[hidden email]> ---
I agree that getting an official apache xmlbeans patch done is preferable to
having people use my forked jar. This jar solves some issues with writing XSSF
workbooks that have unicode surrogate chars.

I have found a related issue in the SXSSF code base.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61246 This means that for
writing SXSSF workbooks, users affected by the unicode surrogate chars issues
will need the fork xmlbeans jar and the latest POI code (or 3.17 beta2 when it
is released).

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |54084
         Depends on|54084                       |


Referenced Bugs:

https://bz.apache.org/bugzilla/show_bug.cgi?id=54084
[Bug 54084] Some Unicode chars(e.g chinese chars) are not written corectly in
xlsx file.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |58247


Referenced Bugs:

https://bz.apache.org/bugzilla/show_bug.cgi?id=58247
[Bug 58247] Some UTF-16 characters are not handled correctly (likely surrogate
pair related)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |61494
                 CC|                            |[hidden email]

--- Comment #19 from Dominik Stadler <[hidden email]> ---
*** Bug 61494 has been marked as a duplicate of this bug. ***


Referenced Bugs:

https://bz.apache.org/bugzilla/show_bug.cgi?id=61494
[Bug 61494] Updating meta properties in xlsm/xlsx corrupted equation
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #20 from Dominik Stadler <[hidden email]> ---
*** Bug 58247 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #21 from Dominik Stadler <[hidden email]> ---
*** Bug 54084 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #22 from [hidden email] ---
I think the more appropriate course of action would be to remove xmlbeans as a
dependency.  The project was terminated over 4 years ago.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #23 from Nick Burch <[hidden email]> ---
(In reply to Scott Coldwell from comment #22)
> I think the more appropriate course of action would be to remove xmlbeans as
> a dependency.  The project was terminated over 4 years ago.

Removing XMLBeans is probably something like 3-6 months of work, and would have
the added disadvantage of probably breaking something like half of all the POI
examples for XLSX / PPTX / DOCX on the internet, and probably most of the big
projects which make deep/custom use of POI for XLSX/PPTX/DOCX processing....

The first step, for which volunteers are very very much welcome(!) is to locate
all the places in your favourite bit of POI (eg XSSF) that leak the CT*
xmlbeans objects, search public examples / github projects / mailing lists etc
to see how those beans are used, ensure we have a proper Usermodel wrapper for
doing the same thing "properly", then deprecate that CT accessor. Once
everything that's commonly done via the low-level xmlbeans classes in other
people's code can be done cleanly with proper POI classes, we can get people to
migrate, then we're in a position to swap out the POI innards to use something
else.

It's quite a lot of work though, which is why more volunteers are needed to
help drive it! :)

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #24 from Greg Woolsey <[hidden email]> ---
Another complication is that none of the replacement technologies that have
been discussed so far can handle the arbitrary XML allowed as "extensions" in
the OOXML spec. One benefit of XMLBeans is that it keeps the raw XML around and
returns any properties/attributes present when asked.  That way POI can "pass
through" unknown content while allowing access to all known content in a file.
This is used quite often by downstream projects, especially ones that start
with custom "template" files containing bits like OLE components, custom Office
extensions, VBA macros, complex pivot tables, etc. and fill in live data on the
fly.  

In the spec this is handled by referencing additional namespaces on the fly by
URL. Any replacement in POI would need to allow similar retention of unknown
XML elements and content.  This completely breaks systems like JAXB, which
needs all possible namespaces and how they fit together to be defined up front.
 There is no dynamic model building or class loading.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #25 from PJ Fanning <[hidden email]> ---
I found some other projects based on POI, that have some usage of spreadsheetml
classes. I raised issues in these projects.
https://github.com/norbert-radyk/spoiwo/issues/28
https://github.com/monitorjbl/excel-streaming-reader/issues/125

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #26 from Dominik Stadler <[hidden email]> ---
*** Bug 61921 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

PJ Fanning <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |61949


Referenced Bugs:

https://bz.apache.org/bugzilla/show_bug.cgi?id=61949
[Bug 61949] XSSFTable should support create/update functions
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

Dominik Stadler <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #27 from Dominik Stadler <[hidden email]> ---
*** Bug 61988 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

PJ Fanning <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #28 from PJ Fanning <[hidden email]> ---
*** Bug 62004 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #29 from Scott Coldwell <[hidden email]> ---
I'm happy to help with the actual conversion when it comes time for that.  My
company just went through a pretty large xmlbeans -> JAXB conversion involving
many 3rd party schemas in various states of schema authoring best practices.
It's really not that bad once you get the classes compiled properly and we've
been through a bunch of the gotchas with making that happen.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #30 from Andreas Beeker <[hidden email]> ---
I have some ideas of how JAXB could be integrated into POI, but currently even
the basics don't work.

If you want to have something to get started with, you could try to solve [1]

This would be only one technical POC. We would need to support also older ECMA
versions, which are not downward compatible.

I thought about having only the xml fragment attached to the usermodel and
parse it on the fly and use the jaxb binder to preserve the xml infoset.

The current issue is about a new xmlbeans version - so we should discuss a JAXB
related solution in a different bugzilla entry.


[1] https://stackoverflow.com/questions/46869482

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 59268] Work on providing an updated version of XMLBeans

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=59268

--- Comment #31 from Andreas Beeker <[hidden email]> ---
Applied PJ Fannings pull request [1] via r1834165
[1] https://github.com/apache/poi/pull/113

Leaving it open until XmlBeans 3.0.0 is released

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

123