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 99063 - Missing Body Element switching to new Woodstock theme
Summary: Missing Body Element switching to new Woodstock theme
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Winston Prakash
: 105422 (view as bug list)
Depends on:
Reported: 2007-03-27 01:21 UTC by _ krystyna
Modified: 2007-07-16 22:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

sample woodstock theme (500.27 KB, application/octet-stream)
2007-03-27 01:23 UTC, _ krystyna

Note You need to log in before you can comment on or make changes to this bug.
Description _ krystyna 2007-03-27 01:21:26 UTC
Netbeans RC1 candidate build - dated 03261315
VWP dated 070321_1


1. Create an EE5 project. Add woodstock theme library via Library
(attaching sample jar)
2. IN project window, switch to this new theme. First we correctly 
   get prompt to "active theme has changed, stop and start ..."
3. Click OK
>Get big red component error "Missing Body Element" .. 
however body element is in Outline, jsp
Can't recover.

Here is exception to log. Deva says the second
informational exception is not the problem.
Assigning to components.

Can add a braveheart theme jar with no issues.

INFORMATIONAL *********** Exception occurred ************ at 4:51 PM on Mar 26,
Annotation: Missing resource from class: java.util.PropertyResourceBundle
Annotation: Key which was not found: jsfx
java.util.MissingResourceException: Can't find resource for bundle java.util.Pro
pertyResourceBundle, key jsfx
        at java.util.ResourceBundle.getObject(
        at java.util.ResourceBundle.getString(
        at com.sun.webui.theme.JarTheme.getPathToJSFile(
        at com.sun.webui.jsf.util.JavaScriptUtilities.renderJavaScriptInclude(Ja
        at com.sun.webui.jsf.util.JavaScriptUtilities.renderJsfxInclude(JavaScri
        at com.sun.webui.jsf.renderkit.html.HeadRenderer.renderAttributes(HeadRe
        at com.sun.webui.jsf.renderkit.html.AbstractRenderer.encodeBegin(Abstrac
        at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.jav
[catch] at com.sun.rave.insync.faces.FacesPageUnit.renderBean(
        at com.sun.rave.insync.faces.FacesPageUnit.renderNode(
        at com.sun.rave.insync.faces.FacesPageUnit.renderBean(
        at com.sun.rave.insync.faces.FacesPageUnit.renderNode(
        at com.sun.rave.insync.faces.FacesPageUnit.renderBean(
        at com.sun.rave.insync.faces.FacesPageUnit.getFacesRenderTree(FacesPageU
        at com.sun.rave.insync.faces.FacesPageUnit.renderHtml(
        at com.sun.rave.insync.models.FacesModel.getHtmlDomFragment(FacesModel.j
        at com.sun.rave.insync.models.FacesModel.findHtmlBody(
        at com.sun.rave.insync.models.FacesModel.getHtmlBody(
        at com.sun.rave.designer.jsf.JsfForm.getHtmlBody(
        at com.sun.rave.designer.WebForm.getHtmlBody(
        at com.sun.rave.designer.WebForm.getHtmlBody(
        at com.sun.rave.designer.DesignerPaneUI.resetPageBox(
        at com.sun.rave.designer.WebForm.modelRefreshed(
        at com.sun.rave.designer.WebForm.access$200(
        at com.sun.rave.designer.WebForm$HtmlDomProviderListener.modelRefreshed(
        at com.sun.rave.designer.jsf.JsfForm.fireModelRefreshed(
        at com.sun.rave.designer.jsf.JsfForm.refreshModel(
        at com.sun.rave.designer.jsf.RefreshServiceImpl.refreshDataObject(Refres
        at com.sun.rave.designer.jsf.RefreshServiceImpl.refreshFolder(RefreshSer
        at com.sun.rave.designer.jsf.RefreshServiceImpl.refreshProject(RefreshSe
        at com.sun.rave.designer.jsf.RefreshServiceImpl.refresh(RefreshServiceIm
        at com.sun.rave.project.jsfproject.ui.RaveThemesFolderNode$SetAsCurrentT
        at javax.swing.AbstractButton.fireActionPerformed(
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
        at javax.swing.DefaultButtonModel.setPressed(
        at javax.swing.AbstractButton.doClick(
        at javax.swing.plaf.basic.BasicMenuItemUI.doClick(
        at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMen
        at java.awt.Component.processMouseEvent(
        at javax.swing.JComponent.processMouseEvent(
        at java.awt.Component.processEvent(
        at java.awt.Container.processEvent(
        at java.awt.Component.dispatchEventImpl(
        at java.awt.Container.dispatchEventImpl(
        at java.awt.Component.dispatchEvent(
        at java.awt.LightweightDispatcher.retargetMouseEvent(
        at java.awt.LightweightDispatcher.processMouseEvent(

        at java.awt.LightweightDispatcher.dispatchEvent(
        at java.awt.Container.dispatchEventImpl(
        at java.awt.Window.dispatchEventImpl(
        at java.awt.Component.dispatchEvent(
        at java.awt.EventQueue.dispatchEvent(
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
        at java.awt.EventDispatchThread.pumpEvents(

        at java.awt.EventDispatchThread.pumpEvents(

[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.mdr.Logger] Invalid element found in attr. collection - removing.
[org.netbeans.javacore] INFORMATIONAL *********** Exception occurred ***********
* at 4:52 PM on Mar 26, 2007
java.lang.Exception: Class not found in index: webapplication64.SessionBean1. Re
        at org.netbeans.modules.javacore.parser.MDRParser.resolveSuperTypes(MDRP
        at org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.j
        at org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.j
        at org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.j
        at org.netbeans.modules.javacore.parser.MDRParser.enterMembers(MDRParser
        at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.directUp
        at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.checkUpT
        at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.updateFr
        at org.netbeans.modules.javacore.ExclusiveMutex.parseIfNeeded(ExclusiveM
        at org.netbeans.modules.javacore.ExclusiveMutex.enter(ExclusiveMutex.jav
        at org.netbeans.mdr.NBMDRepositoryImpl.beginTrans(NBMDRepositoryImpl.jav
        at org.openide.util.RequestProcessor$

        at org.openide.util.RequestProcessor$
Comment 1 _ krystyna 2007-03-27 01:23:11 UTC
Created attachment 39993 [details]
sample woodstock theme
Comment 2 _ krystyna 2007-03-27 18:23:10 UTC
This is a regression from 5.5
Comment 3 Dongmei Cao 2007-03-27 19:37:23 UTC
Actually, I don't know how valid this test is. There are lots of changes in the
theme from woodstock 4.0 to 4.0.2. The woodstock 4.0 theme can not work in
woodstock 4.0.2. If you want to test switching theme feature in VWP 5.5.1, you
need to create a new custom theme based on the woodstock 4.0.2 suntheme.
Comment 4 _ krystyna 2007-03-27 20:15:55 UTC
This is an incompatibility that users who developed a theme
for 5.5 cannot use it in 5.5.1. What are the changes needed to
fix the theme? These will have to be documented.
Comment 5 Jayashri Visvanathan 2007-04-23 18:16:45 UTC
Here is the comment for woodstock team on this issue:
"We have never been able to guarantee that an earlier theme is compatible with 
subsequent release. If we do, we cannot fix lot of bugs. The real answer is
tighten the theme calls to catch exceptions but this is a huge task and was
highlighted in a recent email I sent saying that it was impossible for the
components to run with a theme present. I had tried to see how far I would get
without the theme. After swallowing a dozen or so exceptions I gave up.Any
customizations to a theme must be brought forward with a new release
of the components.Alternatively we could prevent the theme from throwing any
exceptions and just log the failure, but it's not clear if that is appropriate
either. "

Given the above comment, this issue should be tracked under woodstock, not
visualweb. Can you file an issue against woodstock please ?

For now, I am downgrading this because this is turning out to be a docs issue.

Comment 6 Chris Kutler 2007-05-30 22:54:34 UTC
While you are fixing this, maybe you can fix this bad English: "There seems to
be missing body element, which is required to designer to be able to work. You
need to fix the problem in the sources first."    For the first sentence, I
suggest There seems to be a missing body element, which is preventing the Visual
Designer from displaying the page."  As for the second sentence, I can't figure
out what it is trying to tell me. Maybe "You must edit either the Java source
file or the JSP source file, depending on where the error is, to correct the
error."   I can't say for sure if by sources they mean to check both JSP and
Java. Maybe only the JSP file causes this error. As there is no problem with
either my Java source or Java source and I haven't a clue why I am getting this
blasted message.
Comment 7 Winston Prakash 2007-07-12 02:36:53 UTC
I created a custom theme (via style builder) and used that to switching
theme. It works for me.
Comment 8 _ krystyna 2007-07-12 16:59:45 UTC
This is not resolved. This bug points to the migration problem from 5.5 -> 5.5.1: the 
themes are NOT compatible and a 5.5. custom theme needs to be rebuilt with the 5.5.1 structure.
From our Release Notes:

Customized themes from Visual Web Pack 5.5 Java EE5 projects will not work when added to Visual Web Pack 5.5.1.

    Description: Under this circumstance, the Visual Designer reports a "Missing Body Element" error.

    Workaround: The user must recreate customized themes within the IDE's 5.5.1 theme file structure.

Comment 9 Winston Prakash 2007-07-14 00:27:05 UTC
Woodstock bug created.
Comment 10 Winston Prakash 2007-07-16 22:37:05 UTC
*** Issue 105422 has been marked as a duplicate of this issue. ***