This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 129499 - Open-deploy existing project with NB6.1 beta returns: "WEBUITHEME001: No theme name or version specified and no default theme resource available"
Summary: Open-deploy existing project with NB6.1 beta returns: "WEBUITHEME001: No them...
Status: RESOLVED DUPLICATE of bug 129316
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: Sun All
: P1 blocker (vote)
Assignee: Winston Prakash
URL:
Keywords:
Depends on: 129316
Blocks:
  Show dependency tree
 
Reported: 2008-03-07 06:21 UTC by mm
Modified: 2015-12-29 06:53 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Server log (25.51 KB, text/plain)
2008-03-07 17:36 UTC, _ potingwu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mm 2008-03-07 06:21:56 UTC
We have multiple projects running NB6.0.1 version of VisualWeb apps fine. While trying new version of NB6.1beta with one
of existing projects (ear application), got the following in glassfish log:

WEBUITHEME001: No theme name or version specified and no default theme resource available

Googled about this and tried to add:

<context-param>
        <param-name>com.sun.webui.theme.DEFAULT_THEME</param-name>
        <param-value>suntheme</param-value>
</context-param>

to web.xml - no help, still the same error. Any ideas why is that happening ? 

BTW "Project Woodstock Themes" has a child component "Web UI Default Theme" with green triangle attached to it, but
right-click opened menu ("Set as current theme") is inactive.
Comment 1 _ potingwu 2008-03-07 17:35:39 UTC
Yes, I can reproduce it very easily.
1. Create a visualweb project under 6.0.1 and deploy OK
2. Use 6.1 trunk without rebuild, deploy OK
3. Shutdown the server and apply 'Clean and Build', no error
4. Deploy and got an empty page inside the browser

In the server.log, I see many of the following error:
WEBUITHEME001: No theme name or version specified and no default theme resource available.
WebModule[/VW601]No theme name or version specified and no default theme resource available.
com.sun.webui.theme.ThemeConfigurationException: No theme name or version specified and no default theme resource available.

As I check the project libraries setting, all of the needed libraries are there includes the Web UI Default Theme.

Looks like the contents of Theme libraries is not good.
Comment 2 _ potingwu 2008-03-07 17:36:45 UTC
Created attachment 57988 [details]
Server log
Comment 3 _ potingwu 2008-03-07 18:21:53 UTC
I think I found the problem. It is caused by visual web JSF component libraries are not backwards compatible from 6.0.1
to 6.1!

1. When I create a 6.0.1 project, in nbproject/private/private.properties has the following path:
    libs.jsf12-support.classpath.libfile.1=C:\\Program Files\\NetBeans 6.0.1\\visualweb1\\modules\\ext\\jsfcl.jar
    libs.jsf12-support.classpath.libfile.2=C:\\Program Files\\NetBeans 6.0.1\\visualweb1\\modules\\ext\\appbase.jar
    libs.jsf12-support.classpath.libfile.3=C:\\Program Files\\NetBeans 6.0.1\\visualweb1\\modules\\ext\\dataprovider.jar
    libs.jsf12-support.classpath.libfile.4=C:\\Program Files\\NetBeans 6.0.1\\visualweb1\\modules\\ext\\sqlx.jar
    libs.woodstock-components.classpath.libfile.1=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\webui-jsf.jar
    libs.woodstock-components.classpath.libfile.2=C:\\Program Files\\NetBeans 
                                                  6.0.1\\enterprise4\\modules\\ext\\commons-fileupload-1.0.jar
    libs.woodstock-components.classpath.libfile.3=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\json-2.jar
    libs.woodstock-components.classpath.libfile.4=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\prototype-1.5.0.jar
    libs.woodstock-components.classpath.libfile.5=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\dojo-1.0.1.jar
    libs.woodstock-components.classpath.libfile.6=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\jsf-extensions-common-0.1.jar
    libs.woodstock-components.classpath.libfile.7=C:\\Program Files\\NetBeans 
                                                  6.0.1\\visualweb1\\modules\\ext\\jsf-extensions-dynamic-faces-0.1.jar

2. When I use 6.1 to open this project and rebuild by 'Clean and Build', the contents of private.properties for these
JSF libraries do not change. I.e., they are still build by 6.0.1 jar files. Then when deploy, somehow not all of the JSF
component Web UI libraries are compatible and caused the 'Theme not available' error.

3. Then I remove private.properties and build again. I got the following build error because woodstock-components
library has 7 jar files in 6.0.1 but only 5 jar files in 6.1:
    $projdir\nbproject\build-impl.xml:501: Warning: Could not find file 
                                                     $projdir\${libs.woodstock-components.classpath.libfile.7} to copy.

4. Therefore, I remove all lines in build-impl.xml that contain the following instances. Then rebuild OK, and deploy OK!
(a current workaround)
    ${libs.woodstock-components.classpath.libfile.6}
    ${libs.woodstock-components.classpath.libfile.7}

I think there are 2 questions. Should the IDE automatically regenerate the private.properties when the project has been
opened by different IDE? And also regenerate the build-impl.xml as well? I guess these 2 files regeneration are handled
under different IDE strategy!?

I think issue#129316 is related to this one.
Comment 4 _ potingwu 2008-03-07 18:25:03 UTC
To be clear, the workaround is:
1. remove nbproject/private/private.properties
2. remove all lines in nbproject/build-impl.xml that contain the following instances:
    ${libs.woodstock-components.classpath.libfile.6}
    ${libs.woodstock-components.classpath.libfile.7}
Comment 5 mm 2008-03-07 18:44:41 UTC
tried solution suggested by potingwu - still the same problem - as soon as I try to access any VisualWeb page on a
glassfish I get "WEBUITHEME001: No theme name or version specified and no default theme resource available"

/mareks
Comment 6 _ potingwu 2008-03-07 19:22:24 UTC
You need to do the workaround BEFORE opening the project, or even before starting your IDE. Then rebuild by 'Clean and
Build'. Better yet, 'Clean' before the workaround.

Here is what I will do:
1. Open the project, apply 'Clean'
2. Close the IDE, apply the workaround
3. Start the IDE and open the project, apply 'Run'

Comment 7 mm 2008-03-07 19:34:25 UTC
ok, this way i'm able to build and deploy existing project in nb6.1beta

thanks/mareks
Comment 8 David Konecny 2008-03-09 02:11:13 UTC
Without trying to reproduce this it looks like duplicate of issue 129316.
Comment 9 David Konecny 2008-03-10 02:11:19 UTC
Could not reproduce this after fixing issue 129316.

*** This issue has been marked as a duplicate of 129316 ***