Thx for your comment. I’ll try to find some time coming days to give you an answer/feedback.

Thx for your comment. I’ll try to find some time coming days to give you an answer/feedback.

You pointed me here from a post on the Glassfish forum.

This is a nice blog entry. I really wish I’d have seen it about a month ago since I ended up struggling through the same thing on my own. I have a couple of questions if you don’t mind.

I use a very similar project structure, except I don’t have an equivalent to your ‘my-services’ module. Would you mind explaining the concept behind that module? I assume it’s so you can add more ‘business-services’ type modules later without having to reproduce the basic functionality of ‘my-services’ or (maybe worse) mix EJBs from different ‘business-services’.

Also, I tend to split my remote interfaces into separate modules. Using your structure as an example, I’d have:

‘my-entities’
‘my-business-services-api’
‘my-business-services-impl’

Do you have any thoughts on whether or not such a design adds any benefit? It’s not necessary to distribute the ‘my-business-services-impl’ module with application clients, but I’m starting to wonder if it’s worth the hassle of having an extra module for it.

As for the question I was asking on the GF forums, I was asking about combining all of the annotations because I’d like to have the ability to build two UI clients for my app. I’d like to (be able to) build one in Adobe Flex using webservices and one in Java using remote EJBs.

I’d only develop one UI for my app at the moment and have a partially developed Java Swing UI, but I’ve decided to take a week and assess the viability of moving to Flex as a front end technology. I was hoping to mix annotations temporarily so I could re-implement a portion of my UI in Flex and compare the two techs.

After reading your blog post I’m thinking the best strategy for me will be to add an EJB module similar to your ‘my-services’ module and keep adding ‘my-business-services’ style modules for each UI type since it’s very unlikely I’d actually end up writing two UIs using different tech but the same requirements. For example:

‘my-web-services’ (Flex UI)
‘my-remote-ejb-services’ (Java UI)

I apologize if my comment seems a bit long winded. I’d appreciate any feedback you can give me, even if it’s harshly worded criticism.

You pointed me here from a post on the Glassfish forum.

This is a nice blog entry. I really wish I’d have seen it about a month ago since I ended up struggling through the same thing on my own. I have a couple of questions if you don’t mind.

I use a very similar project structure, except I don’t have an equivalent to your ‘my-services’ module. Would you mind explaining the concept behind that module? I assume it’s so you can add more ‘business-services’ type modules later without having to reproduce the basic functionality of ‘my-services’ or (maybe worse) mix EJBs from different ‘business-services’.

Also, I tend to split my remote interfaces into separate modules. Using your structure as an example, I’d have:

‘my-entities’
‘my-business-services-api’
‘my-business-services-impl’

Do you have any thoughts on whether or not such a design adds any benefit? It’s not necessary to distribute the ‘my-business-services-impl’ module with application clients, but I’m starting to wonder if it’s worth the hassle of having an extra module for it.

As for the question I was asking on the GF forums, I was asking about combining all of the annotations because I’d like to have the ability to build two UI clients for my app. I’d like to (be able to) build one in Adobe Flex using webservices and one in Java using remote EJBs.

I’d only develop one UI for my app at the moment and have a partially developed Java Swing UI, but I’ve decided to take a week and assess the viability of moving to Flex as a front end technology. I was hoping to mix annotations temporarily so I could re-implement a portion of my UI in Flex and compare the two techs.

After reading your blog post I’m thinking the best strategy for me will be to add an EJB module similar to your ‘my-services’ module and keep adding ‘my-business-services’ style modules for each UI type since it’s very unlikely I’d actually end up writing two UIs using different tech but the same requirements. For example:

‘my-web-services’ (Flex UI)
‘my-remote-ejb-services’ (Java UI)

I apologize if my comment seems a bit long winded. I’d appreciate any feedback you can give me, even if it’s harshly worded criticism.