- crosspostings removed - On Tue, 20 Nov 2001, tek1 wrote:
> with all the changes going on with ejb and evolution of other architectures > (jdo, soap, etc.), my head is in a whirlwind as to what to use. for now, > i've decided to go with ejb/jboss since it currently the most appropriate > architecture for my system. if its appropriate now, why would it suddenly become inappropriate? I think the important thing is to understand where your application is likely to lead, and understand the uses of the different technologies and their applicability to your current and future requirements. > however, with drastic changes to ejb2 (from 1.1, and certainly more changes > to come) and a lot of talk about jdo and soap (which i only have basic > understanding), i'm concerned with how many changes will be needed to be > made to the client app if one changes to a different architecture in the > near future. (uncertain of how ejb, jdo, and soap relate, how they will > all tie together, if at all...) if you're uncertain of how they tie together, I'd be hesitant to try and accomodate for them. > i've attached a rough uml diagram (as a .pdf file) with notes as to a > possible solution to help clients remain agnostic to the server-side > architecture. my knowledge of jdo and soap is still very low, so i'd > appreciate any insights to these technologies, their future, and ejb's > future from the more experienced system architects. what you are trying to do is a very valid effort. However, the KISS philosophy applies frequently. imho, choose something that works, and stick with it. measure twice - cut once sort of thing. > hope the diagram is understandable and make sense. yep, but I think it shows that you perhaps dont fully understand the issues involved. I see two: (a) remote client access (the fact that you are using a swing client), and (b) data persistence mechanism. ejb solves (a) & (b), jdo solves (b) and soap solves (a). remember when designing to separate out your program using a nice MVC design pattern. > if this is not appropriate for this mailing list, my sincere apologies. (o: ok... I personally accept your apologies... but I'll offer words that I hope are neither offensive, nor out of place. In general, this kind of discussion would be more suited to a *-interest list (as opposed to *-user). note that this is my personal view, and others might feel differently. I would also avoid crossposting, whilst I assume your intention was to reach other developers facing the same issues as you, some people (not me) dont appreciate it (o: fyi, the ejb-interest list would accomodate this discussion imho, to subscribe: Send an email to: [EMAIL PROTECTED] Set the first line of the BODY of the message to: "subscribe ejb-interest" ... the java forums (http://forums.java.sun.com) would also be suitable. > i really just want to jump into developing my system using just ejb and > forget about trying to make the client serverArchitecture-agnostic (which > could be more of a pain), but constantly seeing articles about jdo and soap > arouses concern... there is always going to be new stuff.... develop your system using what you know, and what you're good at. when you find something that is causing you grief, look at alternatives.... my 2c on it anyway. a bit of dribble here from me... probably not much help to you... but hope if gives you something. cheesr dim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
