[api-dev] Exception, removeJob - unexpected:java.lang.InterruptedException

[Bob Crothers]

Title: Exception, removeJob - unexpected:java.lang.InterruptedException







Hi,


I have Java code that looks like:


 nxOfficeWriterOutputStream out = new nxOfficeWriterOutputStream();

 PropertyValue[] propertyValue = new PropertyValue[1];

 propertyValue[0] = new PropertyValue();

 propertyValue[0].Name = OutputStream;

 propertyValue[0].Value = new com.sun.star.uno.Any(com.sun.star.io.XOutputStream.class,

 out);

 storable.storeToURL(private:stream, propertyValue);


Most of the time this works fine. Sometimes I get the following exception.


com.sun.star.lib.uno.environments.remote.JobQueue.removeJob - unexpected:java.lang.InterruptedException


Does anyone have any ideas why I get the exception and what I should do to handle the exception.


Thanks

Bob Crothers

[api-dev] [EMAIL PROTECTED] TOPIC: Contributing

[Michael Hoennig]

Dear OpenOffice.org community,

This is the 2-weekly announcement of current issues regarding the
OOo API project which I want to hightlight to the community.


*** =
*** Todays Issue: Contributing to the OOo API Project
*** -

The OOo community needs YOUR contribution too.  And we are sure that
you can contribute real value to OOo.  Don't know how?  YOU too can
contribute to the OOo API project by:

- Reviewing the documentation and reporting issues if you find any
- Useing the OOo API and reporting issues if you find any
- Answering the Questions of other Users of the OOo API
- Summarizing answers which were given to questions (CodeSnippets)
- Contributing your larger API examples to our example collection
- Pointing out important articles for the [EMAIL PROTECTED] NEWSLETTER 
- Tracking unanswered questions on this mailing list
- Preparing the next issue of [EMAIL PROTECTED] TOPIC
- Writing Test Cases
- Translating Examples to C++ (NEW!)
- Becoming an Official OOo Contributor

Each idea contains a short description of how you could help in
its respect, one ore more URLs for more information and an estimation
about the efford on the task.


*** =
*** Reviewing the documentation and report issues if you find any
*** -

Besides others, the OOo SDK contains a Developers Guide and a
Reference Guide.  It's not only important for developers who
want to develop applications with OOo to know these well.
There is also always room for improvement in such documents.

Thus, read the documentation:
  - http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html
  - http://api.openoffice.org/docs/common/ref/com/sun/star/module-ix.html

And when you find anything to improve which you think should actually
be improved, report an issue to IssueZilla.

After once being registered with IssueZilla, reporting an issue is
just a matter of minutes.  


*** =
*** Using the OOo API and reporting issues if you find any
*** -

Next you might want to use the OOo API for your own projects.
Nothing is perfect, thus don't hesitate to report problems you
consider worth getting fixed to IssueZilla.

Here you find a description of OOos IssueZilla:
  - http://www.openoffice.org/project_issues.html

After once being registered with IssueZilla, reporting an issue is
just a matter of minutes.  Of course code examples, well stripped 
down to the point, would help us even more.  Thus count about up to
30 minutes for a complex issue. 


*** =
*** Answering the Questions of other Users of the OOo API
*** -

dev@api.openoffice.org is not an official support medium.  But that
does not mean, we do not want questions answers.  The OOo developers
will do their very best to answer questions, but WE NEED YOUR HELP!

The OOo core development team is very small compared to competing
projects.  Thus we cannot answer all questions.  If you know an
answer of somebody elses question, please post it to the list.
If you are not sure, answer anyway, but mention your incertitude.

This way you give the core developers more space to answer the tough
questions, maybe your next tough question.

If you know the answer off hand, it only needs a few minutes to
contribute by answering questions.  But we appreciate it even
more if you have a vague idea and do some research.  


*** =
*** Summarizing answers which were given to questions (CodeSnippets)
*** -

If you asked a question and got a satisfactory answer with a code
example, be so nice and save it for somebody else who might have
the same question in future.  The mail archive can be searched,
but the search features are not good enough, mostly because mails
are not structured enough.  But there is a better way:

Summarize your question and the given answer(s) in an XML format
for CodeSnippets.  You can find more information here:

  - http://api.openoffice.org/SDK/snippets/

To delopy a CodeSnippet, you need about 15 minutes each.  
Don't you think that the answer given to you was worth it?

Please submit the created codesnippet to the mailinglist
dev@api.openoffice.org and it will be integrated into the
snippet-collection on http://codesnippets.services.openoffice.org/ 
by one of the comminity members with CVS commit rights.

As an addon to easily create codesnippets Paolo Mantovani  has