• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Where did I go wrong? (<WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where did I go wrong? (<WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK)


  • Subject: Re: Where did I go wrong? (<WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK)
  • From: Q <email@hidden>
  • Date: Mon, 10 Mar 2008 03:11:14 +1000


On 09/03/2008, at 11:02 PM, Johan Henselmans wrote:

I seem to struggle a little more than usual to get this thingy working.

After finding out that my components were apparenlty in 16 bits UTF, al though the file in SubEthaEdit and TextWrangler said they were UTF-8, I zapped all the gremlins via TextWrangler (Thanks Miguel), but now firing the component gives this error:


com.webobjects.foundation.NSForwardException for
com.webobjects.appserver._private.WODeclarationFormatException: <WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK
at com .webobjects .appserver ._private .WOHTMLWebObjectTag._elementWithDeclaration(WOHTMLWebObjectTag.java: 212)
at com .webobjects .appserver ._private.WOHTMLWebObjectTag.dynamicElement(WOHTMLWebObjectTag.java: 122)
at com .webobjects .appserver ._private .WOHTMLTemplateParser .didParseClosingWebObjectTag(WOHTMLTemplateParser.java:52)
at com .webobjects .appserver ._private.WOHTMLParser.didParseClosingWebObjectTag(WOHTMLParser.java: 183)
at com .webobjects .appserver._private.WOHTMLParser.endOfWebObjectTag(WOHTMLParser.java: 150)
at com .webobjects .appserver._private.WOHTMLParser.parseHTML(WOHTMLParser.java:67)..


etc

I checked the code over and over again, It's all well formed HTML, I can even close the whole file until it's one <html>, when I click on the button in the HTML, WOLips displays the corresponding Element, I looked at the file in Text Wrangler and SubEthaEdit for any hidden characters, replace the woo file with one I am sure that is working (the one from Main.wo), I removed the API file, removed different localizations, cleaned the project several times, close WOLips, closed the Computers, cleaned all the caches.

What is it I am overlooking?


Recent versions of WOLips support managing the encoding type of your component using the encoding type value in the file properties dialog.
Before attempting to edit it you MUST tell eclipse what encoding type your component has if it differs from your workspace's default encoding type. Your .html and .wod files must also be saved using the same encoding type, which should match what is detailed in your .woo file or bad things will happen. That said however, WebObjects has some smarts in the parser to identify UTF-16 files even if your .woo file is set to UTF-8, eclipse on the other hand doesn't.


If you use eclipse to manage your component's encoding type and do not use external editors to modify the files you should never need to worry about encoding types any more than ensuring it has been set correctly in the properties.

It sounds like you have (had?) a component that was saved as UTF-16, so your WOD file should have been also. If that is the case then the easiest solution would probably have been to just tell eclipse about the components actual encoding type rather than mess with the component's contents in an external editor. This should be done by opening the properties of the component bundle in WO Package Explorer and explicitly setting it to UTF-16 BEFORE making ANY changes. If all your components have the same encoding than just change the encoding type property of your components folder or localisation folder and let the components inherit their encoding properties from their parent.

WOLips SHOULD generate a warning when eclipse's idea of the component encoding type and the .woo file do not match, which in your case probably didn't happen as your .woo file appears to have been set to UTF-8 despite being UTF-16. This warning will appear in your problems view. I strongly recommend against using any external editor to try and resolve encoding type problems as eclipse will not be able to validate or properly edit the contents of files it does not know the encoding type of.

If possible, could you send me a copy of the component's .wo folder as it was after it was initially imported but before you started editing it, so I can have a better look at what is going on and how eclipse is interacting with the components encoding. I added the encoding handling code a while ago, but a lot has changed recently in the component validation code.

--
Seeya...Q

Quinton Dolan - email@hidden
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Where did I go wrong? (<WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK) (From: Johan Henselmans <email@hidden>)

  • Prev by Date: Re: I must be missing something...
  • Next by Date: Re: DTJC running on the iPhone
  • Previous by thread: Where did I go wrong? (<WOHTMLTemplateParser> no declaration for dynamic element (or component) named CheckBoxConditionsOK)
  • Next by thread: Re: DTJC running on the iPhone
  • Index(es):
    • Date
    • Thread