May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8884) NPE with Remote Deployment on Deploy Only Server

by Max Rydahl Andersen (JIRA)

NPE with Remote Deployment on Deploy Only Server ------------------------------------------------ Key: JBIDE-8884 URL: https://issues.jboss.org/browse/JBIDE-8884 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Final Environment: JBDS 4 / OSX Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M1, 3.2.1.M1 Been using Deploy only to deploy to servers but now it just stops working completely ;( Getting NPE's with the following errors in the error log: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.util.ServerConverter.getJBossRuntime(ServerConverter.java:120) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getRSEConfigName(RSEUtils.java:53) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:78) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:58) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.loadRemoteDeploymentDetails(RSEPublishMethod.java:159) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishStart(RSEPublishMethod.java:60) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:53) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:924) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Error publishing to org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior@179bf17 java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.util.ServerConverter.getJBossRuntime(ServerConverter.java:120) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getRSEConfigName(RSEUtils.java:53) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:78) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:58) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.loadRemoteDeploymentDetails(RSEPublishMethod.java:159) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishStart(RSEPublishMethod.java:60) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:53) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:924) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9023) Redeploying to AS7 after failed deployment fails because of .faileddeployment

by Joshua Wulf (JIRA)

Redeploying to AS7 after failed deployment fails because of .faileddeployment ----------------------------------------------------------------------------- Key: JBIDE-9023 URL: https://issues.jboss.org/browse/JBIDE-9023 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBTools nightly, Eclipse Reporter: Joshua Wulf When a deployment from JBoss Tools to AS 7 fails, a .faileddeployment file is written. When the app is redeployed, the .faileddeployment file is not erased, so it doesn't deploy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8948) AS7 Beta3 fails to stop

by Libor Zoubek (JIRA)

AS7 Beta3 fails to stop ----------------------- Key: JBIDE-8948 URL: https://issues.jboss.org/browse/JBIDE-8948 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Environment: JBossAS 7 Beta3 Reporter: Libor Zoubek Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M1 Installed JBT by following http://community.jboss.org/en/tools/blog/2011/05/12/jboss-tools-milestone.... AS fails to stop, details in .log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8906) jboss runtime detection doesn't spot AS 7 installations

by Max Rydahl Andersen (JIRA)

jboss runtime detection doesn't spot AS 7 installations ------------------------------------------------------- Key: JBIDE-8906 URL: https://issues.jboss.org/browse/JBIDE-8906 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.3.0.M1 Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Critical Fix For: 3.3.0.M2 using runtime detection and it doesn't recognize any of my jboss 7 installations. Should at least recognize JBoss 7 Beta4 or later. -- 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-8762) Subversion installation from JBoss Tools Requirements Update Site doesn't work properly

by Vlado Pakan (JIRA)

Subversion installation from JBoss Tools Requirements Update Site doesn't work properly --------------------------------------------------------------------------------------- Key: JBIDE-8762 URL: https://issues.jboss.org/browse/JBIDE-8762 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 3.2.1 Environment: Linux 32 bit, Java Sun JDK 1.6_24, jbosstools-3.2_stable_branch.aggregate-Update-2011-04-14_00-40-07-H703 Reporter: Vlado Pakan Assignee: Nick Boldt Install Subversion from this URL: http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.6/ Open SVN perspective and try to add some SVN location (http://anonsvn.jboss.org/repos/jbosstools/) Error window is displayed with title "Subversion Native Library Not Available" and error text is "Failed to load JavaHL Library. These are the errors that were encountered: no libsvnjavahl-1 in java.library.path no svnjavahl-1 in java.library.path no svnjavahl in java.library.path java.library.path = /usr/java/jdk1.6.0_24/jre/lib/i386/client:/usr/java/jdk1.6.0_24/jre/lib/i386:/usr/lib/xulrunner-1.9.2:/usr/lib/xulrunner-1.9.2:/usr/lib/xulrunner-1.9.2:/usr/lib/xulrunner-1.9.2:/usr/java/packages/lib/i386:/lib:/usr/lib" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
27
0 / 0

[JBoss JIRA] Created: (JBIDE-8844) AS7 management tools not added to build completely

by Rob Stryker (JIRA)

AS7 management tools not added to build completely -------------------------------------------------- Key: JBIDE-8844 URL: https://issues.jboss.org/browse/JBIDE-8844 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M1 Make sure as7 management tools are added to the build for stop functionality. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8597) Move from m2e 0.12 to 0.13 in trunk / 3.3.indigo branch

by Nick Boldt (JIRA)

Move from m2e 0.12 to 0.13 in trunk / 3.3.indigo branch ------------------------------------------------------- Key: JBIDE-8597 URL: https://issues.jboss.org/browse/JBIDE-8597 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Snjezana Peco Investigate moving from m2eclipse 0.12 [0] (currently mirrored here [1] and composited here [2], [3]) to 0.13 [4] [0] https://repository.sonatype.org/content/sites/forge-sites/m2e/0.12.1/S/0.... [1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/0.12/ [2] http://download.jboss.org/jbosstools/updates/indigo/ [3] http://download.jboss.org/jbosstools/updates/helios/ [4] https://repository.sonatype.org/content/sites/forge-sites/m2e/0.13.0/N/ Two major items to do: * [Sneja] work around GAV/package name changes (org.sonatype.* -> org.eclipse.*) * [Nick] set up new mirror / composite / target platform When you decide what version of m2e 0.13.* you want me to mirror, let me know and I'll add it to [2] and our 3.3.indigo branch target platform. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7281) Wizards should not allow user to select unsupported JAX-WS spec version

by Lukas Jungmann (JIRA)

Wizards should not allow user to select unsupported JAX-WS spec version ----------------------------------------------------------------------- Key: JBIDE-7281 URL: https://jira.jboss.org/browse/JBIDE-7281 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a dynamic web project with target runtime set to JBossAS6-M5 -create a ws client there with JAX-WS spec set to 2.1 and finish the wizard => generated code is of JAX-WS version 2.2 default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version. Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact the generated code is of version 2.2 jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o /tmp/fff -k http://footballpool.dataaccess.eu/data/info.wso?WSDL Could not find log4j.xml configuration, logging to console. WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS 2.1. log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). log4j:WARN Please initialize the log4j system properly. Loading FrontEnd jaxws ... Loading DataBinding jaxb ... wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff -allowElementReferences http://footballpool.dataaccess.eu/data/info.wso?WSDL wsdl2java - Apache CXF 2.2.10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8841) Implement Open-Ons on tag names of Seam config xml

by Viacheslav Kabanovich (JIRA)

Implement Open-Ons on tag names of Seam config xml -------------------------------------------------- Key: JBIDE-8841 URL: https://issues.jboss.org/browse/JBIDE-8841 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Affects Versions: 3.2.0.Final Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 For instance, for namespace xmlns:s="urn:java:ee" node <s:Qualifier/> is resolved to javax.inject.Qualifier, and open-on should open that type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8825) Parameter injection point should resolve taking into account member values of qualifiers

by Viacheslav Kabanovich (JIRA)

Parameter injection point should resolve taking into account member values of qualifiers ---------------------------------------------------------------------------------------- Key: JBIDE-8825 URL: https://issues.jboss.org/browse/JBIDE-8825 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 Consider the example: public class Test { @Produces @Named("abc") String abc; @Inject void setA(@Named("a") String s) { } @Inject void setABC(@Named("abc") String s) { } } Here, injection point in method setA should not be resolved to producer field abc, and injection point in method setABC should be resolved to it. Now, both injection points are resolved to abc. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2011