November 2007 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1337) Extraneous value showing up in generated persistence.xml making it invalid

by Marcus Adair (JIRA)

Extraneous value showing up in generated persistence.xml making it invalid -------------------------------------------------------------------------- Key: JBIDE-1337 URL: http://jira.jboss.com/jira/browse/JBIDE-1337 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.CR1 Environment: Red Hat Developer Studio, Windows XP, Seam 2.0 Reporter: Marcus Adair Priority: Minor When I generate new Seam EAR projects with the CR1 release, the persistence.xml has an error in it. I've tried to find an error in my eclipse database configuration, but can't seem to see a fault. Here is what I get, the final property setting has a trailing "dbname" value which is my database name: <?xml version="1.0" encoding="UTF-8"?>  <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0"> <persistence-unit name="testproj"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/testprojDatasource</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5InnoDBDialect"/> <property name="hibernate.hbm2ddl.auto" value="update"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.format_sql" value="true"/> <property name="jboss.entity.manager.factory.jndi.name" value="java:/testprojEntityManagerFactory"/>dbname </properties> </persistence-unit> </persistence> -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (RHDS-304) Installer still says Beta 2 on last page!

by Max Andersen (JIRA)

Installer still says Beta 2 on last page! ----------------------------------------- Key: RHDS-304 URL: http://jira.jboss.com/jira/browse/RHDS-304 Project: Red Hat Developer Studio Issue Type: Bug Affects Versions: 1.0.0.CR1 Reporter: Max Andersen Priority: Blocker Fix For: 1.0.0.GA Can't we get that version name parameterized so it is all handled by the build so we don't miss things like this ? -- 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

16 years, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (RHDS-316) "Create jBPM Process Project" in the welcome section does not open a wizard

by Adrian Mitev (JIRA)

"Create jBPM Process Project" in the welcome section does not open a wizard --------------------------------------------------------------------------- Key: RHDS-316 URL: http://jira.jboss.com/jira/browse/RHDS-316 Project: Red Hat Developer Studio Issue Type: Bug Affects Versions: 1.0.0.CR1 Environment: windows xp, rhds cr1, java 1.5_0.12 Reporter: Adrian Mitev This is in the error log java.lang.RuntimeException: Configuration element with id=org.jbpm.ui.wizard.new.project is not found at com.redhat.rhds.product.intro.action.RunWizardIntroURLAction.findClassByElementId(RunWizardIntroURLAction.java:78) at com.redhat.rhds.product.intro.action.RunWizardIntroURLAction.findNewWizardsItem(RunWizardIntroURLAction.java:67) at com.redhat.rhds.product.intro.action.RunWizardIntroURLAction.run(RunWizardIntroURLAction.java:44) at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.runAction(IntroURL.java:282) at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(IntroURL.java:193) at org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(IntroURL.java:144) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(IntroURL.java:141) at org.eclipse.ui.internal.intro.impl.swt.PageWidgetFactory$1.linkActivated(PageWidgetFactory.java:63) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:228) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:316) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:300) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:119) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) -- 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

16 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1335) components.xml editor showing errors

by Rizwan Qureshi (JIRA)

components.xml editor showing errors ------------------------------------ Key: JBIDE-1335 URL: http://jira.jboss.com/jira/browse/JBIDE-1335 Project: JBoss Tools Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.0.0.CR1 Environment: Windows-Vista, using RHDS-CR1 Reporter: Rizwan Qureshi seam-gen version: 2.0GA RHDS version:Beta2 When I open the components.xml file using the "Red Hat XML editor" I get errors and one is unable to use the "Tree View" to edit info (all fields are disabled). errors are at these locations: 1. @debug@ 2. <action execute="#{redirect.captureCurrentView}"/> (error displayed: Attribute 'execute' is not allowed....) --------components.xml file-------------------------- <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:persistence="http://jboss.com/products/seam/persistence" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:bpm="http://jboss.com/products/seam/bpm" xmlns:security="http://jboss.com/products/seam/security" xmlns:mail="http://jboss.com/products/seam/mail" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.0.xsd http://jboss.com/products/seam/persistence http://jboss.com/products/seam/persistence-2.0.xsd http://jboss.com/products/seam/drools http://jboss.com/products/seam/drools-2.0.xsd http://jboss.com/products/seam/bpm http://jboss.com/products/seam/bpm-2.0.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-2.0.xsd http://jboss.com/products/seam/mail http://jboss.com/products/seam/mail-2.0.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.0.xsd"> <core:init debug="@debug@" jndi-pattern="@jndiPattern@"/> <core:manager concurrent-request-timeout="500" conversation-timeout="120000" conversation-id-parameter="cid"/> <persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:/omniwebngEntityManagerFactory"/> <drools:rule-base name="securityRules"> <drools:rule-files> <value>/security.drl</value> </drools:rule-files> </drools:rule-base> <security:identity authenticate-method="#{authenticator.authenticate}" security-rules="#{securityRules}"/> <event type="org.jboss.seam.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.postAuthenticate"> <action execute="#{redirect.returnToCapturedView}"/> </event> <mail:mail-session host="localhost" port="2525" username="test" password="test" />   </components> -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1333) Still seeing ConcurrentExceptions in error logs :(

