[JBoss JIRA] Commented: (JBIDE-2038) Connector modules are not deployed
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-2038?page=comments#action_12408119 ]
Max Andersen commented on JBIDE-2038:
-------------------------------------
chris, or simply dont mix ga and nightly builds into the same eclipse ,)
Thanks for the quick update ;)
> Connector modules are not deployed
> ----------------------------------
>
> Key: JBIDE-2038
> URL: http://jira.jboss.com/jira/browse/JBIDE-2038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.1.0.beta1
> Environment: Windows XP Professional SP2
> Eclipse Platform Version: 3.3.2 Build id: M20080221-1800
> Web Tools Platform 'wtp-R-2.0.2-20080223205547'
> Seam 2.0.1 GA
> JBossTools 2.0.1
> JBossAS 4.2.2.GA
> Reporter: Chris Odom
> Assigned To: Rob Stryker
> Fix For: 2.1.0.cr1
>
>
> I have craeted a Seam Project that is deployed as an EAR file. Several weeks of development time has gone by and I have been publishing the ear project to my JBoss Server instance with only one issue.
> issue#1: When publishing the EAR project I find that none of the <ear project>/EarContent/*.<any archive> will get deployed. XML's, any Drools and the Descriptors get deployed but none of the Ear library files get deployed.
> Continuing to my problem. After some development time I created a JCA 1.5 Connector project to use with in my Seam Project. During the JCA project creation I did notice that the wizard had some troubles with the ear selection portion. What I would see is that even though I selected the ear checkbox the ear drop down list would not activate as in it stayed disabled. Unchecking an checking a second time would enable the list. I selected my ear and used JCA 1.5 and Java 5.0 as my only 2 facets and clicked finished. The Project was successfully created and the ear descriptor files were correctly updated.
> issue#2: While checking the new JCA's properties I noticed that I could not see any Targeted Runtimes and when checking "Show all runtimes" the correct ear Runtime shows up in the list but I can not select it as for it is disabled and gives the facet warning text at the bottom. Also with in the Build Properties the Server Runtime is not added either and I had to add it manually.
> After all is said and done, when I go to "publish" the ear project using the JBoss Server View every thing that is in my ear gets deployed excpect the JCA project and of course the issue#1 I mentioned earlier. While using the "Export..." tool I can successfully export the entire ear archive to the JBoss Server with out any problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Closed: (JBIDE-2038) Connector modules are not deployed
by Chris Odom (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-2038?page=all ]
Chris Odom closed JBIDE-2038.
-----------------------------
Resolution: Done
Okay I was using the *****.link methodology for using the nightly builds. With this you can not for the packages that are GA release to not be loaded in favor of the nightly builds. To fix this go into your Help>Software Updates>Manage Configuration. Look at local list of plugins that match our nightly list of plugins and do a replace with. Each time you do this it will ask you to restart but say no until you have replaced each plugin with the nightly version. After that I was able to restart -clean and deploy my JCA connector with in my EAR project. Sorry for the Confusion Rob will close this issue.
> Connector modules are not deployed
> ----------------------------------
>
> Key: JBIDE-2038
> URL: http://jira.jboss.com/jira/browse/JBIDE-2038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.1.0.beta1
> Environment: Windows XP Professional SP2
> Eclipse Platform Version: 3.3.2 Build id: M20080221-1800
> Web Tools Platform 'wtp-R-2.0.2-20080223205547'
> Seam 2.0.1 GA
> JBossTools 2.0.1
> JBossAS 4.2.2.GA
> Reporter: Chris Odom
> Assigned To: Rob Stryker
> Fix For: 2.1.0.cr1
>
>
> I have craeted a Seam Project that is deployed as an EAR file. Several weeks of development time has gone by and I have been publishing the ear project to my JBoss Server instance with only one issue.
> issue#1: When publishing the EAR project I find that none of the <ear project>/EarContent/*.<any archive> will get deployed. XML's, any Drools and the Descriptors get deployed but none of the Ear library files get deployed.
> Continuing to my problem. After some development time I created a JCA 1.5 Connector project to use with in my Seam Project. During the JCA project creation I did notice that the wizard had some troubles with the ear selection portion. What I would see is that even though I selected the ear checkbox the ear drop down list would not activate as in it stayed disabled. Unchecking an checking a second time would enable the list. I selected my ear and used JCA 1.5 and Java 5.0 as my only 2 facets and clicked finished. The Project was successfully created and the ear descriptor files were correctly updated.
> issue#2: While checking the new JCA's properties I noticed that I could not see any Targeted Runtimes and when checking "Show all runtimes" the correct ear Runtime shows up in the list but I can not select it as for it is disabled and gives the facet warning text at the bottom. Also with in the Build Properties the Server Runtime is not added either and I had to add it manually.
> After all is said and done, when I go to "publish" the ear project using the JBoss Server View every thing that is in my ear gets deployed excpect the JCA project and of course the issue#1 I mentioned earlier. While using the "Export..." tool I can successfully export the entire ear archive to the JBoss Server with out any problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Reopened: (JBIDE-2038) Connector modules are not deployed
by Chris Odom (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-2038?page=all ]
Chris Odom reopened JBIDE-2038:
-------------------------------
See comments above!
> Connector modules are not deployed
> ----------------------------------
>
> Key: JBIDE-2038
> URL: http://jira.jboss.com/jira/browse/JBIDE-2038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.1.0.beta1
> Environment: Windows XP Professional SP2
> Eclipse Platform Version: 3.3.2 Build id: M20080221-1800
> Web Tools Platform 'wtp-R-2.0.2-20080223205547'
> Seam 2.0.1 GA
> JBossTools 2.0.1
> JBossAS 4.2.2.GA
> Reporter: Chris Odom
> Assigned To: Rob Stryker
> Fix For: 2.1.0.cr1
>
>
> I have craeted a Seam Project that is deployed as an EAR file. Several weeks of development time has gone by and I have been publishing the ear project to my JBoss Server instance with only one issue.
> issue#1: When publishing the EAR project I find that none of the <ear project>/EarContent/*.<any archive> will get deployed. XML's, any Drools and the Descriptors get deployed but none of the Ear library files get deployed.
> Continuing to my problem. After some development time I created a JCA 1.5 Connector project to use with in my Seam Project. During the JCA project creation I did notice that the wizard had some troubles with the ear selection portion. What I would see is that even though I selected the ear checkbox the ear drop down list would not activate as in it stayed disabled. Unchecking an checking a second time would enable the list. I selected my ear and used JCA 1.5 and Java 5.0 as my only 2 facets and clicked finished. The Project was successfully created and the ear descriptor files were correctly updated.
> issue#2: While checking the new JCA's properties I noticed that I could not see any Targeted Runtimes and when checking "Show all runtimes" the correct ear Runtime shows up in the list but I can not select it as for it is disabled and gives the facet warning text at the bottom. Also with in the Build Properties the Server Runtime is not added either and I had to add it manually.
> After all is said and done, when I go to "publish" the ear project using the JBoss Server View every thing that is in my ear gets deployed excpect the JCA project and of course the issue#1 I mentioned earlier. While using the "Export..." tool I can successfully export the entire ear archive to the JBoss Server with out any problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Commented: (JBIDE-2038) Connector modules are not deployed
by Chris Odom (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-2038?page=comments#action_12408103 ]
Chris Odom commented on JBIDE-2038:
-----------------------------------
Wondering if this has been checked in to SVN. Downloaded the new nightly build JBossTools-200804100822-nightly-ALL-win32.zip did the -clean checked the plugin properties all looks correct. Created a new JCA project (still see the same problems as before issue#2) and was able to catch this error in the part of selecting the ear during the JCA connecter wizard.
java.lang.NullPointerException
at org.eclipse.wst.common.project.facet.ui.internal.FacetsSelectionPanel.setSelectedProjectFacets(FacetsSelectionPanel.java:802)
at org.eclipse.wst.common.project.facet.ui.internal.FacetsSelectionPanel.setDefaultFacetsForRuntime(FacetsSelectionPanel.java:776)
at org.eclipse.wst.common.project.facet.ui.internal.FacetsSelectionPage.setDefaultFacetsForRuntime(FacetsSelectionPage.java:133)
at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.setRuntimeAndDefaultFacets(NewProjectDataModelFacetWizard.java:267)
at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard$2.propertyChanged(NewProjectDataModelFacetWizard.java:239)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:183)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172)
at org.eclipse.wst.common.frameworks.datamodel.AbstractDataModelProvider.setProperty(AbstractDataModelProvider.java:234)
at org.eclipse.jst.j2ee.project.facet.J2EEFacetProjectCreationDataModelProvider.propertySet(J2EEFacetProjectCreationDataModelProvider.java:101)
at org.eclipse.jst.j2ee.jca.project.facet.ConnectorFacetProjectCreationDataModelProvider.propertySet(ConnectorFacetProjectCreationDataModelProvider.java:72)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:182)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172)
at org.eclipse.wst.common.frameworks.datamodel.AbstractDataModelProvider.setProperty(AbstractDataModelProvider.java:234)
at org.eclipse.jst.j2ee.jca.project.facet.ConnectorFacetProjectCreationDataModelProvider.access$1(ConnectorFacetProjectCreationDataModelProvider.java:1)
at org.eclipse.jst.j2ee.jca.project.facet.ConnectorFacetProjectCreationDataModelProvider$1.propertyChanged(ConnectorFacetProjectCreationDataModelProvider.java:55)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337)
at org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.propertySet(J2EEModuleFacetInstallDataModelProvider.java:132)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:182)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172)
at org.eclipse.wst.common.frameworks.datamodel.AbstractDataModelProvider.setProperty(AbstractDataModelProvider.java:234)
at org.eclipse.jst.j2ee.project.facet.J2EEModuleFacetInstallDataModelProvider.propertySet(J2EEModuleFacetInstallDataModelProvider.java:122)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:182)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.setProperty(DataModelSynchHelper.java:189)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper$CheckboxSelectionListener.widgetSelected(DataModelSynchHelper.java:143)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:182)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Was able to uncheck and re-check to select the ear, continued with the JCA connector wizard selected the same facets as before. This time when viewing the JCA project properties I got the same response...No build path for the EAR's runtime envrionment and not targeted runtimes available.
If this is not checked in to SVN then I am sure you did fix it otherwise I am not sure what you fixed!...;)
> Connector modules are not deployed
> ----------------------------------
>
> Key: JBIDE-2038
> URL: http://jira.jboss.com/jira/browse/JBIDE-2038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.1.0.beta1
> Environment: Windows XP Professional SP2
> Eclipse Platform Version: 3.3.2 Build id: M20080221-1800
> Web Tools Platform 'wtp-R-2.0.2-20080223205547'
> Seam 2.0.1 GA
> JBossTools 2.0.1
> JBossAS 4.2.2.GA
> Reporter: Chris Odom
> Assigned To: Rob Stryker
> Fix For: 2.1.0.cr1
>
>
> I have craeted a Seam Project that is deployed as an EAR file. Several weeks of development time has gone by and I have been publishing the ear project to my JBoss Server instance with only one issue.
> issue#1: When publishing the EAR project I find that none of the <ear project>/EarContent/*.<any archive> will get deployed. XML's, any Drools and the Descriptors get deployed but none of the Ear library files get deployed.
> Continuing to my problem. After some development time I created a JCA 1.5 Connector project to use with in my Seam Project. During the JCA project creation I did notice that the wizard had some troubles with the ear selection portion. What I would see is that even though I selected the ear checkbox the ear drop down list would not activate as in it stayed disabled. Unchecking an checking a second time would enable the list. I selected my ear and used JCA 1.5 and Java 5.0 as my only 2 facets and clicked finished. The Project was successfully created and the ear descriptor files were correctly updated.
> issue#2: While checking the new JCA's properties I noticed that I could not see any Targeted Runtimes and when checking "Show all runtimes" the correct ear Runtime shows up in the list but I can not select it as for it is disabled and gives the facet warning text at the bottom. Also with in the Build Properties the Server Runtime is not added either and I had to add it manually.
> After all is said and done, when I go to "publish" the ear project using the JBoss Server View every thing that is in my ear gets deployed excpect the JCA project and of course the issue#1 I mentioned earlier. While using the "Export..." tool I can successfully export the entire ear archive to the JBoss Server with out any problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Commented: (JBIDE-675) Large JSF file are too slow to handle, making editor useless for them
by Maxim Areshkau (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-675?page=comments#action_12408057 ]
Maxim Areshkau commented on JBIDE-675:
--------------------------------------
I have tried to add in function VpeVisualDomBuilder.createNode calling of function Display.readAndDispatch() and now when we type smt. in source editor, eclipse doesn't sleep. But it's solution works for Mac and Windows and crash eclipse on Linux.Also It's solution works match better then using proxy.
Bug with Display.readAndDispatch() was fixed, but it's fill be available only for eclipse 3.4( you can see this thread http://dev.eclipse.org/newslists/news.eclipse.platform.swt/msg40404.html).
> Large JSF file are too slow to handle, making editor useless for them
> ---------------------------------------------------------------------
>
> Key: JBIDE-675
> URL: http://jira.jboss.com/jira/browse/JBIDE-675
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Visual Page Editor
> Affects Versions: ExadelStudioPro4
> Environment: Eclipse 3.2.2
> Exadel Studio 4.0.4
> Kubuntu Feisty Fawn
> 1G RAM
> CPU Intel(R) Pentium(R) 4 CPU 2.80GHz, HyperThreading activated
> Reporter: David Delbecq
> Assigned To: Maxim Areshkau
> Priority: Critical
> Fix For: 2.2.x
>
> Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt, editStructure.txt, JBIDE-675.tar.gz, loading_dump.txt, profiling.tar.gz, stacktraces-rhd2b1.log.gz, tree.txt
>
>
> Post to JIRA, following recommandatiopn here: http://jboss.com/index.html?module=bb&op=viewtopic&t=115447
> When editing JSF files That contains quite a lot of include, it take commonly up to 20 seconds for one character i type to get it's way to the screen. I can even see, after 10 seconds, the cursor goes on step right, and after a new 10 second the character appear in front of the cursor. This make it impossible to use JSF editor from exadel to edit such file, i have to ressort to plain xml editor without completion for facelets tags.
> I will be posting attachement containing description of files involved (sorry, no file content).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years