February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10718) User requesting ports to work for custom adapter

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-10718: ----------------------------------- Summary: User requesting ports to work for custom adapter Key: JBIDE-10718 URL: https://issues.jboss.org/browse/JBIDE-10718 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta1 A user is requesting that default xpath ports should work for his custom adapter. Current support is not available for his specific usecase and so some small api changes will be needed -- 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

2
2
0 / 0

[JBoss JIRA] (JBIDE-10617) Wizard page "Configure Seam Facet Settings" should be with unchecked filed "Create Test Project" and fields "Test Project Name" and "Test Package Name" should be disabled

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-10617: ------------------------------------- Summary: Wizard page "Configure Seam Facet Settings" should be with unchecked filed "Create Test Project" and fields "Test Project Name" and "Test Package Name" should be disabled Key: JBIDE-10617 URL: https://issues.jboss.org/browse/JBIDE-10617 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.0.Beta1 Attachments: ConfigureSeamFacetSettings.png -- 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

3
5
0 / 0

[JBoss JIRA] (JBIDE-10606) Seam Generate Entities wizard problem

by Tomas Remes (Created) (JIRA)

Seam Generate Entities wizard problem ------------------------------------- Key: JBIDE-10606 URL: https://issues.jboss.org/browse/JBIDE-10606 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Environment: JBDS 4.1.0.GA Reporter: Tomas Remes Assignee: Alexey Kazakov Steps to reproduce: 1. Import existing Seam 2.2 project into workspace 2. Add valid Seam runtime to the project (in Seam Settings) 3. No project is selected in package explorer!!! 4. File -> New -> Seam Generate Entities 5. Fill in imported project name (or try to select project using Browse button) 6. Following error occurs: Selected seam project has some invalid settings. Please press "Settings..." and correct them. In settings is everything fine, project has valid Seam runtime and this error still occurs. -- 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

4
4
0 / 0

[JBoss JIRA] (JBIDE-11025) CLONE - CLONE - CLONE - CLONE - CLONE - BPEL Component N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11025: ------------------------------------------- Summary: CLONE - CLONE - CLONE - CLONE - CLONE - BPEL Component N&N Key: JBIDE-11025 URL: https://issues.jboss.org/browse/JBIDE-11025 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: BPEL Reporter: Brian Fitzpatrick Assignee: Robert (Bob) Brodt Fix For: 3.3.0.M5 Create a N&N for any BPEL N&N issues for the M2 release -- 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

3
4
0 / 0

[JBoss JIRA] (JBIDE-10771) OpenShift Express: Unable to create application on Staging

by Attila Nagy (JIRA)

Attila Nagy created JBIDE-10771: ----------------------------------- Summary: OpenShift Express: Unable to create application on Staging Key: JBIDE-10771 URL: https://issues.jboss.org/browse/JBIDE-10771 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Attila Nagy I'm unable to create an application using the staging server because when I typing the application name Eclipse floods the error-log with the following error-message: eclipse.buildId=M20110909-1335 java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product Error Wed Feb 01 11:01:07 CET 2012 Unhandled exception: java.lang.NullPointerException java.lang.RuntimeException: java.lang.NullPointerException at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:65) at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:51) at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:83) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:104) at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:55) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:103) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:103) at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:486) at org.eclipse.core.databinding.ValueBinding$4.run(ValueBinding.java:197) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:188) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:151) at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:140) at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:45) at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:62) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:55) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:93) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:67) at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:62) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:71) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:120) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$1(SimplePropertyObservableValue.java:112) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$2.run(SimplePropertyObservableValue.java:66) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:63) at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:63) at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:55) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) at org.eclipse.swt.widgets.Combo.gtk_changed(Combo.java:1170) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1693) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4402) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.central.editors.GettingStartedPage$9.linkActivated(GettingStartedPage.java:614) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPageModel.validateApplicationName(ApplicationConfigurationWizardPageModel.java:129) at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPageModel.setSelectedCartridge(ApplicationConfigurationWizardPageModel.java:98) 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) at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59) ... 84 more I cannot create on buttons 'Finnish' or 'Next'. -- 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

4
6
0 / 0

