February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-8455) NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example

by Snjezana Peco (JIRA)

NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example ------------------------------------------------------------------------------------------ Key: JBIDE-8455 URL: https://issues.jboss.org/browse/JBIDE-8455 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 If you import the Weld Java EE 6 example, you will face the following exception: !ENTRY org.hibernate.eclipse.console 4 4 2011-02-20 22:54:41.156 !MESSAGE Could not activate Hibernate nature on projectjboss-javaee6-webapp !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2011-02-20 22:54:41.156 !MESSAGE org.eclipse.core.runtime.CoreException: Problems encountered while setting project description. !STACK 1 org.eclipse.core.runtime.CoreException: Problems encountered while setting project description. at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1212) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1238) at org.hibernate.eclipse.console.utils.ProjectUtils.addProjectNature(ProjectUtils.java:133) at org.hibernate.eclipse.console.utils.ProjectUtils.toggleHibernateOnProject(ProjectUtils.java:104) at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.configureInternal(HibernateProjectConfigurator.java:55) at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.mavenProjectChanged(HibernateProjectConfigurator.java:67) at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:646) at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:636) at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:767) at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:346) at org.maven.ide.eclipse.project.MavenProjectManager.refresh(MavenProjectManager.java:65) at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:209) at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:146) at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:481) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$1.run(ArchetypeExamplesWizard.java:73) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$2.run(ArchetypeExamplesWizard.java:85) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8340) connection wizard: latest username is missing in history (content proposal)

by Andre Dietisheim (JIRA)

connection wizard: latest username is missing in history (content proposal) --------------------------------------------------------------------------- Key: JBIDE-8340 URL: https://issues.jboss.org/browse/JBIDE-8340 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8003) DeltaCloud: move #deleteKey to Key

by Andre Dietisheim (JIRA)

DeltaCloud: move #deleteKey to Key ---------------------------------- Key: JBIDE-8003 URL: https://issues.jboss.org/browse/JBIDE-8003 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.x The DeltaCloud class currently has a method #deleteKey. The Deltacloud server reports available actions on objects and does so with Keys. This approach is perfect REST style as it offers links to available actions. Keys currently have a destroy action and deltacloud tools do unmarshall this correctly. The tools implementation should therefore remove #deleteKey from the DeltaCloud class and offer such a method on the key that then delegates to the appropriate (destroy-) action. The current tools implementation already offers this approach for instances but took a shortcut with Keys to have higher prio items for CR1 implemented. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5535) New Web Service

by Burr Sutter (JIRA)

New Web Service --------------- Key: JBIDE-5535 URL: https://jira.jboss.org/jira/browse/JBIDE-5535 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard. The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following: package com.jboss.lab; import javax.jws.WebMethod; import javax.jws.WebService; @WebService public class MyWebService { @WebMethod public String sayHello(String name) { return "Hello2 " + name + "!"; } } And the appropriate entries in the web.xml. <servlet> <servlet-name>MyWebServiceServlet</servlet-name> <servlet-class>com.jboss.lab.MyWebService</servlet-class> </servlet> <servlet-mapping> <servlet-name>MyWebServiceServlet</servlet-name> <url-pattern>/MyWebService</url-pattern> </servlet-mapping> See screenshots for current functionality. This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing. -- 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, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7923) Allow user to re-create the Top-down web service

by Lukas Jungmann (JIRA)

Allow user to re-create the Top-down web service ------------------------------------------------ Key: JBIDE-7923 URL: https://issues.jboss.org/browse/JBIDE-7923 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Minor use case: -have a dynamic web project with some messed up implementation of a web service from wsdl -goal is to recreate the service - regenerate artifacts from wsdl, replace current ws implementation class with new, empty one and readd entries into web.xml if needed current approach: -user has to clean everything manually - delete entries from DD, delete generated classes, delete service implementation class and rerun the new web service wizard suggested approach: -allow user to rerun the web service wizard for service existing in the project asking him if he wants to re-create it and if so then rerun the wsconsume, recreate service impl class and update DD. All these steps should be presented to the user (by default all would be on) and user should be allowed to choose which of them he wants the IDE to do and/or -provide some context sensitive action for this somewhere in the IDE, perhaps service node in project explorer view looks like a good candidate for this -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1440) Smooks Java-To-XML FreeMarker Fails in ESB

by Will Dinyes (JIRA)

Smooks Java-To-XML FreeMarker Fails in ESB ------------------------------------------ Key: JBDS-1440 URL: https://jira.jboss.org/browse/JBDS-1440 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Affects Versions: 4.0.0.Beta1 Environment: java-1.6.0-sun-devel, JBDS 4.0.0.Beta1 Reporter: Will Dinyes I created a smooks-java-to-xml.xml (attached) config via the Smooks tooling in JBDS to translate a simple bean (.java file attached) back to XML via Apply Template with an XSD (attached). When deploying this to SOA-P and then running a test, I get the following exception (in part, full exception stack attached): freemarker.core.InvalidReferenceException: Expression .vars["com"] is undefined on line 3, column 21 in free-marker-template. freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124) freemarker.core.DynamicKeyName._getAsTemplateModel(DynamicKeyName.java:75) freemarker.core.Expression.getAsTemplateModel(Expression.java:89) freemarker.core.Expression.getStringValue(Expression.java:93) freemarker.core.DollarVariable.accept(DollarVariable.java:76) freemarker.core.Environment.visit(Environment.java:208) freemarker.core.MixedContent.accept(MixedContent.java:92) freemarker.core.Environment.visit(Environment.java:208) freemarker.core.Environment.process(Environment.java:188) freemarker.template.Template.process(Template.java:232) This seems to be a missing descriptor or library that isn't deployed to the server? Not sure what's causing this. Maybe Smooks Java-to-XML isn't something we can do through the tooling at this time? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8337) Web Knowledge Base plugin throws NullPointerException on exit

