[jira] [Created] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
Daniel Kulp created GERONIMO-6509: - Summary: XMLStreamException not calling super(th) in constructors Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Daniel Kulp The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833856#comment-13833856 ] Daniel Kulp commented on GERONIMO-6509: --- FactoryConfigurationError has the same problem XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833867#comment-13833867 ] Guillaume Nodet commented on GERONIMO-6509: --- Sendingsrc/main/java/javax/xml/stream/FactoryConfigurationError.java Transmitting file data . Committed revision 1546068. XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp Assignee: Guillaume Nodet The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned GERONIMO-6509: - Assignee: Guillaume Nodet XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp Assignee: Guillaume Nodet The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833866#comment-13833866 ] Guillaume Nodet commented on GERONIMO-6509: --- Sendingsrc/main/java/javax/xml/stream/XMLStreamException.java Transmitting file data . Committed revision 1546066. XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp Assignee: Guillaume Nodet The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned GERONIMO-6509: - Assignee: Guillaume Nodet XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp Assignee: Guillaume Nodet The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (GERONIMO-6509) XMLStreamException not calling super(th) in constructors
[ https://issues.apache.org/jira/browse/GERONIMO-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved GERONIMO-6509. --- Resolution: Fixed XMLStreamException not calling super(th) in constructors -- Key: GERONIMO-6509 URL: https://issues.apache.org/jira/browse/GERONIMO-6509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Daniel Kulp Assignee: Guillaume Nodet The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable. There are two problems this causes: 1) The cause is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded. 2) For the super(th) one, no message is set at all.Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException(). Any generic exception handling mechanism would not be able to provide a useful error message. -- This message was sent by Atlassian JIRA (v6.1#6144)
[VOTE] Release stax-api-1.2 spec v 1.2
I've uploaded a release at https://repository.apache.org/content/repositories/orgapachegeronimo-014/ to fix the following issue: https://issues.apache.org/jira/browse/GERONIMO-6509 Please review and vote, Cheers, Guillaume
Re: [VOTE] release geronimo-jbatch_1.0-1.0
+1
Thanks guys
2013/11/26 Romain Manni-Bucau rmannibu...@gmail.com
Signature are available here
https://java.net/projects/jbatch/sources/jsr-352-git-repository/show/JSR352.Tests.TCK?rev=6126835af9eb5dedb24825826820d1b7476e78e9
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/11/26 Alan D. Cabrera l...@toolazydogs.com:
+1 looks good
Regards,
Alan
On Nov 25, 2013, at 7:53 AM, Mark Struberg strub...@yahoo.de wrote:
Good evening!
I'd like to call a VOTE on releasing the geronimo jbatch 1.0 API.
The API is already used in Apache BatchEE and passes the JSR-352 JBatch
TCK.
The staging repo is
https://repository.apache.org/content/repositories/orgapachegeronimo-005/
The source release is here
https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/geronimo/specs/geronimo-jbatch_1.0_spec/1.0/geronimo-jbatch_1.0_spec-1.0-source-release.zip
The tag can be found here
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jbatch_1.0_spec-1.0/
[+1] ship it
[+0] meh, don't care
[-1] nope, because ${reason}
Here is my +1
LieGrue,
strub
--
Jean-Louis
