Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 113888 - Migration of Woodstock Themes - detect if custom themes used
Migration of Woodstock Themes - detect if custom themes used
Product: obsolete
Classification: Unclassified
Component: visualweb
Other All
: P3 (vote)
: 6.x
Assigned To: Winston Prakash
Depends on:
  Show dependency treegraph
Reported: 2007-08-27 18:56 UTC by _ krystyna
Modified: 2008-12-10 19:24 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description _ krystyna 2007-08-27 18:56:29 UTC
Woodstock themes were found to be incompatible migrating 5.0 -> 5.1
and we face the same issue if any custom Woodstock theme is
migrated from 5.1 -> 6.0. 

We should prevent the user from receiving a Missing Body Element error
on migration. 

Winston has proposed detecting the custom theme on migration and making 
a switch to the default Woodstock theme.
Comment 1 Winston Prakash 2007-08-27 20:53:54 UTC
The proposed solution

- Get the project version and check if it is 5.1 project
- Get the theme name from project
   String themeName = JsfProjectUtils.getProjectProperty(project, JsfProjectConstants.PROP_CURRENT_THEME);
   if (!themeName.equals("theme-default"){
      // Replace the theme to default theme      
      // Display a warning message giving appropriate information     
Comment 2 Winston Prakash 2007-09-06 22:52:44 UTC
Hi Po-ting, is there a way to accomplish the steps while opening the project.
Comment 3 _ potingwu 2007-09-06 23:08:15 UTC
Do you mean you want to do some modification after opening a visualweb project? If so, looks into:

you can either copy the codes to your module, or insert your actions into the following loop:
  for (Project project : jsfProjectsSet) {

Comment 4 _ krystyna 2007-09-10 17:51:22 UTC
This should be release noted for Beta1 that users should manually switch to the default theme
before migrating.
Comment 5 Winston Prakash 2007-09-20 15:37:37 UTC
As we decided during Viusalweb i-team bug status council, 
downngrading this bug to p2.

- Release note issue, so that user can switch to default theme.
- Since user may not know why "No body found" error,
  we should post a dialog if a legacy Java EE 5 project is opened
  and it has custom theme.  
Comment 6 Winston Prakash 2007-10-18 02:18:33 UTC
We don't have proper support from Theme Context for this now.
So marking this for future release
Comment 7 _ krystyna 2007-10-18 23:39:48 UTC
(When did this become a P3?)

If nothing can be done, Migration docs / release notes should suggest the
user not attempt to resolve the missing reference of the theme library
but instead should remove the reference via Project Properties. They
should remove the reference from the Libraries and the Build/Packaging.
They will still receive a red Source File Error because no theme will be
set by default. They need to explicitly then select the project Themes
node and set Web UI Default Theme.
Comment 8 Peter Zavadsky 2008-12-10 19:24:28 UTC
No current plan to resolve it. Moving to 'later'.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo