Hi!
I’m not sure if combining Struts and X-Application is a good idea. I’ve seen a work student doing exactly this and the resulting architecture was very complex. Technically, it’s challenging to make them both live in the same web-application. The both have their own idea how to design web-applications - and either design kind of rules out the other.
In my optionion, X-Application is fine for simple applications (mostly create/read/update/search) xml data. If you think your business logic fits into what plugin offer, you should do it with X-Application only - no structs. Otherwise, if you can’t see a solution for your logic, use struts only - no X-Application; you’d have to use Tamino’s Java API, but this gives you full power and the resulting design is much simpler. If Struts is a prerequisite for your project: use Structs+Tamino API, no X-Application.
Michael
Business Logic in JSP pages: from X-Application’s point of view, business logic should go into plugins, the JSP page is just the “GUI” to activate it.
Software AG Germany, Darmstadt
#Tamino#webMethods#API-Management