Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

[10:27:26 EST(-0500)] * JASIGLogBot (i=jasigch@jasigch.Princeton.EDU) has joined ##uportal
[10:27:55 EST(-0500)] <EricDalquist> weird, had to reboot the bot to get it to reconnect
[10:46:21 EST(-0500)] * EiNZTEiN (n=einztein@205.241.143.4) has joined ##uportal
[10:49:02 EST(-0500)] * lescour (n=lescour@129.244.24.211) has joined ##uportal
[11:03:38 EST(-0500)] <lescour> eric, do you know what release up-1873 (cas portlets) will target?
[11:04:26 EST(-0500)] <EricDalquist> if it happens in 2.X it would likely be a 2.6.2 release
[11:05:18 EST(-0500)] <lescour> thanks. i'm not having any success so far, using the code from the wiki
[11:06:20 EST(-0500)] <EricDalquist> :/ perhaps an email to the list detailing exactly what you've done and what you are seeing would be useful?
[11:06:24 EST(-0500)] <EricDalquist> I have never used the code
[11:06:34 EST(-0500)] <EricDalquist> just more participating at the conceptual level
[11:06:51 EST(-0500)] <EricDalquist> since we don't use CAS it is hard for me to test without setting up a whole environment
[11:07:01 EST(-0500)] <lescour> i replied back to jen asking her what steps were needed
[11:07:20 EST(-0500)] <lescour> so hopefully she will respond soon
[11:07:47 EST(-0500)] <EricDalquist> I saw that ... explaining what you've done/tried so far will likely get you a faster/more detailed response
[11:09:01 EST(-0500)] <lescour> ok. thanks
[11:10:07 EST(-0500)] * ac_chan (n=alex@tempoutsidepix.pratt.edu) has joined ##uportal
[11:10:13 EST(-0500)] <ac_chan> hello
[11:13:44 EST(-0500)] * jayshao (n=jayshao@72-254-4-169.client.stsn.net) has joined ##uportal
[11:20:18 EST(-0500)] <ac_chan> i am in the process of studying on customizing contributed classifieds channel ... i was wondering where i can get additional ifnormation on developing customized channels
[11:20:27 EST(-0500)] <ac_chan> other then the wiki on ja-sig.org
[11:20:59 EST(-0500)] <EricDalquist> the wiki and asking questions on uportal-user
[11:21:11 EST(-0500)] <ac_chan> ok
[11:21:14 EST(-0500)] <EricDalquist> or in here if there happen to be people with channel development experience
[11:21:37 EST(-0500)] <ac_chan> thanks.. reading through the source code right now of the classifieds channel
[11:21:42 EST(-0500)] <EricDalquist> I've really only done portlet development
[11:29:43 EST(-0500)] <ac_chan> i need to do more research before i barage the mailing list with questions.
[11:49:23 EST(-0500)] * awills (n=awills@uni1.unicon.net) has joined ##uportal
[11:50:00 EST(-0500)] <awills> morning folks... anyone care to brainstorm?
[11:50:19 EST(-0500)] <EricDalquist> about what?
[11:50:56 EST(-0500)] <awills> i intended to give the packaging on import/export tech more consideration at some point before checking it in
[11:51:06 EST(-0500)] <awills> seems like it might be a good time
[11:52:25 EST(-0500)] <awills> for starters... i had posed the question at the unconference: "does it make more sense to have these files spread throughout the classpath (as they are) or organized into a single package or package tree?"
[11:52:50 EST(-0500)] <EricDalquist> single package/tree
[11:53:34 EST(-0500)] <awills> yeah that's the answer i got more... and while it seems counterintuitive to me on some levels, it should would make it easier to track them all
[11:53:46 EST(-0500)] <EricDalquist> yup
[11:53:54 EST(-0500)] <EricDalquist> and they are not files that are part of the framework runtime
[11:53:57 EST(-0500)] <awills> what about org.jasig.portal.io?
[11:53:58 EST(-0500)] <EricDalquist> they are an aspect
[11:54:08 EST(-0500)] <EricDalquist> sounds good
[11:55:54 EST(-0500)] <awills> and beyond that... what about org.jasig.portal.io.v2_6_1 (subpackage) or something... it would be nice to make the versions of these files part of their location, 'cause i expect them to change as uPortal changes
[11:56:22 EST(-0500)] <EricDalquist> hrm
[11:56:36 EST(-0500)] <EricDalquist> doing versions in package names could get ugly
[11:56:49 EST(-0500)] <EricDalquist> so what is the use case for having multiple versions of the files ...
[11:57:05 EST(-0500)] <awills> here it is...
[11:57:10 EST(-0500)] <EricDalquist> so I could have uPortal 2.6.1 checked out and using code there export data for 2.5.0 and import into 2.6.1?
[11:57:36 EST(-0500)] <awills> everything that exports comes w/ a URL specifying the script that imports it
[11:58:19 EST(-0500)] <awills> so you could export stuff from 2.6 and it would basically declare that it's data in 2.6 format
[11:59:02 EST(-0500)] <awills> in the future, if data/format change, the old script location can merely transform (adding intelligent defaults for new stuff) and pass to the new script
[11:59:10 EST(-0500)] <awills> and the old files will be none the wiser
[11:59:19 EST(-0500)] <EricDalquist> ok
[11:59:53 EST(-0500)] <awills> should be very easy to go 2.6 -> 3.0, at least I hope (smile)
[12:00:04 EST(-0500)] <EricDalquist> so as changes to the import files are made (something changes about object foo from 2.6.1 to 2.6.2) you need the import for foo_2.6.1 as well as foo_2.6.2 right?
[12:00:33 EST(-0500)] <awills> right... but basically that looks like this...
[12:01:24 EST(-0500)] <awills> move the 2.6.1 version to 2.6.2, make your (minor) changes, add a new script to 2.6.1 that invokes the new location, transforming or adding stuff if necessary
[12:02:04 EST(-0500)] <awills> we could do it like this perhapps: org.jasig.portal.io.v2_6
[12:02:17 EST(-0500)] <awills> and org.jasig.portal.io.v3_0
[12:02:36 EST(-0500)] <awills> adding v2_6_3 etc only if something compells us to
[12:03:33 EST(-0500)] <esm> what about using a more oo approach and subclassing
[12:04:04 EST(-0500)] <esm> or interfaces with an impl for (say) 2.6.1 and another impl for 2.6.2
[12:04:43 EST(-0500)] <esm> i know zero about the import/export code so I don't know if its feasible
[12:04:46 EST(-0500)] <awills> well, i think what I'm looking at is a bit similar to that
[12:05:08 EST(-0500)] <esm> similar enough to not use separate packages for versions?
[12:05:21 EST(-0500)] <awills> the import/export tech in coded in Java but configured in XML
[12:05:23 EST(-0500)] <EricDalquist> sticking version numbers in the package names just seems ugly to me but I don't know the code either
[12:05:40 EST(-0500)] <awills> only the XML needs to be added to uPortal's classpath
[12:06:25 EST(-0500)] <awills> how about org.jasig.portal.io.import-user_v2-6.crn?
[12:06:40 EST(-0500)] <awills> and org.jasig.portal.io.import-user_v3-0.crn?
[12:06:45 EST(-0500)] <awills> does that look better?
[12:07:10 EST(-0500)] <esm> right i don't see a problem with the deployment or runtime, it just that if what you really want is one implementation for one version and other implementation for another version that interfaces and/or subclassing could be used to do that
[12:08:02 EST(-0500)] <esm> applicationContext.getBean( "crn-2.6-exporter" ) and applicationContext.getBean( "crn-3.0-importer" )
[12:08:07 EST(-0500)] <esm> something like that
[12:08:24 EST(-0500)] <esm> or
[12:08:34 EST(-0500)] <esm> lol
[12:08:38 EST(-0500)] <esm> sorry thinking of sienfeld
[12:08:58 EST(-0500)] <esm> ImporterExporter ie = appCtx.getBean( "importerexporter" )
[12:09:07 EST(-0500)] <esm> ie.setSource( "2.6" );
[12:09:13 EST(-0500)] <esm> ie.setTarget( "3.0" );
[12:09:21 EST(-0500)] <esm> george as the importer exporter
[12:09:23 EST(-0500)] <esm> hehehe
[12:09:52 EST(-0500)] <awills> there's no uPortal-specific Java code for import/export... just uPortal-specific configurations of Java code from other open source projects
[12:10:53 EST(-0500)] <awills> these configurations are in the form of XML, very similar (conceptually) to spring app contexts
[12:11:42 EST(-0500)] <awills> so imagine you have to include 2 app contexts for 2 different versions, and that they were going to live in the package tree
[12:11:46 EST(-0500)] <esm> oh so the stuff going under (say) org.jasig.portal.io.import-user_v2-6.crn are just resources (xm files)?
[12:11:55 EST(-0500)] <awills> how would you name them differently?
[12:12:03 EST(-0500)] <awills> that's right
[12:12:08 EST(-0500)] <esm> ahh ic
[12:12:08 EST(-0500)] <awills> .crn = XML
[12:12:41 EST(-0500)] <esm> sorry, i thought you were talking about adding java classes under the proposed packages
[12:12:59 EST(-0500)] <esm> and I took it to be a symtom of a greater issue that doesn't exist
[12:12:59 EST(-0500)] <esm> ok
[12:13:03 EST(-0500)] <awills> np... happy to explain what i'm doing where it's needed (smile)
[12:13:54 EST(-0500)] <esm> yeah I guess you need some way to name space the files
[12:15:03 EST(-0500)] <esm> so the files under o.j.p.i.import.* all have the same names?
[12:15:22 EST(-0500)] <awills> it only takes ~1500 lines of XML to handle import & export of users, groups, channels, memberships, permissions, layouts – and will be considerably less in 3.0 if eric gets JPA/Hibernate in there like he's looking at
[12:15:42 EST(-0500)] <EricDalquist> heh, none of the stuff you've listed will be using jpa/hib
[12:15:45 EST(-0500)] <EricDalquist> only the new daos
[12:15:57 EST(-0500)] <EricDalquist> which there will be 4 or 5 of
[12:16:01 EST(-0500)] <awills> they currently have names like import-user.crn, import-layout.crn
[12:16:18 EST(-0500)] <esm> would it work to just have one package (directory) with all the xml files and put version #'s in the file names? or is that too complex
[12:16:22 EST(-0500)] <awills> ah, new daos
[12:16:48 EST(-0500)] <awills> presumably for portlet defs & portlet instances
[12:16:52 EST(-0500)] <EricDalquist> yup
[12:16:57 EST(-0500)] <awills> cool
[12:17:01 EST(-0500)] <EricDalquist> the only existing daos that will get refactored are preferences
[12:17:07 EST(-0500)] <EricDalquist> I was thinking version numbers on files as well esm
[12:17:19 EST(-0500)] <EricDalquist> since it isn't like there will be new versions for every version of uportal
[12:17:20 EST(-0500)] <awills> like the earlier example?
[12:17:27 EST(-0500)] <EricDalquist> just when the OM changes
[12:17:31 EST(-0500)] <EricDalquist> which isn't that often
[12:17:31 EST(-0500)] <awills> no, it will be much rarer
[12:17:39 EST(-0500)] <EricDalquist> even between minor versions
[12:18:27 EST(-0500)] <awills> do you think people will frek out if they export from uP3 and it says it imports w/ v2-6?
[12:18:31 EST(-0500)] <awills> freak*
[12:18:47 EST(-0500)] <EricDalquist> probably not
[12:18:50 EST(-0500)] <awills> good
[12:19:03 EST(-0500)] <EricDalquist> perhaps include wording that these are ObjectModel versions
[12:19:14 EST(-0500)] <awills> yeah, i'll find a place to do that
[12:19:15 EST(-0500)] <EricDalquist> and the ObjectModel doesn't change at the same rate as uPortal
[12:19:21 EST(-0500)] <awills> yup
[12:19:34 EST(-0500)] <awills> are we on the same page then?
[12:20:27 EST(-0500)] <awills> oh and actually...
[12:20:48 EST(-0500)] <awills> it's really only the import script locations that have to be versioned and maintained...
[12:21:06 EST(-0500)] <awills> b/c a portal is really only responsible for exporting it's own flavor
[12:21:29 EST(-0500)] <EricDalquist> yup
[12:21:32 EST(-0500)] <EricDalquist> sounds great
[12:21:54 EST(-0500)] <awills> ok, i will work on that today
[12:22:04 EST(-0500)] <awills> won't take long
[12:22:29 EST(-0500)] <awills> eric i'm working w/ JHU the rest of this month on a 2.6 upgrade
[12:22:49 EST(-0500)] <EricDalquist> cool
[12:22:49 EST(-0500)] <awills> i've finally seen import/export working on MS SQL Server w/ my own eyes

  • No labels