J-Link and external jar

[magic_halli]

Hi,



i

 

[cmarcum]

Do you know if ContextFactory.init method spawns a new
thread? I think synchronous j-link apps are limited to 1
thread.

Best regards,
Carl

 

[magic_halli]

Do you know if ContextFactory.init method spawns a new

thread? I think synchronous j-link apps are limited to 1

thread.

I dont know exactly, if ContextFaxtory.init spawns a new thread - but i can imagine!

In this case... is it posible to solve my problem?



Is there any reading about Jlink and threads?



Thanks a lot

 

[cmarcum]

On my system Wildfire 3.0 english version has a
jlinkug.pdf user guide. In chapter 4 "J-Link Programming
Considerations" doesn't really say it explicitly, but it
says you can't use javax.swing.JWindow because it starts
a thread.

I found a unknown version manual online at:
http://summer.nchc.org.tw/~proe/ptc_help/html/usascii/proe/j link/jprogconsid.htm#1005128

Best regards,
Carl

 

[diego.peinado]

I've this problem also.


Have to include the full path of your jar library to the CLASSPATH environment variable.


c:\mylibs\foo.jar

 

[magic_halli]

I solved my problem!

I developed for the communication with our ERP-system a separat
java-project. Now i have in ProE one jlink-application... this
application do something in ProE, after that it retrieves the separat
java-project and passes some values to this.

Now the jlink-application is done and the secound java-project is
working now in the background and do something in out ERP-system (based
upon the passed values from Jlink-application). This is the workaround
in my special case!

The main problem were the diffenrent project-compiler-settings i had to
use: jlink-application only use java1.4 and ERP-interface need
java1.6!!!

Thats it... and it works great!



Thanxxx

 

[frage29]

Hi magic_halli,

i have exactly the same problem. One of my applications needs java 1.4, and the other java 6. Until now, I didn