Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | unopkg: Enhance errorhandling for invalid bootstrapping parameters | ||
---|---|---|---|
Product: | General | Reporter: | joerg.skottke |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | 680m222 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
joerg.skottke
2007-08-08 12:01:51 UTC
The variable UserInstallation should be documented somewhere, since the office uses it for quite some time now. I do not know where. The unopkg cannot handle this exception since it does not know the content and the meaning of the bootstrap variables. Only the code which uses the variable can determine the cause of error. The problem this, that it is not possible to transport the initial error unmodified to the user. One reason is that UNO interfaces must declare the allowed exceptions at a method. If now a function throws an exception according to its specification but the calling function cannot handle this exception nor can it throw it (because it does not define that it can throw this exception) then it must throw something other, in which case some information is lost. No image a deep stack of function calls .... In short, there is currently no useful concept of handling these kind of errors. Every now and then someone tries to tackle this ... However, according to JSC there is a new attempt being made. Let's see what comes of it. . Reopen To jsc - according to jl you are working on a solution for this. Can you provide an issue id? Thanks! no i am not working on this. The info was that a group of engineers will discuss a general error handling concept. The whole area is much more complex and can't be easy addressed with one issue. In the concrete issue of the unopkg script the error appears first in javaldx, the next part is the configuration. It is more or less impossible to detect all errors depending on bootstrap variables here. We need an overall concept for errors. The unopkg script is only one place that would benefit from a well defined error handling concept. I send the issue to kr for further comments or opinions related error handling in context of bootstrap variables. jsc -> kr: please comment or better provide a solution No solution insight -> re-targetd to 3.0. Moved target to 3.1 By the way, would be an "IllegalArgumentException", to be throwable by any method, a valid approach? The configuration could throw it after determining that the provided "UserInstallation" directory is invalid. We could precise it with a "BootstrapParameterException" or so ... |