Ask questions and see you at 1st, February at 6.PM. CET: http://www.ustream.tv/channel/adambien Also see archives: airhacks.tv
- Management JSR-372
- JCache Integration JSR-107
- MVC JSR-371
Ask questions and see you at 1st, February at 6.PM. CET: http://www.ustream.tv/channel/adambien Also see archives: airhacks.tv
Hi Adam,
Which tool would you choose between maven3 and gradle for a JavaEE application.
The chosen tool has to support a continuous build and continuous integration system.
Next to the build process of artifacts we intend to drive unit tests, integration tests, system tests, functional tests - of course with additional tools.
Thanks a lot!
Petru
Hi Adam, some last-minute question (hopefully not too late for this evening) :-Þ:
Using JAX-RS sub resources example ,
it looks like new transactions aren't created automatically as it would be using e.g. @stateless on a
"normal" JAX-RS resource. Is there a way to circumwent this except creating transactions manually?
Thanks.
Hi Adam.
I would like to ask you what is the best strategy for REST API versioning (api/v1/.., api/v2/...).
Thank you very much.
Hi adam,
Is there a way to send a message to a particular user in a group chat using java websocket api.
How to measure concurrent user of system ?
We have development a mini banking system of using java ee. we have 150 branches per user . currently
we cannot calculated concurrent user for this system . what is the common best practice for finding concurrent user ?
what are common critical issues for enterprise system when run into production environment ?
we have development a JAVA EE7 application(mini banking solution.).
We use common architecture : JSF(presentation)+ CDI(service/dao)+ JPA + Wildfly 10
We have to go into production environment at April-2016. it this situation,
i want to know more about what are the common critical issue of Enterprise system(java ee) when run into live environment ?
give me some guideline for initial preparation
my idea is : critical issues
ui problem : Our one of application use spring mvc+jqery .
we also use huge jquery and json for ui scripting (send/retrieve/validation).
this application 300 page /form.
we almost finish our development , we are doing testing and facing one problem :
lots of silly bugs(ui) from different silly point .
From my understanding reason of this kind bug is :
use different ui in different style like : validation pattern, grid , form , masking, different type js plugin.
1. plain form(grid)/Tabbed form
2. inline edit grid
4. add to grid
5. cyle based grid
6. Search result grid / partial grid editing
But our maximum page has same category functionality.
How to organize our page /form minimum set of pattern
that perform easy maintenance in ui layer .
I have confusion about large scale financial application ui layout .
i have some idea but i am not clear here .
From my experience ,
this one of critical issue in enterprise application development .
how to use a common ui pattern for whole application ui ??
pls give me some suggestion how to minimize this problem
* this ui pattern provide UI designers and developers with a common way to think about the problem at hand and provide a baseline design that can be customized to your specific application needs*
Hi Adam,
I would like to know, what are your "live" experiences with "Architectural documentation". Do you write/produce something in your business-projects or is this topic left out by the companies?
Thanks,
Ulrich