• Decrease font size
  • Reset font size to default
  • Increase font size
Merapi Forums
Welcome, Guest
Please Login or Register.    Lost Password?
Re:I've not test for now, but I've read documentat (1 viewing) (1) Guest
Go to bottom Post Reply Favoured: 0
TOPIC: Re:I've not test for now, but I've read documentat
#16
Tizisa (User)
Posts: 12
graphgraph
User Offline Click here to see the profile of this user
I've not test for now, but I've read documentation 9 Months, 1 Week ago Karma: 0  
I've not test for now, but I've read documentation, and I think there the same Artemis problem. In fact I'm able to call an instance, but I'm not able to stop it. In this way java socket stay opened....
 
Logged Logged  
  The administrator has disabled public write access.
#17
adam (Admin)
Admin
Posts: 23
graph
User Offline Click here to see the profile of this user
Re:I've not test for now, but I've read documentat 9 Months, 1 Week ago Karma: 0  
This is true. The socket is left open as a development convenience. In the next release we'll make this configurable so that when the AIR app exits the Java app exits as well.
 
Logged Logged  
  The administrator has disabled public write access.
#290
mduchene (User)
Admin
Posts: 1
graphgraph
User Offline Click here to see the profile of this user
Re:I've not test for now, but I've read documentat 1 Week, 3 Days ago Karma: 0  
Hi,
I don't see why "the AIR app exits the Java app exits as well" ?
I all depends on the kind of application to create. Sometimes it is quite nice to have java stoped, but some others the java application should keep running to continue its work like a service.
I tried to manually disconnect the front view before closing it, but there is only one method (closeAllMerapiObjects) and it didn't do the job.

Could you please make it possible to have both uses of the bridge?
 
Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop