[dev] unopkg fails

2006-06-06 Thread Tobias Krais
Hi together,

please tell me whether there is an other bug in OOo.

My problem: I want to register a little UNO package at OOo, using
unopkg. It does not matter which Java compiler I use for compiling my
package. If I want to register my ready built package I can't use the
Free Software Foundation 1.4.2 Java (all others I tested will work). If
I use the FSF 1.4.2 Java and try to enable my UNO Package using the
command "/usr/lib/openoffice/program/unopkg gui" I get following error:
-%<-
(com.sun.star.lang.DisposedException) { { { Message = "URP_Bridge :
disposed\X000a(tid=8) Unexpected connection closure", Context =
(com.sun.star.XInterface) 0x0 } } }
-%<-

Can you tell me whether this is a OOo Bug or not?

I attached the pkg-file for it is very small. I hope this is OK.

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] unopkg fails

2006-06-07 Thread Jürgen Schmidt

Hi Tobias,

Tobias Krais wrote:

Hi together,

please tell me whether there is an other bug in OOo.

My problem: I want to register a little UNO package at OOo, using
unopkg. It does not matter which Java compiler I use for compiling my
package. If I want to register my ready built package I can't use the
Free Software Foundation 1.4.2 Java (all others I tested will work). If
I use the FSF 1.4.2 Java and try to enable my UNO Package using the
command "/usr/lib/openoffice/program/unopkg gui" I get following error:
-%<-
(com.sun.star.lang.DisposedException) { { { Message = "URP_Bridge :
disposed\X000a(tid=8) Unexpected connection closure", Context =
(com.sun.star.XInterface) 0x0 } } }
-%<-

Can you tell me whether this is a OOo Bug or not?


can you be more concrete ...
- which Java version was used to compile your package
- which other Java versions did have tested

Juergen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] unopkg fails

2006-06-07 Thread Tobias Krais

Hi Jürgen,


My problem: I want to register a little UNO package at OOo, using
unopkg. It does not matter which Java compiler I use for compiling my
package. If I want to register my ready built package I can't use the
Free Software Foundation 1.4.2 Java (all others I tested will work). If
I use the FSF 1.4.2 Java and try to enable my UNO Package using the
command "/usr/lib/openoffice/program/unopkg gui" I get following error:


[...]


can you be more concrete ...
- which Java version was used to compile your package

> - which other Java versions did have tested

I used Sun Java 1.5.0_06 from Debian Sid non-free for compiling. It 
doesn't matter which -source and -target flags I used (tried it with 
1.1, 1.2, 1.3, 1.4). I also used the Blackdown Java 1.4.2.03-1 and the 
FSF GCJ 1.4.2.


I tested _every_ combination of these JDKs that means I e.g. compiled it 
with Sun Java while OOo used Sun Java -> it works; I tried compiling 
with each of these Javas, but only the FSF GCJ Java did not succeed with 
adding the UNO package.


Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] unopkg fails

2006-06-07 Thread Jürgen Schmidt

Tobias Krais wrote:

Hi Jürgen,


My problem: I want to register a little UNO package at OOo, using
unopkg. It does not matter which Java compiler I use for compiling my
package. If I want to register my ready built package I can't use the
Free Software Foundation 1.4.2 Java (all others I tested will work). If
I use the FSF 1.4.2 Java and try to enable my UNO Package using the
command "/usr/lib/openoffice/program/unopkg gui" I get following error:


[...]


can you be more concrete ...
- which Java version was used to compile your package

 > - which other Java versions did have tested

I used Sun Java 1.5.0_06 from Debian Sid non-free for compiling. It 
doesn't matter which -source and -target flags I used (tried it with 
1.1, 1.2, 1.3, 1.4). I also used the Blackdown Java 1.4.2.03-1 and the 
FSF GCJ 1.4.2.


I tested _every_ combination of these JDKs that means I e.g. compiled it 
with Sun Java while OOo used Sun Java -> it works; I tried compiling 
with each of these Javas, but only the FSF GCJ Java did not succeed with 
adding the UNO package.


mmh, it's obviously that you have to use Java 1.5 in the office when you 
compile your component with Java 1.5. For all combinations where you use 
1.5 for compiling and a smaller version in the office i would expect 
that it won't work because the incompatible class file format in Java 
1.5. I personally use only Sun Java packages ;-) and can't say anything 
about the FSF GCJ but i will give it a try when i find some time to test it.


Juergen




Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] unopkg fails

2006-06-08 Thread Tobias Krais
Moin Jürgen,

[...]

>> I used Sun Java 1.5.0_06 from Debian Sid non-free for compiling. It
>> doesn't matter which -source and -target flags I used (tried it with
>> 1.1, 1.2, 1.3, 1.4). I also used the Blackdown Java 1.4.2.03-1 and the
>> FSF GCJ 1.4.2.
>>
>> I tested _every_ combination of these JDKs that means I e.g. compiled
>> it with Sun Java while OOo used Sun Java -> it works; I tried
>> compiling with each of these Javas, but only the FSF GCJ Java did not
>> succeed with adding the UNO package.
> 
> mmh, it's obviously that you have to use Java 1.5 in the office when you
> compile your component with Java 1.5. For all combinations where you use
> 1.5 for compiling and a smaller version in the office i would expect
> that it won't work because the incompatible class file format in Java
> 1.5.

Not in case I compile with options -source 1.4 -target 1.4

> I personally use only Sun Java packages ;-) and can't say anything
> about the FSF GCJ but i will give it a try when i find some time to test
> it.

Hmm. You mail header tells me that you are using Windows. This is not
really a problem in Windows, because Windows OOo comes with a Java 1.5.
This is only a problem with Debian Linux, where OOo comes with the FSF
Java... and I can't change the Java via commandline.

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] unopkg fails

2006-06-08 Thread Jürgen Schmidt

Tobias Krais wrote:

Moin Jürgen,

[...]


I used Sun Java 1.5.0_06 from Debian Sid non-free for compiling. It
doesn't matter which -source and -target flags I used (tried it with
1.1, 1.2, 1.3, 1.4). I also used the Blackdown Java 1.4.2.03-1 and the
FSF GCJ 1.4.2.

I tested _every_ combination of these JDKs that means I e.g. compiled
it with Sun Java while OOo used Sun Java -> it works; I tried
compiling with each of these Javas, but only the FSF GCJ Java did not
succeed with adding the UNO package.

mmh, it's obviously that you have to use Java 1.5 in the office when you
compile your component with Java 1.5. For all combinations where you use
1.5 for compiling and a smaller version in the office i would expect
that it won't work because the incompatible class file format in Java
1.5.


Not in case I compile with options -source 1.4 -target 1.4

ok, you mentioned it before




I personally use only Sun Java packages ;-) and can't say anything
about the FSF GCJ but i will give it a try when i find some time to test
it.


Hmm. You mail header tells me that you are using Windows. This is not
really a problem in Windows, because Windows OOo comes with a Java 1.5.
This is only a problem with Debian Linux, where OOo comes with the FSF
Java... and I can't change the Java via commandline.


sure, i understand you. I read currently my Mail under windows but i 
work on Windows, Linux and Solaris ;-)


But nevertheless we have to check this.
When you compile your package with FSF GCJ Java and use for example sun 
Java 1.4.2 in the office, does it work? Maybe there is a general problem 
with the FSF GCJ.


Juergen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]