2nd Airhacks Q&A And The Answers Are:

2nd airhacks.io edition, >10 answered questions, scheduled for 0.5h, recorded 1h. Thanks for all the interactions during the show!

Caused by EventTooLongException, the following questions remained unanswered and are going to be covered during the Airhacks.io "June" edition (June, 2nd, 6 P.M.):

  1. Joker question (a topic which bothers me, but unfortunately no one asked a question so far :-))

Write your questions as comments to this post, drop me a tweet or write a comment on my youtube channel: https://www.youtube.com/user/bienadam. I will pick again the 10 most recent questions and will answer them at the next edition of Airhacks Q & A.

Testing (unit <-> integration) and quality seems to be still a hot topic, so I scheduled a special, regular (offline) event at MUC this summer: http://workshops.adam-bien.com/about-testing.htm. There are already registrations available, so hurry up!

See you at the regular Java EE Workshops at MUC Airport and particularly at Java EE Architectures. ...and live each first Monday of the month at 6 P.M (CET) http://airhacks.io!

See also other screencasts at: http://adam-bien.tv or subscribe to http://www.youtube.com/user/bienadam.


Great video Adam! Really helpful!

I have one question regarding the co-existence of Spring and Java EE components in the same application.

On my current project we have a spring-based application, where all the business logic is implemented using spring beans. Due to new requirements we want to expose some of the business logic as SOAP web-services.

The application is running on WAS 8.5 and JEE6. I want to implement the webservice-endpoints as simple plain JEE @Webservice JAX-WS components, and let the endpoints delegate incoming calls to the spring bussiness components in the spring runtime.

What do you generally see as the potential problems when components call each other across different run time environments like this (jee->spring)? Is it a bad idea and should we just stick with pure Spring?

Posted by Jørgen Ringen on May 09, 2014 at 08:35 AM CEST #

What are you using to record your sessions? Do you need to do something special to layer yourself in the lower-right corner of your screen capture? I imagine you sitting in front of a big green screen.

The video/audio is very nice quality and the lack of distractions due to low quality makes for a great user experience.


Posted by Mark on May 09, 2014 at 08:45 PM CEST #

Regarding constructor injection:

For beans that are proxied a no-argument default constructor is required. This applies to no-interface EJBs as well as CDI beans in request or session scope.

So you would have one constructor for injection and one for proxying:

public RateCalculator(CountryRate countryRate){
this.countryRate = countryRate;

// for proxying
public RateCalculator() {
this.countryRate = null;

See also this question on Stackoverflow:

I believe in Spring 4 this is solved with more aggressive proxying using Objenesis.

Posted by Arend v. Reinersdorff on May 10, 2014 at 03:42 PM CEST #

What are the best practices to avoid naming conflicts with backing beans in JSF?
Let's say there is a backing bean com.project.flight.boundary.Booking.java with @Named("booking").
And there is another backing bean com.project.car.boundary.Booking.java @Named("booking").

This will lead to a naming conflict in the JSF page. How is this supposed to be resolved? Sure I can use two different names, but is there a way to add e.g. some namespace like the package in EL to make these two backing bean names unique?
How do larger projects/teams deal with this possible conflict?


Posted by Reto Hotz on May 23, 2014 at 05:10 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments