Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.7.1
-
Component/s: Tool Integrations
-
Labels:None
-
Environment:Any suppored by NB (confirmed on Linux and Windows).
-
Workaround Description:For now, the workaround is reinstallation of glassfish server. There might be less drastic way possible, like cleanup of those deployed artifacts (I didn't test it yet).
Description
ICESoft plugins for NB 6.1 create deployment problem (tested on NB 6.5).
It seems the implementation clashes with NB plugins providing Woodstock framework.
The problem is following.
If you deploy to Glassfish (v2) project (web app) with one framework, then consequent deoployed projects with other framework won't work. I.e. it will be deployed, but the pages won't show the components.
The problem occurs this way:
1) If you first (after glassfish installation) deploy project with Woodstock framework... then later deployed projects with ICESoft framework won't work.
2) If you first (after glassfish installation) deploy project with ICESoft framework... then later deployed projects with Woodstock framework won't work.
There seems to be some clash with deployed artifacts. First came to my mind that there are two different implementations of appbase.jar (same classes, packaging but diff implementations)... there might be other potentional culprits, but I didn't investigate it deeper, since I don't have an access to all the relevant code impls.
It seems the implementation clashes with NB plugins providing Woodstock framework.
The problem is following.
If you deploy to Glassfish (v2) project (web app) with one framework, then consequent deoployed projects with other framework won't work. I.e. it will be deployed, but the pages won't show the components.
The problem occurs this way:
1) If you first (after glassfish installation) deploy project with Woodstock framework... then later deployed projects with ICESoft framework won't work.
2) If you first (after glassfish installation) deploy project with ICESoft framework... then later deployed projects with Woodstock framework won't work.
There seems to be some clash with deployed artifacts. First came to my mind that there are two different implementations of appbase.jar (same classes, packaging but diff implementations)... there might be other potentional culprits, but I didn't investigate it deeper, since I don't have an access to all the relevant code impls.
Issue Links
- blocks
-
ICE-4129 Woodstock appbase.jar and ICEfaces wyswyg-appbase.jar
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion