• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

EJB 2.0 on Jboss 5.0.1 migration to EJB 3.0 wildfly 13.0.0Final. tier forgets previoius values?  RSS feed

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Greetings and salutations.

My native language isn't English and im pretty stupid when I talk about code but I want to improve.

I'm working on a migration Project thats is getting an odd behavioiur.

I'm getting a nullpointer exception.

The Project in itself is a 10+ ish year old JEE Project wich has been run on a JBOSS 5.0.1 server. The EJB's are 2.0 there are two of them.
The Project is a EAR file with one Web.war, one EJB.jar and one EJBClient.jar in it. objective is to switch the beans to 3.0 and to deploy this on a wildfly 13.0.0FINAL server.

After several guides and experiments how to make beans I've managed to create a 3.0 bean that I can call upon.

The Project when it worked pre migration have two session beans that are similiar in the build up. Ill show you the one im working on thats getting the problem.

The interface:

The implementation:

Targetable command:


CommandTarget: (Also contains my new Bean calls)

So this is the implementation basicly of the EJB and the EJB client. the implemenation of everythign except the session bean is in the client.
Now in the Web application we have a function that will call upon this long chain of commands. If its ok ill only show partial of it since it breaks in that part?

It breaks on the last line, the nullpointer.

When we did tests here - sysouts We saw taht both the cmd and the dto actually had values in them they got the proper information from the database. But once it returns to ActionidentitetKonsultCommand the dto is still empty. this works in the old code. the only change i did was i switched to my bean implementation wich is following:

and the interface:

Im guessing I've missed some sort of property somwere?
Thank you for your time

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!