[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
[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
[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