Skip to main content

Java EE 7 Fixes Java EE 6's Absent Code

In a recent blog post, Adam Bien, has shown how the upcoming Java EE 7 api fixes issues that were present when testing applications against Java EE 6.

In Java EE 6, applications could be compiled against the Java EE 6 api using the javaee-web-api Maven artifact. As the classes in the maven artifact however were just stub classes they only allowed compilation and would not allow a set of tests to run against the api's outside of the application server.  This would cause ClassFormatErors such as

Caused by: java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class

The fix for this issue was to compile and run tests against a 3rd party EE 6 api rather than the standard such as described on this tip.

Adam has shown that this is no longer the case in EE 7, and using the official javaee-api Maven artifact will enable testing to be performed against the EE 7 api as expected.

Thanks Adam for the tip !

Comments

  1. [...] In a recent blog post, Adam Bien, has shown how the upcoming Java EE 7 api fixes issues that were present when testing applications against Java EE 6. In Java EE 6, applications could be compiled against the Java EE 6 ...  [...]

    ReplyDelete

Post a Comment

Popular posts from this blog

Creating a Joke Application in React

Introduction I've recently started learning React. I've been a backend developer for a long time, but have started to love doing client side work. As they say, the best way to learn is to practise. So here is a simple joke application that I've written in React. The source code for the application can be found on GitHub at: https://github.com/doobrie/react-joke Creating the project Whilst practising, I've quite often created projects from scratch, but this is quite tedious as the same steps need to be taken for each project. I needed to create the project structure, configure Babel, write some control scripts etc. Instead of doing that this time, I've used the create-react-app tool to scaffold the basics of an application. npx create-react-app This sets up everything that you need to get started with a React app. Coding As this is a simple project, I've created one react component, function app() . I've created this as a functional c...

Changing Default Search Provider in Firefox on Linux Mint

On Linux Mint, the default version of Firefox is installed and configured to allow the following search engines to be queried directly from the address bar: Yahoo! Startpage DuckDuckGo Wikipedia Mint defines these as the default available set of search engines based upon 3 criteria (funding to Linux Mint, privacy support and whether the search engine is non-commercial). Other search engines such as Google, Bing or Twitter, etc. can easily be added into the default version of Firefox however. To add a different search provider, browse to Search Engines At the bottom of the page, click on the icon of the requested search engine, then click on the ... button in the URL bar and select the Add Search Engine option. You then have the option to change the default search engine within Firefox preferences to your new choice.

The new Eclipse logo

In a blog post today, Ian Skerrett has announced the new logo for Eclipse. Last fall we [The Eclipse Foundation] started a process to  update the Eclipse logo . The existing logo had not been change since Eclipse was launched and it was showing its age. I am happy to announce we have finished the process and am pleased to introduce the updated Eclipse logo. The new logo has a fresh modern look to it, which I think is a good improvement and will stand Eclipse in good stead for the future. The new logo will be included with the next Eclipse release train, Luna, and gradually rolled out across the Eclipse site and projects. What do you think?  Do you like the new logo?  Add your comments below.