[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project

[Vlado Pakan (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12516333#action_12516333 ] 

Vlado Pakan commented on JBIDE-5916:
------------------------------------

I have double check it.

Within JBDS I have only JDK 1.6 runtime defined. But anyways when I created esb project it has set Compiler Compliance Level to 1.5.

I'm using SOA-P runtime JBoss [SOA] 5.0.0.GA_SOA (build: SVNTag=5.0.0.GA_SOA date=201002151345). And the same runtime I defined as ESB runtime and specify as ESB runtime via New ESB Project wizard when creating new ESB project.

But JBoss ESB Runtime is not added to project classpath. It has to be added manually.

> 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.CR3
>         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.CR3, 3.1.1
>
>
> 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