by Denis Golovin (JIRA)

Web Knowledge Base plugin throws NullPointerException on exit ------------------------------------------------------------- Key: JBIDE-8337 URL: https://issues.jboss.org/browse/JBIDE-8337 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Eclipse IDE for Java EE Developers with JBT JBossAS, Seam, Richfaces installed from Development update site Reporter: Denis Golovin {noformat} java.lang.NullPointerException at org.jboss.tools.jst.web.kb.WebKbPlugin.cleanObsoleteFiles(WebKbPlugin.java:96) at org.jboss.tools.jst.web.kb.WebKbPlugin.access$0(WebKbPlugin.java:92) at org.jboss.tools.jst.web.kb.WebKbPlugin$1.saving(WebKbPlugin.java:77) at org.eclipse.core.internal.resources.SaveManager.executeLifecycle(SaveManager.java:361) at org.eclipse.core.internal.resources.SaveManager$1.run(SaveManager.java:170) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.resources.SaveManager.broadcastLifecycle(SaveManager.java:173) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1108) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1087) at org.eclipse.core.internal.resources.DelayedSnapshotJob.run(DelayedSnapshotJob.java:44) at org.eclipse.core.internal.resources.SaveManager.shutdown(SaveManager.java:1366) at org.eclipse.core.internal.resources.Workspace.close(Workspace.java:428) at org.eclipse.core.resources.ResourcesPlugin.stop(ResourcesPlugin.java:383) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:843) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:836) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:501) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:550) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1097) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:597) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:690) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:588) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:415) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8268) CDI Facet should not be available for EAR projects

by Denis Golovin (JIRA)

CDI Facet should not be available for EAR projects -------------------------------------------------- Key: JBIDE-8268 URL: https://issues.jboss.org/browse/JBIDE-8268 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.M1 It is available and has option Create bean.xml that does nothing. So it rather confusing that useful. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8495) Evaluate removal of TPTP from JBT 3.3

by Nick Boldt (JIRA)

Evaluate removal of TPTP from JBT 3.3 ------------------------------------- Key: JBIDE-8495 URL: https://issues.jboss.org/browse/JBIDE-8495 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, Cleanup Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen TPTP is being archived after their 4.7.2 release in Helios SR2 [1]. Therefore, we need to either continue to build our TPTP stuff on top of the Helios version of TPTP and patch it if necessary so it'll work in Eclipse 3.7 (JBT 3.3), or remove it entirely & drop support. [1] http://www.eclipse.org/tptp/home/project_info/devplans/EclipseTPTPProject... Currently, the feature groups we use from Eclipse TPTP 4.7 are: <unit id="org.eclipse.tptp.platform.profile.server.feature.group" version="4.5.1.v201009092123-7H7F3AkF7B79N8WCTEH"/> <unit id="org.eclipse.tptp.platform.instrumentation.ui.feature.group" version="4.3.2.v201101261720-797918s735435695C83"/> <unit id="org.eclipse.tptp.platform.core.feature.group" version="4.7.2.v201101261720-8X8ZFXoFLWUl6wn5veAISx"/> <unit id="org.eclipse.tptp.platform.jvmti.feature.group" version="4.5.1.v201009092123-797A38s7354466855B7"/> <unit id="org.eclipse.tptp.platform.trace.feature.group" version="4.5.2.v201101261720-7L7O8fBgJ9EC9NDREaF9"/> <unit id="org.eclipse.tptp.platform.xerces.feature.group" version="4.6.0.v201005032111-777K4AkF7B77R7c7N77"/> <unit id="org.eclipse.tptp.platform.instrumentation.ui.feature.group" version="4.3.2.v201101261720-797918s735435695C83"/> <unit id="org.eclipse.tptp.platform.probekit.feature.group" version="4.5.2.v201101271120-7H7BF8QAkF7B87RBVCFFD"/> <unit id="org.eclipse.tptp.platform.commons.logging.feature.group" version="4.5.0.v201005032111-2-37w312116191612"/> <unit id="org.eclipse.tptp.platform.jakarta.log4j.feature.group" version="4.5.0.v201005032111-217E7w312116191611"/> <repository location="http://download.eclipse.org/tptp/updates/helios/"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8436) JPA: validation of generic generator annotation isn't performed when it used with id mapping

by Dmitry Geraskov (JIRA)

JPA: validation of generic generator annotation isn't performed when it used with id mapping -------------------------------------------------------------------------------------------- Key: JBIDE-8436 URL: https://issues.jboss.org/browse/JBIDE-8436 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.x 1) Create mapping field in an entity: @Id @GenericGenerator(name = "my_generator", strategy = "wrong_strategy") private int id2; 2) Error expected, but nothing is shown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
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 2011