[JBoss JIRA] (JBIDE-10393) Resource bundle varible not getting resolved in xhtml editor
by Vimal Kansal (Created) (JIRA)
Resource bundle varible not getting resolved in xhtml editor
------------------------------------------------------------
Key: JBIDE-10393
URL: https://issues.jboss.org/browse/JBIDE-10393
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Vimal Kansal
Assignee: Alexey Kazakov
I used the maven archetype "jboss-javaee6-webapp-blank-archetype" to create a blank project. I have created a messages.properties file as /src/main/java/com.corejsf/messages.properties. In my faces-config.xml, I have configured :
<application>
<resource-bundle>
<base-name>com.corejsf.messages</base-name>
<var>msgs</var>
</resource-bundle>
</application>
Now, when I create a new .xhtml page and want the auto-completion to automatically resolve an expression like #{msgs. i.e after typing #{msgs. when I press CTRL+SPACE, I don't see the list of properties defined in the resource bundle. However, CTRL+SPACE stuff works if I refer to any CDI bean.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-3191) Cannot run tests when building JMX by itself
by Nick Boldt (JIRA)
Cannot run tests when building JMX by itself
--------------------------------------------
Key: JBIDE-3191
URL: https://jira.jboss.org/jira/browse/JBIDE-3191
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Affects Versions: 3.0.0.beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.cr1
Using /devstudio-trunk/releng/org.jboss.ide.eclipse.releng/hudson/build.sh with the following parameters changed, JMX will build on its own:
builders=jmx
nightlyBuildSteps=standalone.product,reports,build-results,update-site
Turning tests back on, however, the build fails:
builders=jmx
nightlyBuildSteps=standalone.product,reports,tests,build-results,update-site
[java] Java Result: 13
[echo]
[echo] The builder <b>tests</b> failed to compile with the following results:<br/><br/>
[echo]
[echo] <pre>
[echo] BUILD FAILED
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:24: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:64: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/org.jboss.ide.eclipse.releng/builders/tests/customTargets.xml:13: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/genericTargets.xml:88: Bundle org.jboss.tools.common.kb.test_0.0.0 failed to resolve.:
[echo] Missing required plug-in org.jboss.tools.common_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.kb_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.test_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.projecttemplates_0.0.0.
[echo]
[echo]
[echo] Total time: 3 minutes 2 seconds
[echo] </pre>
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/3.0.0.CR1/200811132054/tests
BUILD FAILED
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:12: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:56: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:37: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:76: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:105: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:261: Specify at least one source - a file or a resource collection.
Total time: 23 minutes 21 seconds
I suspect this is a result of the tests being coupled together, such that they depend on the whole build (builders=jmx,examples,drools-ide,archives,richfaces,jbpm-convert,freemarker,hibernate-tools,struts,jbpm,as,seam,esb,ws,birt,portlet,smooks) and its output.
Would there be value in incrementally splitting each build's tests out so they can run independently? eg.,
builders=jmx,jmx-tests
nightlyBuildSteps=standalone.product,reports,tests-jmx,build-results,update-site
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10639) Can't create JSF project
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10639:
--------------------------------------
Summary: Can't create JSF project
Key: JBIDE-10639
URL: https://issues.jboss.org/browse/JBIDE-10639
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.3.0.Beta1
I just tried to created JSF 2 KickStart project via JBossTools Wizard and got:
{code}
java.lang.NullPointerException
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1003)
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:972)
at org.apache.velocity.runtime.RuntimeSingleton.parse(RuntimeSingleton.java:265)
at org.apache.velocity.app.Velocity.evaluate(Velocity.java:274)
at org.jboss.tools.jst.web.ui.operation.TemplatePreprocessor.process(TemplatePreprocessor.java:92)
at org.jboss.tools.jst.web.ui.operation.TemplatePreprocessor.execute(TemplatePreprocessor.java:58)
at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.preprocessTemplate(WebNatureOperation.java:594)
at org.jboss.tools.jsf.ui.operation.JSFProjectCreationOperation.copyTemplate(JSFProjectCreationOperation.java:114)
at org.jboss.tools.jst.web.ui.operation.WebProjectCreationOperation.preCreateWebNature(WebProjectCreationOperation.java:76)
at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.run(WebNatureOperation.java:222)
at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1029)
at org.jboss.tools.jst.web.ui.wizards.project.NewWebProjectWizard.performFinish(NewWebProjectWizard.java:66)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
...
org.eclipse.core.runtime.CoreException: java.lang.NullPointerException
at org.jboss.tools.jst.web.ui.operation.WebProjectCreationOperation.preCreateWebNature(WebProjectCreationOperation.java:81)
at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.run(WebNatureOperation.java:222)
at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1029)
at org.jboss.tools.jst.web.ui.wizards.project.NewWebProjectWizard.performFinish(NewWebProjectWizard.java:66)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.lang.NullPointerException
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1003)
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:972)
at org.apache.velocity.runtime.RuntimeSingleton.parse(RuntimeSingleton.java:265)
at org.apache.velocity.app.Velocity.evaluate(Velocity.java:274)
at org.jboss.tools.jst.web.ui.operation.TemplatePreprocessor.process(TemplatePreprocessor.java:92)
at org.jboss.tools.jst.web.ui.operation.TemplatePreprocessor.execute(TemplatePreprocessor.java:58)
at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.preprocessTemplate(WebNatureOperation.java:594)
at org.jboss.tools.jsf.ui.operation.JSFProjectCreationOperation.copyTemplate(JSFProjectCreationOperation.java:114)
at org.jboss.tools.jst.web.ui.operation.WebProjectCreationOperation.preCreateWebNature(WebProjectCreationOperation.java:76)
... 49 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10698) Option to disable twisties for files in the "project explorer" view
by Vadim Dmitriev (JIRA)
Vadim Dmitriev created JBIDE-10698:
--------------------------------------
Summary: Option to disable twisties for files in the "project explorer" view
Key: JBIDE-10698
URL: https://issues.jboss.org/browse/JBIDE-10698
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Vadim Dmitriev
JBT extends project explorer view so all files now have twisties near them, even for files that are not expandable (i.e. when you click twistie it just disappears).
It would be nice to have a preference to disable this file "augmentation" or at least for these twisties to be displayed only for files that can really be expanded (faces-config.xml, web.xml, etc.).
{color:gray}Twistie is a little +/- or triangle icon near node of the tree to expand/collapse it. Strange word, but never heard a better name for this GUI element.{color}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10754) Hyperlink tests failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10754:
--------------------------------------
Summary: Hyperlink tests failure
Key: JBIDE-10754
URL: https://issues.jboss.org/browse/JBIDE-10754
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, common/jst/core, jsp/jsf/xml source editing, Seam 2
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.3.0.Beta1
For example:
{code}
Running org.jboss.tools.cdi.seam.text.ext.test.CdiSeamTextExtAllTests
Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 21.012 sec <<< FAILURE!
testSeamConfigTagNameHyperlink(org.jboss.tools.cdi.seam.text.ext.test.SeamConfigTagNameHyperlinkTest) Time elapsed: 0.186 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find HyperLink
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.tools.cdi.text.ext.test.CDIHyperlinkTestUtil.checkHyperLinkInXml(CDIHyperlinkTestUtil.java:226)
at org.jboss.tools.cdi.seam.text.ext.test.SeamConfigTagNameHyperlinkTest.testSeamConfigTagNameHyperlink(SeamConfigTagNameHyperlinkTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
{code}
{code}
Tests run: 78, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 511.708 sec <<< FAILURE!
testSeamViewPartitioner(org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest) Time elapsed: 33.838 sec <<< ERROR!
java.lang.AbstractMethodError
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:48)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitions(HyperlinkDetector.java:74)
at org.jboss.tools.seam.ui.test.hyperlink.TestHyperlinkDetector.getPartitions(SeamViewHyperlinkPartitionerTest.java:297)
at org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest.testSeamViewPartitioner(SeamViewHyperlinkPartitionerTest.java:124)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10756) Debug button attempts to start already running server, reports port in use
by James Wilson (JIRA)
James Wilson created JBIDE-10756:
------------------------------------
Summary: Debug button attempts to start already running server, reports port in use
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press the "Start the server in debug mode" button on the Servers view toolbar. When I want to run my application I usually click on the Debug button on the main Eclipse toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools 3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again and it all works fine after that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBDS-1985) Synchronizing a VDB takes too long in 7.4.2
by Paul Nittel (JIRA)
[ https://issues.jboss.org/browse/JBDS-1985?page=com.atlassian.jira.plugin.... ]
Paul Nittel commented on JBDS-1985:
-----------------------------------
Today I tested 4.1.1, updated with the patch, again with Platypus. Worked great.
> Synchronizing a VDB takes too long in 7.4.2
> -------------------------------------------
>
> Key: JBDS-1985
> URL: https://issues.jboss.org/browse/JBDS-1985
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Support Patch
> Security Level: Public(Everyone can see)
> Components: teiid
> Affects Versions: 4.1.1.GA
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 4.1.2.GA
>
> Attachments: JBDS1985.upversion.patch.txt, org.teiid.designer.core.patch, org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, org.teiid.designer.vdb.test.patch, org.teiid.designer.vdb.ui.patch, TEIIDDES-1200-7.4.2-Patch-A.zip, TEIIDDES_1200.zip, UdfManager.java.patch, UdfUiPlugin.java.patch, VdbUtil.java.patch
>
>
> Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0)
> Investigating/debug noted 2 areas.
> 1) New UdfManager is not caching a FunctionLibrary and each SQL validation is creating a new instance. (needs a fix)
> 2) Synchronizing a VDB is hammering the ChecksumUtil.computeChecksum() during the VDB's resource build processing
> 3) PreviewManager is using a new Vdb() object to determine if "preview = true" and version #. However, it's heavy weight and currently the Vdb() is registering for events, but is not being Unregistered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months