xpages - How is your approach for creating your own set of controls aka own Extensions Library? -


what approach creating own set of controls aka own extensions library? after few years of xpages development have huge set of controls general purpose building ui, web services etc. (probably other developers.) when start new project have copy entire stuff 1 database new 1 involves controls, jars, css, images, java code ... , loose control maintain central version of controls & codes, scattered among several projects/databases , things messy fast.

we have thought creating our own extension library described here http://www-10.lotus.com/ldd/ddwiki.nsf/dx/master_table_of_contents_for_xpages_extensibility_apis_developer_guide there not enough documentation topic , entire development process quite complicated (at least seems me. tried 2 times based on docs above going through eclipse plugin project -> feature project -> update site , still having bugs around)

what experience , approach creating , maintaining shared xpages controls in domino environment? there hidden feature miss here can us?

take @ xsp starter kit on openntf , xpages sdk setup eclipse environment plugin development. you'll want eclipse ide rcp , rap developers. install starter kit , sdk eclipse , should set.

the starter kit sample plugin kinds of examples of phase listeners, components, etc. once want deploy plugin, create update site within eclipse , use update site nsf available on server install place update site. once that's done, can replicate nsf other servers may need plugin.

for more information starter kit, take @ this slide deck. there github project starter kit. documentation xpages sdk can found here. , video setting sdk available on youtube. lastly, here's documentation setting update site nsf.


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -