[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project
[
https://jira.jboss.org/jira/browse/JBIDE-5916?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5916:
---------------------------------
the default compiler lever is set by WTP according the version of jst.java project facet,
the default jst.java version is picked up from the ESB project facet definition, ESB
project facet definition set the java facet version to a range something like:
version="[5.0", so WTP pick up the lower version number as the default, as you
know, this is not ESB specific, all wtp project might have the same issue.
For ESB project, we can only change the ESB 4.7 definition by setting jst.java version
range to "[6.0", the project wizard will use 6.0 as java default version if ESB
4.7 only works with java 6.0
Wrong Compiler Compliance Level set when creating new ESB Project
------------------------------------------------------------------
Key: JBIDE-5916
URL: https://jira.jboss.org/jira/browse/JBIDE-5916
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.1.0.GA
Environment: JBDS 3.0.0v201002190339M-H173-CR2
Java Sun JDK 1.6.0_16-b01
JBoss [SOA] 5.0.0.GA_SOA (build: SVNTag=5.0.0.GA_SOA date=201002151345)
Reporter: Vlado Pakan
Assignee: Brian Fitzpatrick
Fix For: 3.1.0.GA, 3.2.next
Attachments: esbwizardpage.gif, esbwizardpage.gif, JBIDE-5916.patch,
JBIDE-5916.patch, JBIDE-5916.V2.patch, NewActionWizard.java.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When new ESB Project is created (File > New > Others > ESB Project) this project
has set Compiler Compliance Level to 1.5 (Project > Properties > Java Compiler) even
when only Java JDK 1.6 Runtime is specified within workspace.
Then when user adds new ESB Action to this project (File > New > Others > ESB
Action) it generates new class with this content (JBoss ESB Runtime jas to be added to
project classpath):
import org.jboss.soa.esb.actions.AbstractActionPipelineProcessor;
import org.jboss.soa.esb.helpers.ConfigTree;
import org.jboss.soa.esb.actions.ActionProcessingException;
import org.jboss.soa.esb.message.Message;
public class EsbAction extends AbstractActionPipelineProcessor {
protected ConfigTree _config;
public EsbAction(ConfigTree config) {
_config = config;
}
@Override
public Message process(Message message) throws ActionProcessingException {
//ADD CUSTOM ACTION CODE HERE
return message;
}
}
And compiler is complaining about @Override annotation on method process(Message)
displaying this error:
The method process(Message) of type EsbAction must override a superclass method
Either when Compiler Compliance level is set to 1.6 or Project Facets Java version is set
to 6.0 (Project Properties > Project Facets > Java) error disappear.
I think it should work in the way that when user creates new EBS Action it should be
created without errors so Compiler Compliance Level or Project Facets Java should be set
properly.
--
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