Issues

Select view

Select search mode

 
33 of 33

autostarting plug-ins causes a lot of errors if 2Pack/AdempiereActivator is used

Fixed

Description

I have a plug-in with a 2Pack. I want it to autostart with the swing client. If i set the start level to 6 or below, i get a bunch of errors caused by the activator. It seems that the pipo plug-ins are not ready at this time.
If i set the starting level to 7 or higher, the plug-in is never activated (even if i check the "activate this plug-in when one of its classes is loaded")

Carlos met the same problem. We would really appreciate a working solution.

Environment

None

Details

Assignee

Reporter

Components

Affects versions

Priority

Created March 13, 2013 at 10:17 PM
Updated December 27, 2013 at 2:53 PM
Resolved March 21, 2013 at 12:57 PM

Activity

Show:

Angel ParraJune 21, 2013 at 8:59 PM

Thanks Carlos Ruiz, i created issue ticket https://idempiere.atlassian.net/browse/IDEMPIERE-1092.

If i can correct the problem publishes the corresponding patch.

Carlos RuizJune 20, 2013 at 8:47 PM

Angel, thanks for reporting, please open a new ticket just for swing.

Regards,

Carlos Ruiz

Angel ParraJune 20, 2013 at 8:29 PM

This issue has not been resolved yet, still gives me the same error described.

I Perform a test case creating a new plugin and adding a package 2Pack.zip, starting the plugin using version Idempiere swing, the method addingservice of AdempiereActivator class does not start, it is the method used to start the service plugin and perform the 2Pack.zip packin.

This method addingservice only starts in the web version, in the swing version does not start and does not make the plugin Packin.

Jan ThielemannApril 18, 2013 at 2:38 PM

Closed because its fixed

Jan ThielemannMarch 21, 2013 at 12:57 PM

For our cases it seems to work now.