[JBoss JIRA] (JBIDE-10470) Hibernate configuration is not able to use Hibernate Configuration File referenced in persistence.xml

by Jiri Peterka (Created) (JIRA)

Hibernate configuration is not able to use Hibernate Configuration File referenced in persistence.xml ----------------------------------------------------------------------------------------------------- Key: JBIDE-10470 URL: https://issues.jboss.org/browse/JBIDE-10470 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M4 Environment: JBSD 5.0.M5 H55 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 1. Create JPA Project 2. Add JPA/Hibernate(4.0) libs 3. Open persitence.xml 4. On Hibernate page use Configuration file, create it 5. Try to use Hibernate Console ERROR: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration Could not create JPA based Configuration <No message> java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException: <no message> java.lang.reflect.InvocationTargetException javax.persistence.PersistenceException: [PersistenceUnit: jpahibernate40] Unable to configure EntityManagerFactory [PersistenceUnit: jpahibernate40] Unable to configure EntityManagerFactory org.hibernate.HibernateException: /jpahibernate40/src/hibernate.cfg.xml not found /jpahibernate40/src/hibernate.cfg.xml not found In persistence.xml is: <property name="hibernate.ejb.cfgfile" value="/jpahibernate40/src/hibernate.cfg.xml"/> -- 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

6
12
0 / 0

[JBoss JIRA] (JBIDE-10502) Could not embed cartridges to application

by Pavol Srna (Created) (JIRA)

Could not embed cartridges to application ----------------------------------------- Key: JBIDE-10502 URL: https://issues.jboss.org/browse/JBIDE-10502 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: jbdevstudio-product-linux-gtk-5.0.0.v201112150534M-H62-M5.jar Reporter: Pavol Srna Assignee: Andre Dietisheim Fix For: 3.3.0.M5 Attachments: stack.txt See attached stack trace. -- 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

9
20
0 / 0

[JBoss JIRA] (JBIDE-10693) openshift should provide a "remember password" option

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10693: ------------------------------------------- Summary: openshift should provide a "remember password" option Key: JBIDE-10693 URL: https://issues.jboss.org/browse/JBIDE-10693 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Xavier Coulon Fix For: 3.3.0.Beta1 we should provide secure storage of the password for openshift access. this becomes important/relevant with express console view. -- 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

4
9
0 / 0

[JBoss JIRA] (JBIDE-10623) CDI Tool documentation in JBoss Tools Reference Guides

by Stuart Smith (JIRA)

Stuart Smith created JBIDE-10623: ------------------------------------ Summary: CDI Tool documentation in JBoss Tools Reference Guides Key: JBIDE-10623 URL: https://issues.jboss.org/browse/JBIDE-10623 Project: Tools (JBoss Tools) Issue Type: Task Components: CDI Affects Versions: 3.2.1.Final Reporter: Stuart Smith Assignee: Alexey Kazakov Currently if you go to the "Reference Guides" section of the JBoss Tools documentation there is no mention of the CDI tools. In the "New and Noteworthy" notes there is always a section on 'CDI/Seam' tools so one assumes these are developed together. However, when going to the 'Seam Tools' reference guide there is also no mention of CDI tools. Since currently the only way to get CDI tools is to install JBoss Tools it might be good to document CDI tools separately if this makes sense. This way anyone looking for CDI tools (who may not know the history and relationship with Seam) will not misinterpret that they must use Seam in their project to use CDI. -- 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

3
11
0 / 0

[JBoss JIRA] Created: (JBDS-856) Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value

by Robert Morse (JIRA)

Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value ---------------------------------------------------------------------------------------------------------------- Key: JBDS-856 URL: https://jira.jboss.org/jira/browse/JBDS-856 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Mac OS X 10.6 (Snow Leopard) JBoss AS 5.1.0.GA JDK 1.6 Reporter: Robert Morse When trying to create a new JBoss AS server, JBDS complains with: The server cannot be saved for the following reasons: One or more ports have an invalid value. This may adversely affect the tooling's ability to interact with the server. I've never seen this error before, and I'm not sure what the port values should be. Currently, the Automatically detect check boxes are checked -- 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

6
19
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012