Tuesday, 15 February 2011

XPage Osgi plug in development -



XPage Osgi plug in development -

background have designed many tools in past year or designed help me programme xpages. these tools include helper java classes, extended logging (making utilize of openlogger , own stuff), , few other things sense cannot work without. has been discussed employer, , sense might thought start publishing these items openntf. since these tools made of 3 .nsfs, designed utilize same java code, key javascript classes, css, , custom command or two, consolidate key items plug-in can installed @ server , client level. want consolidation before think publishing of work i've done far. far much work maintain, not me, potential users. have not found info on how such thing in google searches. have create sure able create utilize of extlib libraries, openntf domino api, , notes api.

my questions

how 1 best go designing such plug-ins? must designer utilize eclipse, or possible straight in notes designer? how designer best go keeping server , client date while designing , updating plug-in code? why github used? where best place material started in direction? sort of sense lost in woods, knowing need head north, not having compass first step.

thank much input.

in experience, found diving plug-in development huge pita until used it, it's worth overall.

as whether can utilize designer plugin development: yes, want not so. started out using designer sort of thing while, presumably same sentiment you: why bother installing instance of eclipse when i'm sitting in 1 day? however, between designer's age (it's equivalent to, think, eclipse 3.4), oddities when comes working sets between "applications" , "project explorer" views, and, in case, want utilize mac app, ended switching.

there 2 major starting points: xsp starter kit (http://www.openntf.org/internal/home.nsf/project.xsp?name=xsp%20starter%20kit) , niklas heidloff's video on setting eclipse xpages development (http://www.openntf.org/main.nsf/blog.xsp?permalink=nhef-8rvb5h). latter mentions xpages sdk (http://www.openntf.org/internal/home.nsf/project.xsp?name=xpages%20sdk%20for%20eclipse%20rcp), useful. in setup, found video largely useful, aspects either hard find (ibm's downloads shifting sands) or optional (debugging, depend on whether or not you're using eclipse on windows).

those resources should set up. main thing worry when setting eclipse environment making sure plug-in execution environment done. if you're next sdk setup instructions, should need be.

the next thing know way plugins structured. each plugin want install in designer or domino paired feature project (a feature can house several plugins), , potentially update site - lastly 1 optional if want import features update site nsf. that's how normal plugin development: export paired feature directory , import feature server's update site nsf , install in designer there using application -> install. can set things deploy server's plugin/feature directories instead of taking step of installing update site if you'd prefer. github doesn't come play aspect - it's more sharing/collaborating code , having remote storage location git repositories (which highly advise).

and "lost in woods" feeling: yep, you'll have while. there lots of moving parts , esoteric concepts hold of @ once. if follow above links , start basics xsp starter kit (which plugin project can pair feature) - say, printing text in activator class , making implicit global variable create sure works - should help feet wet.

osgi xpages xpages-extlib

No comments:

Post a Comment