Thanks for the help.
I read the link, but I dindt see an example doing the 3 points that you mentioned above
1.) create some session token
2.) create addressing properties using this token
3.) associate every request/response with this information
- The class that public the services is a Session Bean, isnt it?
- Can different clients for example .NET, PHP deal with this services properly. (because of addressing properties)
I would be grateful if you can show me an example about this, where session token and adressing properties are used.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993047#3993047
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993047
Hello,
I'm designing a J2EE application to interface a legacy app that uses partitioned tables on its database backend.
For instance 'tblBall_1', 'tblBall_2', etc......
In design terms the entity 'Ball' is a single entity which I want to represent as such in my class model.
Is there anyway to achieve this with EJB 3? Or are there any workarounds that others have used?
The only thing I can think of is to create a view to aggregate the tables together but I suspect this may run like a dog in production.
I found this post that seemed related to my question:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76591
but redesigning the database is not an option for me.
Any comments or suggestions would be greatly appreciated!
Tim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993042#3993042
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993042