xManish schrieb:

Hi... Good to know there are people with common interest in embedding xwiki to existing project.

Here is my confusion. Please comment if you have idea on this. I have my J2EE project. It uses JSF, Spring and Hibernate. So I have my own hibernate.cfg.xml and web.xml and other config files. Now, I'm trying to add xwiki as a module to my project. Since Xwiki uses Struts and Hibernate, it also has its own hibernate.cfg.xml and web.xml files. How do I integrate these two now? Can I have both of these in my project and move on?

If I am able to work it out, I think I can move forward. I just learnt the way how we can delegate the struts action management to the spring framework.

Regards, Manish

Hi xManish, if you want to merge your project and xwiki into a single project you need to consider: 1. Will you have one database or two ? 2. How to merge the look and feel ? 3. How are you going to handle the different release cycles ? There is a long list of options for each of these steps and just heres just what comes to my mind: 1. Database Do you want to extend the XWiki database with your existing entity model ? Or are you going to save your entites within the existing generic Xwiki Datamodel ? If this is an option for you then why not just write XWiki applications instead of the spring/hibernate way ? If you don't want to extend XWiki db but have go with your own then you have to deal with 2 seperate Databases under spring transaction management regime ... 2. Look and feel How much JSFs / Spring Controllers are already written ? Again, if the answer is zero then why bother at all doing it this way ? It would be much simpler just writing some XWiki apps with velocity. It largely depends on - where the main app value comes from and what you expect from Xwiki being integrated with your app. - your level of knowledge of the internals of Xwiki and the other thechnologies - the state of your own app (beginning - legacy) As my app is also Spring / Hibernate based (I don't use JSFs but JSPs and the spring taglibs) for me this 'merge into a single project' approach in the sense of a single deployment (.WAR) seems to much effort. My focus is on 'making it feel' like a single project but keeping both completely apart. 2 apps, 2 databases. In front Apache Httpd to merge the namespaces. I just miss the 'single sign-on'-step. The level of interaction may not be that smart, but the effort should be pretty feasible. If your project is just beginning you might also consider of writing an XWiki application instead. Although the documentation is somehow basic and theres no literature except the xwiki-online stuff this seems to me a good option. And you will get pretty decent and timely support on this mailing list. have fun Andreas