[JBoss JIRA] Created: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project
5:59 a.m.
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
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
Fix For: 3.1.0.CR2
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
6:01 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Vlado Pakan updated JBIDE-5916:
-------------------------------
Fix Version/s: (was: 3.1.0.CR2)
Affects Version/s: 3.1.0.CR2
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.CR2
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
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
8:17 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Rydahl Andersen updated JBIDE-5916:
---------------------------------------
Fix Version/s: 3.1.1
3.2.next
Affects Version/s: 3.1.0.CR3
(was: 3.1.0.CR2)
Assignee: Brian Fitzpatrick
Unless the ESB wizard is stupid then it should simply be using the defaults as specified
in the IDE - are you saying it it is enabling project specific settings and forces Java 5
compiler compliance even though your IDE is set to Java 6 ?
Or is the global default also Java 6 for you ?
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.1, 3.2.next
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
8:17 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Note, you say ESB jars has to be added to the project classapth ....the ESB project wizard
is supposed to add the runtime so they get their automatically...?
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.1, 3.2.next
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
8:19 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Rydahl Andersen updated JBIDE-5916:
---------------------------------------
Fix Version/s: 3.1.0.CR3
(was: 3.2.next)
marking for CR3 since it sounds that esb wizard is not creating a project with ESB
available, but I hope this is just funky eclipse defaults.
p.s. you are using a SOA-P runtime, right ?
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
8:35 a.m.
New subject: [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...
]
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
2:07 p.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
Ok, I'm still at a loss as to why this occurs, but I can tell you specifically what
fixes it from a file settings point of view.
There are two files in [project]/.settings/ that need to be changed:
1. org.eclipse.jdt.core.prefs
Change the lines:
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
org.eclipse.jdt.core.compiler.compliance=1.5
org.eclipse.jdt.core.compiler.source=1.5
To:
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6
org.eclipse.jdt.core.compiler.compliance=1.6
org.eclipse.jdt.core.compiler.source=1.6
2. org.eclipse.wst.common.project.facet.core.xml
Change the line:
<installed facet="jst.java" version="5.0"/>
to
<installed facet="jst.java" version="6.0"/>
Once those changes have been made, simply do a clean/rebuild and the errors go away.
The only place that I see any references to "5.0" are in the project facet
definition in the plugin.xml of org.jboss.tools.esb.project.core. For each version of
jst.jboss.esb defined, there's a constraints section that refers to the facet
"jst.java" that says it must be at the level 5.0 or above (version =
"[5.0"). This jives with the WTP documentation here:
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.wst.doc.isv/r...
which says "version - Specifies the match expression for the facet version. The
expression should be of the form "2.2,2.5,[3.0-5.3],(7.3", where the commas
function as an OR. Brackets and parenthesis are used as part of the range notation. A
bracket means inclusive while a parenthesis means exclusive."
<project-facet-version
facet="jst.jboss.esb"
version="4.7">
<group-member
id="modules">
</group-member>
<constraint>
<and>
<conflicts
group="modules">
</conflicts>
<requires
facet="jst.java"
version="[5.0">
</requires>
</and>
</constraint>
</project-facet-version>
Messing with the requires version doesn't seem to do any good.
Max recalled a similar issue from a while back
(https://jira.jboss.org/jira/browse/JBIDE-1647) that was similar to this.
I'm open to suggestions here. Nothing I've tried has remotely worked.
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
2:09 p.m.
New subject: [JBoss JIRA] Assigned: (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...
]
Brian Fitzpatrick reassigned JBIDE-5916:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Brian Fitzpatrick)
Max, not sure where else to go with this one.
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: Max Rydahl Andersen
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
4:40 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Rydahl Andersen updated JBIDE-5916:
---------------------------------------
Assignee: Viacheslav Kabanovich (was: Max Rydahl Andersen)
Ok, so there are two issues here, one easy to fix, and one a bit trickier.
1) We should not add @Override by default to the implementation because
@Override is only possibly to put on interface method in Java 6, not Java 5.
Slava, could please attach a patch that will remove the @Override annotation for the
action and assign back to me ?
For those who care here are the links that convinced me of the above:
Java 6 @Override snafu:
http://dertompson.com/2008/01/25/override-specification-changes-in-java-6/
http://blogs.sun.com/ahe/entry/override_snafu
ESB API doc showing what is interface and what is class:
http://www.jboss.org/file-access/default/members/jbossesb/freezone/docs/4...
http://www.jboss.org/file-access/default/members/jbossesb/freezone/docs/4...
2) The ESB project wizard seems to hardcode the default Facet configuration for EAP and
does not provide any way
to modify the configured setup (look at dynamic web project or Seam project here is a
combo and modify button to let user configure the facets used during project creation)
Since EAP 5 doesn't exist in a Java 5 version (we should check that ?) the default for
facet configuration of EAP (and by consequence also SOA-P) should thus be Java 6.
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: Viacheslav Kabanovich
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
4:49 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Note, the setup issue is not really ESB specific, the issue is just that ESB is forcing
the defaults (no modify button) and ESB action wizard generates Java6 only code.
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: Viacheslav Kabanovich
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
4:56 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Double Note, the reason Action should not generate Java 6 is that this also should work
on SOA-P 4.3 or standalone ESB which is still not tied to Java6
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: Viacheslav Kabanovich
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
7:04 a.m.
New subject: [JBoss JIRA] Assigned: (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...
]
Viacheslav Kabanovich reassigned JBIDE-5916:
--------------------------------------------
Assignee: Max Rydahl Andersen (was: Viacheslav Kabanovich)
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: NewActionWizard.java.patch
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
7:04 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Viacheslav Kabanovich updated JBIDE-5916:
-----------------------------------------
Attachment: NewActionWizard.java.patch
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: Viacheslav Kabanovich
Fix For: 3.1.0.CR3, 3.1.1
Attachments: NewActionWizard.java.patch
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
7:53 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Rob Stryker updated JBIDE-5916:
-------------------------------
Attachment: JBIDE-5916.patch
The attached patch refuses EAP 5.0 the ability to accept jst.java facet versions under
6.0. This automatically pushes compiler compliance up and removes the error. I cannot
verify for certain that this *actually* removes the error, though, for reasons I will
state below, however bfitz states that if compliance is 6.0, then the override should not
cause an error.
I will say trying to test this is absolutely infuriating, the most difficult part being
trying to figure out how to get my project to actually get an ESB classpath container onto
it, even with the presence of an EAP.
When I am in the first page of the esb project wizard, automatically selected is my JBoss
EAP 5.0 Server Runtime. Below it is also automatically selected "ESB Version:
4.7". Yet when I push forward two pages, it tells me my server does Not have esb 4.7
in it, I then have to go back two pages and change the facet version, then forward two
pages to see if the error has disappeared.
I finally gave up, as it one by one informed me that I do not have a satisfactory version
in my EAP 5.0 runtime at all, which I find as extremely unlikely. At at least one attempt
told me I did not even have a runtime selected, when the UI clearly did. (I eventually
got confused enough that I did a du -a | grep -i "esb" command to see if the
eap server had any jars or anything that mentioned "esb" anywhere in the file
name. None did. So now I'm wondering if my install is just odd, but I don't
suspect it is.
I decide to switch to not using the "Server supplied runtime" and instead
creating a new one on the third page, and I again pointed to my jboss-eap-5.0 folder. At
no point did *this* dialog inform me that none of the versions were found. Instead I, once
again, had to select each of the 6 versions to find out none were valid for this folder.
I finally pointed directly to an actual esb server (jbossesb-server-4.4.GA) and hte dialog
did auto-fill itself in, though I also remember *I* was hte one who made that fix about 2
months ago after a similarly infuriating attempt at this.
However even after I do this, I notice in my Package Explorer that there is *NO* classpath
container containing any ESB jars on hte project. So I check the .classpath file ot see if
ANYTHING was added at all, and I see this:
<classpathentry kind="con" path="server.supplied/SomeName"/>
Aside from the ridiculously short and uninformative name "server.supplied", the
adept user will note that this entry was not, actually, server supplied at all, but rather
the *other* option, as I outlined abouve and pointed directly to an esb installation.
Aside from that, this "server.supplied" is directly visible in the Java Build
Path property page, under the Libraries tab. Which means this constant is exposed to
users to see.
Anyway, I've just continued testing and magically got a configuration that "just
worked" (still not sure how). I can verify the @Override is still there, and there is
no error.
The end. Use the patch. And for god sakes please fix this wizard
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: JBIDE-5916.patch, NewActionWizard.java.patch
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
7:59 a.m.
New subject: [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...
]
Rob Stryker commented on JBIDE-5916:
------------------------------------
I was clearly making a mistake and using EAP when i should have been using SOAP. The
wizard should note this and not leave it ambiguous to me.
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: JBIDE-5916.patch, NewActionWizard.java.patch
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
9:25 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Rob Stryker updated JBIDE-5916:
-------------------------------
Attachment: JBIDE-5916.V2.patch
This is the real patch sorry
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: JBIDE-5916.patch, JBIDE-5916.V2.patch, NewActionWizard.java.patch
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
10:33 a.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
I have spun off the wizard validation issues into JBIDE-5936
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: JBIDE-5916.patch, JBIDE-5916.V2.patch, NewActionWizard.java.patch
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
5:36 a.m.
New subject: [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...
]
Viacheslav Kabanovich commented on JBIDE-5916:
----------------------------------------------
I have applied NewActionWizard patch to CR3.Annotation @Override will be generated or not,
according to the project settings, following the same logic as New Java Class wizard.
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: JBIDE-5916.patch, JBIDE-5916.V2.patch, NewActionWizard.java.patch
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
8:56 a.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
Just have to wait for the next good build...
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: 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
8:56 a.m.
New subject: [JBoss JIRA] Resolved: (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...
]
Brian Fitzpatrick resolved JBIDE-5916.
--------------------------------------
Resolution: Done
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: 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
8:56 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Brian Fitzpatrick updated JBIDE-5916:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
I believe both aspects of this bug have been committed. So we should be able to close it
as fixed...
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.1.1
Attachments: 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
1:09 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Brian Fitzpatrick updated JBIDE-5916:
-------------------------------------
Fix Version/s: 3.2.next
(was: 3.1.1)
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.2.next
Attachments: 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
5:15 a.m.
New subject: [JBoss JIRA] Reopened: (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...
]
Vlado Pakan reopened JBIDE-5916:
--------------------------------
Tested on jbdevstudio-eap-linux-gtk-3.0.0.v201003050335M-H45-CR3.
Compiler Compliance Level on newly created ESB project is still set to 1.5 even when only
JDK v1.6 Java Runtime is defined.
Action File is generated properly without @Override annotation.
ESB Runtime is added properly to project
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.2.next
Attachments: 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
2:51 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5916:
----------------------------
Attachment: JBIDE-5916.patch
This patch is enable the modify button for change project facets on the first page of ESB
project wizard
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.2.next
Attachments: 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
2:54 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5916:
----------------------------
Attachment: esbwizardpage.gif
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: Max Rydahl Andersen
Fix For: 3.1.0.CR3, 3.2.next
Attachments: 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
3 a.m.
New subject: [JBoss JIRA] Assigned: (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 reassigned JBIDE-5916:
-------------------------------
Assignee: Brian Fitzpatrick (was: Max Rydahl Andersen)
Can you review the patch to see if it works? thanks.
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.2.next
Attachments: 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
8:15 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Denny, what branch is this a patch against ?
What does "enable the modify button" have to do with setting the jst.facet to
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.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.2.next
Attachments: 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
10:37 p.m.
New subject: [JBoss JIRA] Updated: (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 updated JBIDE-5916:
----------------------------
Attachment: esbwizardpage.gif
Max, the patch is against trunk, it provides a chance to modify the version
jst.java.facet to 6.0. see attached screenshot of the wizard page.
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
7:42 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Denny, enable the Modify button is a *separate* issue. Please put in a separate issue and
let this issue be about having correct compiler level set by default.
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
2:53 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-5916:
--------------------------------------------
Brian, now that JBIDE-6056 is separated out - is there anything left on this issue ? Is
the default correct ?
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
2:55 a.m.
New subject: [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
3:36 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Rydahl Andersen updated JBIDE-5916:
---------------------------------------
Fix Version/s: 3.1.1
(was: 3.1.0.GA)
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.1, 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
3:18 p.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
So Denny was JBIDE-5916.V2.patch ever applied to both the trunk and the 3.1.x branch?
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.1, 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
2:44 a.m.
New subject: [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:
---------------------------------
JBIDE-5916.V2.patch was created by Rob and it only changes the plugin
org.jboss.ide.eclipse.as.core, it's Rob's code, I think Rob might have done.
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.1, 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
11:26 a.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
So what are you suggesting then Denny? Just the UI fix and not the facet fixes?
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.1, 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
1:41 a.m.
New subject: [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:
---------------------------------
Brian, I think the UI fix is enough and I don't think we can fix it by changing facet
definition, see JBIDE-6056.
I think we can close this issue and focus on JBIDE-6056
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.1, 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
9:27 a.m.
New subject: [JBoss JIRA] Resolved: (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...
]
Brian Fitzpatrick resolved JBIDE-5916.
--------------------------------------
Resolution: Done
Closed, focusing on the solution in JBIDE-6056
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.1, 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
9:27 a.m.
New subject: [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...
]
Brian Fitzpatrick commented on JBIDE-5916:
------------------------------------------
Denny, that actually sounds good. Let's close this issue and focus on JBIDE-6056
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.1, 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
5:15 a.m.
New subject: [JBoss JIRA] Closed: (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...
]
Vlado Pakan closed JBIDE-5916.
------------------------------
Verified on JBossTools-Update-3.1.0.v201004291720R-H72-GA.
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.1, 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
11:27 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project
[
https://jira.jboss.org/browse/JBIDE-5916?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick reopened JBIDE-5916:
--------------------------------------
Wrong Compiler Compliance Level set when creating new ESB Project
------------------------------------------------------------------
Key: JBIDE-5916
URL: https://jira.jboss.org/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.1, 3.2.x
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:29 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project
[
https://jira.jboss.org/browse/JBIDE-5916?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-5916:
-------------------------------------
Fix Version/s: 3.2.0.M1
(was: 3.2.x)
Wrong Compiler Compliance Level set when creating new ESB Project
------------------------------------------------------------------
Key: JBIDE-5916
URL: https://jira.jboss.org/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.1, 3.2.0.M1
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:29 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project
[
https://jira.jboss.org/browse/JBIDE-5916?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick closed JBIDE-5916.
------------------------------------
Resolution: Done
Wrong Compiler Compliance Level set when creating new ESB Project
------------------------------------------------------------------
Key: JBIDE-5916
URL: https://jira.jboss.org/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.1, 3.2.0.M1
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5768
days inactive
5892
days old
jbosstools-issues@lists.jboss.org
41 comments
6 participants
participants (6)
-
Brian Fitzpatrick (JIRA) -
Denny Xu (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)
-
Viacheslav Kabanovich (JIRA)
-
Vlado Pakan (JIRA)