Comments for A Java geek

Comment on CDI worse than Spring for autowiring? by Roger Parkinson

Roger Parkinson — Sun, 05 Feb 2012 22:28:29 +0000

Autowiring by type in Spring works okay for me. But I do use it very selectively. Where I have one bean ever of that type used in lots of places I tend to autowire that bean by type rather than clutter the XML file. Identifying such beans doesn’t give me a problem so far.
I think the only place I use autowire by name is in test code.
In a couple of cases I use the component-scan to define the beans and inject a list of them into a class. That’s more auto-defining than autowiring I guess. But it also reduces the XML clutter, so I think of it as similar.

Comment on Flamingo tutorial by alex

alex — Fri, 03 Feb 2012 13:38:07 +0000

Hello, I tried to add a change listener to my Ribbon but it doesn’t work. How can I detect the change of tab in my Ribbon ?

Thank you for your help.

Comment on Bean validation and JSR 303 by Siva

Siva — Wed, 01 Feb 2012 02:16:06 +0000

@Mohammad
You need to use ValidationGroups.

public interface CarChecks {
}

@NotNull(message = “The car name cannot be empty”, groups=com.CarChecks)
private String carName;

Comment on Adapters in JAXB by Andrew Fink

Andrew Fink — Tue, 31 Jan 2012 07:05:50 +0000

Try to ask http://blog.bdoughan.com/ – JAXB guru

Comment on Shoud you change your design for testing purposes? by Roger Parkinson

Roger Parkinson — Mon, 23 Jan 2012 07:08:03 +0000

For setting mocks I agree with you. I still use Spring and I use a different beans xml file to inject test mocks. Test code is in the same package. Sometimes I change a method from private to protected so that test code can call it directly for testing. In that case I’m changing the design. So I can see I should start using PrivateAccessor. I never do that to a setter, though.

But I do want to make the point that testability is part of the design. Before I used DI I had horrible designs from a testing point of view and a lot of my better design work came out of asking the question: How can I make this easier to test?

Comment on Bean validation and JSR 303 by jens

jens — Sat, 14 Jan 2012 20:21:55 +0000

hi, super hilfreicher Artikel!! Vielen Dank!! Viele Grüße Jens

Comment on Flamingo tutorial by Janavi Joshi

Janavi Joshi — Wed, 11 Jan 2012 12:00:39 +0000

@MuthuAnanth

Get all suppoerted Jar file here

http://javaswingcomponents.blogspot.com/2011/12/jribbon.html

Comment on Property editors by khong07

khong07 — Tue, 03 Jan 2012 11:33:49 +0000

Hi oliver, nicolas,

Could you give me an plain example with converter or propertyeditorregistar callback?

Because actually, i use stringarraypropertyeditor to convert string property to array with custom delimiter (so need constructor arg in stringarraypropertyeditor)

Many thanks.
Khong07

Comment on Flamingo tutorial by Nicolas Frankel

Nicolas Frankel — Wed, 28 Dec 2011 22:21:36 +0000

Your MainFrame class should extend JRibbonFrame, not JFrame. That should solve your problem.

Comment on Flamingo tutorial by Rene

Rene — Wed, 28 Dec 2011 22:13:12 +0000

Hi,
i know it is possible to use an own frame inheriting from JFrame and add a JRibbon component e.g. with BorderLayout.NORTH to this frame.
The ribbon is painted well and works except the application menu button. When the user presses it, there occurs the ClassCastException (see below).
Is there a workaround for this?

Regards René

Exception in thread “AWT-EventQueue-0″ java.lang.ClassCastException: de.lambdamoo.aha.client.main.MainFrame cannot be cast to org.pushingpixels.flamingo.api.ribbon.JRibbonFrame
at org.pushingpixels.flamingo.internal.ui.ribbon.appmenu.BasicRibbonApplicationMenuButtonUI$1.getPopupPanel(BasicRibbonApplicationMenuButtonUI.java:118)
at org.pushingpixels.flamingo.internal.ui.common.BasicCommandButtonUI.processPopupAction(BasicCommandButtonUI.java:1103)
at org.pushingpixels.flamingo.internal.ui.common.BasicCommandButtonUI$4.actionPerformed(BasicCommandButtonUI.java:1075)
at org.pushingpixels.flamingo.api.common.JCommandButton$DefaultPopupButtonModel.firePopupActionPerformed(JCommandButton.java:314)
at org.pushingpixels.flamingo.api.common.JCommandButton$DefaultPopupButtonModel.setPressed(JCommandButton.java:346)
at org.pushingpixels.flamingo.internal.ui.common.BasicCommandButtonListener.mousePressed(BasicCommandButtonListener.java:122)