Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Select boxes in new FormAPI
ktaylor1
We have MetaTagger set to use the new FormAPI. Simple text fields can be mapped and work properly.
Text and textarea fields will map to taxonomies and will be populated from EA's BUT they are converted to selects:
2008-04-04 13:52:42,428 WARN com.interwoven.ui.tagui.util.RulesetRepositoryManager - Resetting current item input type of: text to select for backwards compatibility.
#1 The values in the "select" are populated from EAs but are not selected.
#2 In required fields you have to manually select at least one value in order to save.
#3 Selecting only one of multiple values chosen from a taxonomy will not change the total number of values in the EA for that tag. The chages have to be done via the Add/Edit taxonomy popup. Then a value needs to be selected again before saving.
#4 Reopening the tagging screen after saving will show the same results - select boxes with all of the EA values and nothing selected.
How do we get the text or textareas to work and allow a save after populating?
"Real" selects cannot be mapped to taxonomies or simple fields.
this code works and sets up a working select:
Please enter Division/State value
Impacted Areas:
Adding tagEngineConfig="metatagger://MT_Rulefile" throws the following error (the item is in the MT_Rulefile and simple fields can map):
Error: 2008-04-04 13:49:30,148 ERROR com.interwoven.ui.tagui.LaunchNextGenTagUICommand - Exception while merging DCT rules with DCR data, merged DCT=null
2008-04-04 13:49:30,148 ERROR com.interwoven.ui.tagui.LaunchNextGenTagUICommand - Exception while merging DCT rules with DCR data, DCR shell=null
2008-04-04 13:49:30,149 ERROR com.interwoven.ui.tagui.LaunchNextGenTagUICommand - Exception while merging DCT rules with DCR data, merged
DCR=null 2008-04-04 13:49:30,149 ERROR com.interwoven.ui.tagui.LaunchNextGenTagUICommand - LaunchNextGenTagUICommand caught DCTMergeManagerException while merging datacapture.cfg from: /iwmnt/default/main/employer/WORKAREA/Content/templatedata/employer/DESCRIPTION/data/Atest
com.interwoven.ui.tagui.util.DCTMergeManagerException: java.lang.NullPointerException
at com.interwoven.ui.tagui.util.RulesetRepositoryManager.insertMetaTaggerDecorations(RulesetRepositoryManager.java:518)
at com.interwoven.ui.tagui.util.RulesetRepositoryManager.getRuleset(RulesetRepositoryManager.java:131)
at com.interwoven.ui.tagui.util.DCTMergeManager.getAndResolveRulesets(DCTMergeManager.java:244)
at com.interwoven.ui.tagui.util.DCTMergeManager.processRulesets(DCTMergeManager.java:147)
at com.interwoven.ui.tagui.util.DCTMergeManager.mergeDCT(DCTMergeManager.java:125)
at com.interwoven.ui.tagui.util.DCTMergeManager.mergeDCT(DCTMergeManager.java:93)
at com.interwoven.ui.tagui.LaunchNextGenTagUICommand.buildDCRDocument(LaunchNextGenTagUICommand.java:527)
at com.interwoven.ui.tagui.LaunchNextGenTagUICommand.populateJSPBeanForSingleFile(LaunchNextGenTagUICommand.java:209)
at com.interwoven.ui.tagui.LaunchNextGenTagUICommand.execute(LaunchNextGenTagUICommand.java:155)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommand(CommandHandler.java:419)
at com.interwoven.ui.base.impl.command.CommandCallbackContextImpl.callback(CommandCallbackContextImpl.java:45)
at com.interwoven.ui.base.wizard.WizardCommand.execute(WizardCommand.java:115)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:234)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at com.interwoven.ui.base.impl.command.CommandServlet.doPost(CommandServlet.java:263)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.livesite.spring.hibernate.web.filter.OpenSessionsInViewFilter.doFilterInternal(OpenSessionsInViewFilter.java:141)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:204)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:105)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException ... 48 more ^
Find more posts tagged with
Comments
Migrateduser
One thing to check - there is a known issue with Unicode byte-order-marks in the config files.
As far as the widgets shown, the taxonomy widget overrides the semantics and display of any other widget that it is bound to (radio, select, ....).
I couldn't quite follow the #1-4 description, can you rephrase?
ktaylor1
We have existing content with EAs that were previously set up by selecting values from MetaTagger taxonomies in the old form API. In the old MetaTagger forms the fields were set up as text or textareas.
When we use a text or textarea field in the new FormAPI it automatically resets it to a "select" if it is mapped with a tagEngineConfig. The warning message is "Resetting current item input type of: text to select for backwards compatibility."
This new "select" gets populated with the existing EAs but none of them are selected or highlighted. If the original text field was required the new "select" will not allow a save until an option is selected. If you Edit/Add a new value from the taxonomy you have to highlight a value in the "select" box again before you can save.
If we try to set up a proper select it will throw an error when we map it to the taxonomy that is forcing the issue above.
We need to get a text or textarea to work properly in the new FormAPI. Or get a select to map to a taxonomy.
Migrateduser
Sounds like this needs to be funneled through support. If FormAPI is not required, then you could also flip back to the original TagUI.
ktaylor1
Thanks. We have a ticket open, but these things take time. Had hoped that someone else may have run into a similar issue. Just trying to get this up in dev so we can try to get some validation checks in place through the API.
new_report.rptdesign