You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andor E <ey...@googlemail.com> on 2012/05/14 15:35:18 UTC
AO 3.4: Java Extension and HeadlessException
Hi,
I have just started to test AO 3.4 with our extension (WollMux) and ran
into trouble right at the start. One part of our software is an external
Swing GUI that connects to OOo/AO via bootstrapping. When this program
tries to instantiate its main form, it throws a java.awt.HeadlessException.
It's also supposed to launch an invisible Writer document. The launching
works, but the window is visible.
Needless to say, this works with OOo 3.2.1/3.3.
Has anything changed in the way JAVA is launched or in the bootstrapping
mechanism? I couldn't find anything on this in the release notes. Also is
there any documentation on changes in the API?
Greetings
eymux
Re: AO 3.4: Java Extension and HeadlessException
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Andor,
On Wed, May 16, 2012 at 03:41:08PM +0000, Andor E wrote:
> I'm not sure, how this can be a bug in my code.
I don't mean a bug *in* your code, I mean a bug *with* your Java
application in the environment you are testing it.
> The very same code runs fine with OOo 3.2.1 and OOo 3.3.
Did you test this in the very same machine you're seeing this bug?
> What stymies me, is, why the JRE seems to run headless.
And that's why I say a bug with your Java application in your
environment. In my environment, your extension can be installed and it
runs, and your Java application also works.
Your backtrace is pretty clear:
de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
you hit the bug in your Java application when you try to instantiate the
Swing JFrame, IMHO it has nothing to do with Apache OpenOffice, your
application is running in other process with its own JVM, etc. And
bootstrapping the office should have no influence at all...
>
> The WollMux quickstarter is completely distinct from the AOO
> quickstarter. It tries to keep the soffice process alive. I will make
> another test with both quickstarters disabled.
If nothing works, I'd suggest as in my previous mail, and test with
another JVM/jdk.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: AO 3.4: Java Extension and HeadlessException
Posted by Andor E <ey...@googlemail.com>.
I'm not sure, how this can be a bug in my code. The very same code
runs fine with OOo 3.2.1 and OOo 3.3. What stymies me, is, why the JRE
seems to run headless.
The WollMux quickstarter is completely distinct from the AOO
quickstarter. It tries to keep the soffice process alive. I will make
another test with both quickstarters disabled.
On 5/16/12, Ariel Constenla-Haile <ar...@apache.org> wrote:
> Hi Andor,
>
> On Tue, May 15, 2012 at 09:54:47AM +0000, Andor E wrote:
>> Hi,
>> thanks for the responses.
>>
>> My tests have been done on Kubuntu 10.04, because it comes closest to
>> our production environment.
>>
>> And here is a stacktrace:
>>
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.HeadlessException
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.Window.<init>(Window.java:437)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.Frame.<init>(Frame.java:419)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> javax.swing.JFrame.<init>(JFrame.java:218)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.access$500(WollMuxBar.java:156)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar$5.run(WollMuxBar.java:446)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventQueue.access$000(EventQueue.java:96)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventQueue$1.run(EventQueue.java:608)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventQueue$1.run(EventQueue.java:606)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.security.AccessController.doPrivileged(Native Method)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
>> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
>>
>> Steps to reproduce:
>> * Install WollMux.oxt
>> * Install wollmux-config
>> * lauchch ./wollmuxbar
>> (Please refer to www.wollmux.org for installation instructions and
>> downloads.)
>>
>> I'm not using Tomcat or any API connected with Tomcat.
>>
>> I hope this answers all questions.
>> The bug is very reproducable and I'm pretty sure that I've installed
>> my extension correctly.
>
> I cannot reproduce it, and I'm also sure I installed the extension
> correctly, it is working.
>
> Your project is made up of two pieces:
>
> - an AOO extension, works inside AOO
> - a Java application, that bootstraps AOO, that is a client application
>
> Looking at the backtrace:
>
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.HeadlessException
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.Window.<init>(Window.java:437)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.Frame.<init>(Frame.java:419)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> javax.swing.JFrame.<init>(JFrame.java:218)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
>
>
> - the bug is in the Java application, not in the extension
> - the bug seems unrelated to AOO: it looks like your application is able
> to connect to AOO, reading the backtrace and looking at your sources
> it seems the java.awt.HeadlessException is triggered by the following
> code
>
> eventHandler.connectWithWollMux();
> createGUI(conf);
>
> Did you debug the code? Is the exception thrown after bootstrapping AOO?
> Can you bootstrap the office?
>
> IMO this is unrelated to AOO, and it looks more like a bug on your Java
> application. Did you try to reproduce this on other machine? Which
> JRE/jdk are you using? Did you test in the same machine, with other
> JRE/jdk (for example, if you're using the OpenJDK, then try with the
> one from Oracle)?
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>
Re: AO 3.4: Java Extension and HeadlessException
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Andor,
On Tue, May 15, 2012 at 09:54:47AM +0000, Andor E wrote:
> Hi,
> thanks for the responses.
>
> My tests have been done on Kubuntu 10.04, because it comes closest to
> our production environment.
>
> And here is a stacktrace:
>
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.HeadlessException
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.Window.<init>(Window.java:437)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.Frame.<init>(Frame.java:419)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> javax.swing.JFrame.<init>(JFrame.java:218)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.access$500(WollMuxBar.java:156)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar$5.run(WollMuxBar.java:446)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventQueue.access$000(EventQueue.java:96)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventQueue$1.run(EventQueue.java:608)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventQueue$1.run(EventQueue.java:606)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.security.AccessController.doPrivileged(Native Method)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
>
> Steps to reproduce:
> * Install WollMux.oxt
> * Install wollmux-config
> * lauchch ./wollmuxbar
> (Please refer to www.wollmux.org for installation instructions and downloads.)
>
> I'm not using Tomcat or any API connected with Tomcat.
>
> I hope this answers all questions.
> The bug is very reproducable and I'm pretty sure that I've installed
> my extension correctly.
I cannot reproduce it, and I'm also sure I installed the extension
correctly, it is working.
Your project is made up of two pieces:
- an AOO extension, works inside AOO
- a Java application, that bootstraps AOO, that is a client application
Looking at the backtrace:
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.HeadlessException
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173)
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.Window.<init>(Window.java:437)
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.Frame.<init>(Frame.java:419)
2012-05-14 14:08:25 ERROR(WollMuxBar:450): javax.swing.JFrame.<init>(JFrame.java:218)
2012-05-14 14:08:25 ERROR(WollMuxBar:450): de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
- the bug is in the Java application, not in the extension
- the bug seems unrelated to AOO: it looks like your application is able
to connect to AOO, reading the backtrace and looking at your sources
it seems the java.awt.HeadlessException is triggered by the following
code
eventHandler.connectWithWollMux();
createGUI(conf);
Did you debug the code? Is the exception thrown after bootstrapping AOO?
Can you bootstrap the office?
IMO this is unrelated to AOO, and it looks more like a bug on your Java
application. Did you try to reproduce this on other machine? Which
JRE/jdk are you using? Did you test in the same machine, with other
JRE/jdk (for example, if you're using the OpenJDK, then try with the
one from Oracle)?
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: AO 3.4: Java Extension and HeadlessException
Posted by Joost Andrae <Jo...@gmx.de>.
Hi,
I'm not sure but perhaps it's an issue related to the QuickStarter
mechanism because the source code within WollMux want's to access this?
Perhaps buxfix
https://svn.apache.org/viewvc?view=revision&revision=1338503 is related
to this issue? What does line 450 in
../wollmux-11.10a-developer/wollmux-11.10a/WollMux/src/de/muenchen/allg/itd51/wollmux/dialog/WollMuxBar.java
look like within your local source repository?
For me it looks like this part of WollMuxBar.java creates the WollmuxBar
and it uses a boolean "true" value to configure it as OOo Quickstarter
instead of the original one.
> 2012-05-14 14:08:25 ERROR(WollMuxBar:450):
> java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
Kind regards, Joost
Re: AO 3.4: Java Extension and HeadlessException
Posted by Andor E <ey...@googlemail.com>.
Hi,
thanks for the responses.
My tests have been done on Kubuntu 10.04, because it comes closest to
our production environment.
And here is a stacktrace:
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.HeadlessException
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.Window.<init>(Window.java:437)
2012-05-14 14:08:25 ERROR(WollMuxBar:450): java.awt.Frame.<init>(Frame.java:419)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
javax.swing.JFrame.<init>(JFrame.java:218)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.createGUI(WollMuxBar.java:480)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar.access$500(WollMuxBar.java:156)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
de.muenchen.allg.itd51.wollmux.dialog.WollMuxBar$5.run(WollMuxBar.java:446)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventQueue.access$000(EventQueue.java:96)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventQueue$1.run(EventQueue.java:608)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventQueue$1.run(EventQueue.java:606)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.security.AccessController.doPrivileged(Native Method)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
2012-05-14 14:08:25 ERROR(WollMuxBar:450):
java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
Steps to reproduce:
* Install WollMux.oxt
* Install wollmux-config
* lauchch ./wollmuxbar
(Please refer to www.wollmux.org for installation instructions and downloads.)
I'm not using Tomcat or any API connected with Tomcat.
I hope this answers all questions.
The bug is very reproducable and I'm pretty sure that I've installed
my extension correctly.
Greetings
Andor Ertsey
On 5/15/12, Ariel Constenla-Haile <ar...@apache.org> wrote:
> Hello Andor,
>
> On Mon, May 14, 2012 at 03:35:18PM +0200, Andor E wrote:
>> Hi,
>> I have just started to test AO 3.4 with our extension (WollMux) and ran
>> into trouble right at the start. One part of our software is an external
>> Swing GUI that connects to OOo/AO via bootstrapping. When this program
>> tries to instantiate its main form, it throws a
>> java.awt.HeadlessException.
>> It's also supposed to launch an invisible Writer document. The launching
>> works, but the window is visible.
>> Needless to say, this works with OOo 3.2.1/3.3.
>>
>> Has anything changed in the way JAVA is launched or in the bootstrapping
>> mechanism? I couldn't find anything on this in the release notes. Also is
>> there any documentation on changes in the API?
>
>
> I downloaded your extension and it seems to work on Linux (Fedora 16, 64
> bits): http://people.apache.org/~arielch/images/wollmux.png
> The only issue I've found is
> https://issues.apache.org/ooo/show_bug.cgi?id=119102
>
> Could you please enumerate the steps to reproduce the HeadlessException
> exception? I started the test by running ./wollmuxbar
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>
Re: AO 3.4: Java Extension and HeadlessException
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hello Andor,
On Mon, May 14, 2012 at 03:35:18PM +0200, Andor E wrote:
> Hi,
> I have just started to test AO 3.4 with our extension (WollMux) and ran
> into trouble right at the start. One part of our software is an external
> Swing GUI that connects to OOo/AO via bootstrapping. When this program
> tries to instantiate its main form, it throws a java.awt.HeadlessException.
> It's also supposed to launch an invisible Writer document. The launching
> works, but the window is visible.
> Needless to say, this works with OOo 3.2.1/3.3.
>
> Has anything changed in the way JAVA is launched or in the bootstrapping
> mechanism? I couldn't find anything on this in the release notes. Also is
> there any documentation on changes in the API?
I downloaded your extension and it seems to work on Linux (Fedora 16, 64
bits): http://people.apache.org/~arielch/images/wollmux.png
The only issue I've found is https://issues.apache.org/ooo/show_bug.cgi?id=119102
Could you please enumerate the steps to reproduce the HeadlessException
exception? I started the test by running ./wollmuxbar
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: AO 3.4: Java Extension and HeadlessException
Posted by Pedro Giffuni <pf...@apache.org>.
On 05/15/12 07:23, Roberto Resoli wrote:
> 2012/5/15 Pedro Giffuni<pf...@apache.org>:
>> Hello,
> ...
>>> what is used of Tomcat for inside AOO? Do you mean the
>>> entire Tomcat API or
>>> the Servlet part only? I tried to find some info about
>>> this, having
>>> found Tomcat update
>>> notice inside AOO 3.4 release notes. Cold you point me to
>>> some documentation?
>>>
>> We only use the servlet API and its used for Apache Commons
>> so its basically an extensions-only thing.
> so, I guess, the presence of the servlet API in AOO
> is only there as a dependancy of Apache Commons, and "Tomcat"
> is the particular implementation chosen of the servlet specification
> (version 2.4, for tomcat 5.5.35 [1]).
> Do you think this might be worthwhile a rewording in the Release Notes?
The change is meant to be transparent. I don't think it's worth to
detail much more about it.
Pedro.
Re: AO 3.4: Java Extension and HeadlessException
Posted by Roberto Resoli <ro...@gmail.com>.
2012/5/15 Pedro Giffuni <pf...@apache.org>:
> Hello,
...
>> what is used of Tomcat for inside AOO? Do you mean the
>> entire Tomcat API or
>> the Servlet part only? I tried to find some info about
>> this, having
>> found Tomcat update
>> notice inside AOO 3.4 release notes. Cold you point me to
>> some documentation?
>>
>
> We only use the servlet API and its used for Apache Commons
> so its basically an extensions-only thing.
so, I guess, the presence of the servlet API in AOO
is only there as a dependancy of Apache Commons, and "Tomcat"
is the particular implementation chosen of the servlet specification
(version 2.4, for tomcat 5.5.35 [1]).
Do you think this might be worthwhile a rewording in the Release Notes?
> I think Andors problem is unrelated though.
I am with you, Headless Exception is thrown where the JVM cannot find
the native GUI peer needed by a GUI application.
In server side applications a solution is to run in "Headless Mode",
setting the System property "java.awt.headless" to "True",
both programmatically or from command line [2].
I dont'know if this holds also when the runtime is invoked inside AOO.
bye,
rob
[1] https://tomcat.apache.org/whichversion.html
[2] http://java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/
rob
> Pedro.
>
Re: AO 3.4: Java Extension and HeadlessException
Posted by Pedro Giffuni <pf...@apache.org>.
Hello,
--- Mar 15/5/12, Roberto Resoli <ro...@gmail.com> ha scritto:
...
> 2012/5/14 Pedro Giffuni <pf...@apache.org>:
> > Hello Andor;
>
> Hello Andor, Pedro
>
> > --- Lun 14/5/12, Andor E <ey...@googlemail.com>
> ha scritto:
> > ...
> >> Data: Lunedì 14 maggio 2012, 08:35
> >> Hi,
> >> I have just started to test AO 3.4 with our
> extension
> >> (WollMux) and ran into trouble right at the start.
> One
> >> part of our software is an external Swing GUI that
> >> connects to OOo/AO via bootstrapping. When this
> program
> >> tries to instantiate its main form, it throws a
> >> java.awt.HeadlessException.
>
> may you post a stacktrace ?
>
> >> It's also supposed to launch an invisible Writer
> document.
> >> The launching works, but the window is visible.
> >> Needless to say, this works with OOo 3.2.1/3.3.
> >>
> >
> > Just wondering ... perhaps you are using the servlet
> API?
> >
> > We did update Apache Tomcat:
> > http://tomcat.apache.org/tomcat-5.5-doc/index.html
>
> what is used of Tomcat for inside AOO? Do you mean the
> entire Tomcat API or
> the Servlet part only? I tried to find some info about
> this, having
> found Tomcat update
> notice inside AOO 3.4 release notes. Cold you point me to
> some documentation?
>
We only use the servlet API and its used for Apache Commons
so its basically an extensions-only thing.
I think Andors problem is unrelated though.
Pedro.
Re: AO 3.4: Java Extension and HeadlessException
Posted by Roberto Resoli <ro...@gmail.com>.
2012/5/14 Pedro Giffuni <pf...@apache.org>:
> Hello Andor;
Hello Andor, Pedro
> --- Lun 14/5/12, Andor E <ey...@googlemail.com> ha scritto:
> ...
>> Data: Lunedì 14 maggio 2012, 08:35
>> Hi,
>> I have just started to test AO 3.4 with our extension
>> (WollMux) and ran into trouble right at the start. One
>> part of our software is an external Swing GUI that
>> connects to OOo/AO via bootstrapping. When this program
>> tries to instantiate its main form, it throws a
>> java.awt.HeadlessException.
may you post a stacktrace ?
>> It's also supposed to launch an invisible Writer document.
>> The launching works, but the window is visible.
>> Needless to say, this works with OOo 3.2.1/3.3.
>>
>
> Just wondering ... perhaps you are using the servlet API?
>
> We did update Apache Tomcat:
> http://tomcat.apache.org/tomcat-5.5-doc/index.html
what is used of Tomcat for inside AOO? Do you mean the entire Tomcat API or
the Servlet part only? I tried to find some info about this, having
found Tomcat update
notice inside AOO 3.4 release notes. Cold you point me to some documentation?
Many thanks,
Roberto Resoli
> best regards,
>
> Pedro.
Re: AO 3.4: Java Extension and HeadlessException
Posted by Pedro Giffuni <pf...@apache.org>.
Hello Andor;
--- Lun 14/5/12, Andor E <ey...@googlemail.com> ha scritto:
...
> Data: Lunedì 14 maggio 2012, 08:35
> Hi,
> I have just started to test AO 3.4 with our extension
> (WollMux) and ran into trouble right at the start. One
> part of our software is an external Swing GUI that
> connects to OOo/AO via bootstrapping. When this program
> tries to instantiate its main form, it throws a
> java.awt.HeadlessException.
> It's also supposed to launch an invisible Writer document.
> The launching works, but the window is visible.
> Needless to say, this works with OOo 3.2.1/3.3.
>
Just wondering ... perhaps you are using the servlet API?
We did update Apache Tomcat:
http://tomcat.apache.org/tomcat-5.5-doc/index.html
best regards,
Pedro.