November 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2484) java.lang.NullPointerException when select Validate from context menu in Package Explorer

by Anton Klimkovich (JIRA)

java.lang.NullPointerException when select Validate from context menu in Package Explorer ----------------------------------------------------------------------------------------- Key: JBIDE-2484 URL: http://jira.jboss.com/jira/browse/JBIDE-2484 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Environment: WinXP 200807071935-nightly Reporter: Anton Klimkovich Assigned To: Alexey Kazakov EXECUTE: Create Seam War web project or JSF web project EXECUTE: Select Validate from context menu in Package Explorer for created project FAILURE: java.lang.NullPointerException at org.eclipse.jpt.core.internal.validation.JpaValidator.validationMessages(JpaValidator.java:55) at org.eclipse.jpt.core.internal.validation.JpaValidator.validate(JpaValidator.java:48) at org.eclipse.jpt.core.internal.validation.JpaValidator.validateInJob(JpaValidator.java:77) at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:78) at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:689) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:559) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:523) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:662) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:527) at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:100) at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:60) at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) 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, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2512) Problem with referencing libaries

by Marcin M (JIRA)

Problem with referencing libaries ---------------------------------- Key: JBIDE-2512 URL: http://jira.jboss.com/jira/browse/JBIDE-2512 Project: Tools (JBoss Tools) Issue Type: Bug Components: libmanagement Affects Versions: 2.1.2 Environment: Ububtu Linux 8.04 Reporter: Marcin M Fix For: 2.1.3 <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>SymNet-ear</display-name> <module> <web> <web-uri>SymNet.war</web-uri> <context-root>/SymNet</context-root> </web> </module> <module> <ejb>SymNet-ejb.jar</ejb> </module> <module> <ejb>jboss-seam.jar</ejb> </module> </application> such application.xml will work after patching the eclipse installation by mentioned in the thread patch. but if you want to have your librarites to be put inside a folder (eg. lib) the problem remains <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>SymNet-ear</display-name> <module> <web> <web-uri>SymNet.war</web-uri> <context-root>/SymNet</context-root> </web> </module> <module> <ejb>lib/SymNet-ejb.jar</ejb> </module> <module> <ejb>jboss-seam.jar</ejb> </module> </application> 15:41:21,000 ERROR [MainDeployer] Could not initialise deployment: file:/D:/Java/jboss-4.2.2.GA/serv er/default/deploy/SymNet-ear.ear/ org.jboss.deployment.DeploymentException: url file:/D:/Java/jboss-4.2.2.GA/server/default/deploy/Sym Net-ear.ear/jboss-seam.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214) at org.jboss.deployment.EARDeployer.init(EARDeployer.java:288) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja va:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentSc anner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja va:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja va:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2899) Allow export of server definitions without resetting launch config

by Gabriele Garuglieri (JIRA)

Allow export of server definitions without resetting launch config ------------------------------------------------------------------ Key: JBIDE-2899 URL: https://jira.jboss.org/jira/browse/JBIDE-2899 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.alpha Reporter: Gabriele Garuglieri Priority: Minor Currently we can export a JBoss Tools server definition using the default WTP server panel. There right clicking on the server opens a context menu whose last item is "Properties". Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project. The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done. The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations. (This is not strictly related but while you are at it, in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons). -- 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

16 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1634) Content Assist for "jsfc" attribute in facelets pages should sort proposals to have a list of available jsf components above other proposals.

by Alexey Kazakov (JIRA)

Content Assist for "jsfc" attribute in facelets pages should sort proposals to have a list of available jsf components above other proposals. --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1634 URL: http://jira.jboss.com/jira/browse/JBIDE-1634 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common Affects Versions: 2.0.0.GA Reporter: Alexey Kazakov Assigned To: Alexey Kazakov Fix For: 2.0.1 Testcase: EXECUTE: Create Seam WAR Project EXECUTE: Open home.xhtml EXECUTE: Insert <a jsfc="h:"></a> EXECUTE: Ctrl+Space in <a jsfc="h:| ASSERT: There are proposals with available JSF components in very top of the list: f:actionListener f:... h:... -- 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, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-814) Resource bundle completion works for <f:loadBundle> but doesn't work for <a4j:loadBundle>

