What does this has got to do with Seam? What is the relation to Seam?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093880#4093880
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093880
It's not seam related actually but i think here is the best place to ask.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093881#4093881
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093881
And when i say the database will be changed every year - the idea is every
year to start with a clear for better performance.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093882#4093882
Reply to the post :
If you design your schema properly you probably shouldn't have to do anything
like this. How much data are you talking about?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093892#4093892
Reply to the post :
Like a 2 million records per in the tables
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093898#4093898
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093898
___
jboss-user
There will be a search for fields in the tables - like searching in a various
fields
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093907#4093907
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093907
That is not that many records, depending on what you want to do with them. As
long as they are properly indexed etc and you are not doing any full table
scans that should not be a problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093902#4093902
Reply
I also believe that DAO isn't necessary anymore. But I do believe that some
helper (or service) classes are a good thing.
You would get something like this:
| view layer
| |
| |
| business layer
| | |
| |
Yes, you are probably right. But creating such a view handler would probably be
a lot of work and complicated to build. But I still have the feeling that an
extra layer would be better. But it is a feeling and I can't really rational
base it on anything.
I am playing with Seam now, so I will
So you are saying that I could use the same Action classes to create a non-web
application with? I don't really see that. You already add a lot of annotations
to the Action class to let it communicate with the view, like the @In, @Out,
@DataModel, @DataModelSelection, etc...
View the original
smies wrote : So you are saying that I could use the same Action classes to
create a non-web application with? I don't really see that. You already add a
lot of annotations to the Action class to let it communicate with the view,
like the @In, @Out, @DataModel, @DataModelSelection, etc...
1) You can still add layers
2) jpdl pageflows let you remove the pageflow out of the pages.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3966069#3966069
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3966069
You could probably create three ejb libraries for layering.
- ejb lib for entities classes
- ejb lib for business classes
- ejb lib JSF action listeners and other web related classes
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3966102#3966102
Reply to the
13 matches
Mail list logo