by Max Andersen (JIRA)

Still seeing ConcurrentExceptions in error logs :( -------------------------------------------------- Key: JBIDE-1333 URL: http://jira.jboss.com/jira/browse/JBIDE-1333 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Assigned To: Alexey Kazakov Priority: Critical Fix For: 2.0.0.GA >From error logs in JBIDE-1329: user is still getting concurrentmodification exceptions in CR1! - is the seam model not threadsafe or ? !ENTRY org.eclipse.wst.validation 4 0 2007-11-19 14:51:29.479 !MESSAGE *** ERROR ***: Mon Nov 19 14:51:29 EET 2007 java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at org.jboss.tools.seam.internal.core.SeamProject.getVariables(SeamProject.java:992) at org.jboss.tools.seam.internal.core.el.SeamExpressionResolver.internalResolveVariables(SeamExpressionResolver.java:65) at org.jboss.tools.seam.internal.core.el.SeamExpressionResolver.resolveVariables(SeamExpressionResolver.java:53) at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveVariables(SeamELCompletionEngine.java:645) at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:390) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateElOperand(SeamELValidator.java:277) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateEl(SeamELValidator.java:256) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateString(SeamELValidator.java:245) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateNodeContent(SeamELValidator.java:210) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateDom(SeamELValidator.java:181) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateFile(SeamELValidator.java:138) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateAll(SeamELValidator.java:114) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateAll(SeamValidatorManager.java:84) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:64) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

16 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (RHDS-313) Proper warning when installing on 64-Bit JVMs on Linux

by Sanne Grinovero (JIRA)

Proper warning when installing on 64-Bit JVMs on Linux ------------------------------------------------------ Key: RHDS-313 URL: http://jira.jboss.com/jira/browse/RHDS-313 Project: Red Hat Developer Studio Issue Type: Bug Components: installer, Build, integration Affects Versions: 1.0.0.beta2 Environment: Linux x86_64, any jdk Reporter: Sanne Grinovero Priority: Minor Fix For: LATER When picking the JVM, the installer shows a "The chosen directory does not contain a Java VM"-message, when picking a 64-bit jdk. It checks for "selected-path/lib/i386/client/libjvm.so" to verify the path but it is "selected-path/lib/amd64/server/libjvm.so" for a 64-bit jdk. -- 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

16 years, 11 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-1330) can not xhtml pages on mac os x 10.5

by Murat HAZER (JIRA)

can not xhtml pages on mac os x 10.5 ------------------------------------ Key: JBIDE-1330 URL: http://jira.jboss.com/jira/browse/JBIDE-1330 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.CR1 Environment: mac os x 10.5 Reporter: Murat HAZER when i try to open xhtml pages i get the following error Unhandled event loop exception Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line -Djava.awt.headless=true solves the problem but this time code completion/assist and vidual editor don't work... -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1302) deploy directory ui layout is broken

by Max Andersen (JIRA)

deploy directory ui layout is broken ------------------------------------ Key: JBIDE-1302 URL: http://jira.jboss.com/jira/browse/JBIDE-1302 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Reporter: Max Andersen Assigned To: Rob Stryker Fix For: 2.0.0.CR1 The browse button instead of the text field is the one that is scaled when stretching the layout. Browse could be changed to ... to take up less space and allow one to actually read what is set. -- 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

16 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1287) War conversation bean contains unused ejb imports

by Max Andersen (JIRA)

War conversation bean contains unused ejb imports ------------------------------------------------- Key: JBIDE-1287 URL: http://jira.jboss.com/jira/browse/JBIDE-1287 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Assigned To: Max Andersen Priority: Minor Fix For: 2.0.0.GA -- 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

16 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-1326) Exception on creating hibernate configuration

by Mikle Dryakhlenkov (JIRA)

Exception on creating hibernate configuration --------------------------------------------- Key: JBIDE-1326 URL: http://jira.jboss.com/jira/browse/JBIDE-1326 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.CR1 Environment: RHDS 1.0.0 CR1 Reporter: Mikle Dryakhlenkov Assigned To: Max Andersen Fix For: 2.0.0.GA Testcase: EXECUTE: Create project with hibernate files cfg.xml and hbm.xml. EXECUTE: Add configuration with type "Core" for created project (click on button "OK" on creation dialog). ASSERT: Configuration tree are expandeable (there is no exception "Could not compute classpath"). EXECUTE: Delete this configuration. EXECUTE: Add the same configuration again, but press button "Apply" before pressing button "Ok". ASSERT: Configuration tree are expandeable (there is no exception "Could not compute classpath"). -- 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

16 years, 12 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2007