by Adrian Mitev (JIRA)

Resource bundle completion works for <f:loadBundle> but doesn't work for <a4j:loadBundle> ----------------------------------------------------------------------------------------- Key: JBIDE-814 URL: http://jira.jboss.com/jira/browse/JBIDE-814 Project: JBoss Tools Issue Type: Bug Components: JSF Environment: rhds beta1, jdk 1.5_0.12, windows XP Reporter: Adrian Mitev -- 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, 4 months

5
21
0 / 0

[JBoss JIRA] Created: (JBIDE-1486) property rendered=false don't process

by Sergey Dzmitrovich (JIRA)

property rendered=false don't process ------------------------------------- Key: JBIDE-1486 URL: http://jira.jboss.com/jira/browse/JBIDE-1486 Project: JBoss Tools Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.0.GA Reporter: Sergey Dzmitrovich Assigned To: Maxim Areshkau Attachments: rendered_false_vpe.png if jsf, seam, richfaces component has property rendered="false". It is represented all the same. -- 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, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-3186) Add setting up of taglib using DND from palette

by Yura Zhishko (JIRA)

Add setting up of taglib using DND from palette ----------------------------------------------- Key: JBIDE-3186 URL: https://jira.jboss.org/jira/browse/JBIDE-3186 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Create a new jsp or xhtml page 2) DND some component from palette into visual pane (for example rich:calendar) ASSERT: Insert tag dialog should appear, taglib should be added automaticly at the top of the source pane, component should be rendered. ACTUAL: Insert tag dialog doesn't appear, taglib isn't added, component isn't rendered -- 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

16 years, 4 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-883) Clean out vpe plugins code

by Denis Golovin (JIRA)

Clean out vpe plugins code -------------------------- Key: JBIDE-883 URL: http://jira.jboss.com/jira/browse/JBIDE-883 Project: JBoss Tools Issue Type: Sub-task Reporter: Denis Golovin Assigned To: Sergey Vasilyev -- 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, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-863) Option for creating of page.xml file when selected jsp/xhtml file in the package explorer

by Adrian Mitev (JIRA)

Option for creating of page.xml file when selected jsp/xhtml file in the package explorer ----------------------------------------------------------------------------------------- Key: JBIDE-863 URL: http://jira.jboss.com/jira/browse/JBIDE-863 Project: JBoss Tools Issue Type: Feature Request Reporter: Adrian Mitev Priority: Minor Example: when /view/preview.xhtml file is selected, option that will create file /view/preview.page.xml -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2318) Case Sensitive Code Completion in JSF page editor

by Andy Gibson (JIRA)

Case Sensitive Code Completion in JSF page editor ------------------------------------------------- Key: JBIDE-2318 URL: http://jira.jboss.com/jira/browse/JBIDE-2318 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.1 Environment: JBDS 1.1.0 CR 1, JBoss Tools 2.1.1 GA (tested Both), Windows XP, Eclipse-Europa-Winter, brand new project Reporter: Andy Gibson There are some issues with case sensitivity in the code completion for Seam items. I'll attach a movie demonstrating this, but essentially, if you try code completion with : <h:outputText value="#{paramv"/> (lower case 'v' at the end) Then the value #{paramValues} will appear in the code suggestions. However, if you have : <h:outputText value="#{conversatione"/> (lower case 'e' at the end) Then #{conversationEntries} does NOT appear, but it will appear if I make the trailing 'e' an upper case 'E'. The conversationEntries and paramValues are available in a newly created project if you want to try and re-produce the problem. If I create a bean called "myBean" and type : <h:outputText value="#{myb"/> Then myBean does not appear but if you type ; <h:outputText value="#{myB"/> Then myBean does appear. The problem also extends into methods / attributes on the bean, so #{conversation.changeflush does not return anything. -- 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, 4 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2008