Re: Some progress

This progress email is a great idea, this way i can keep track of the 
changes and new stuff that you're up to. Makes my job a little easier :o)

Anyway, i've been busy with tests also. I've finally been able to 
"master" de IntelliJ testing framework to create some decent tests. I 
actually ended up not using the open test framework but had to use the 
internal API as the current open api doesn't allow me to do what i want, 
got lot's of help from the IntelliJ guys to achieve this.

I hope to attack the classpath resource this weekend. I think i've got a 
decent implementation of the context resources stuff. I actually took 
the approach of allowing several roots for the web context, just like 
the classpath. I did this because IntelliJ let's you very easily 
configure several context roots for your web application. In fact, the 
default web application is generated with two context roots, so it made 
all the sense in the world to implement tapidea following the same approach.


Cheers

Hugo

Geoff Longman wrote:
> Since the spindle project seems like a black hole lately, I'm going to
> send a note to this list after every session. It would be rare that
> one of these notes would be worthy of a blog entry. Doing this is as
> much to inform the interest as to remind myself that yes, I am making
> progress.
>
> Wednesday was release day at the day job and I didn't get away until after 11pm
>
> Yesterday I was worn out after wednesday + several days of late night
> spindl'n so I packed it in early and went to bed for a change
> (7:30pm!)
>
> Tonight, I made some changes in the interface of the IDOMModelSource.
> The parse methods now take an ICoreResource. I didn't plan on doing
> this but I'm thinking about how elements of specs are going to have
> location buts coming from all over the place (like an annotated class
> or super interface) long story - hope to fill in the blanks soon.
>
> Added a skimpy (but to be improved as tests are written)
> implementation of a JarClasspathRoot/JarClasspathResource combo. this
> is the java/tests/ dir of spindle-core.
>
> Intend to use it to test things like NamespaceResolvers. The Framework
> library is large and intricate - a good target for later comprehensive
> NamespaceResolver tests. As an added bonus, nothing in the framework
> currently uses annotaions. Thus, it's a great testbed I can use before
> I figure out how I'm going to handle annotations.
>
> Plan to add a File based ClasspathRoot/ClasspathResource too. (for testing)
>
> See? progress!
>
> Geoff
>
> --
> The Spindle guy.          http://spindle.sf.net
> Get help with Spindle:   
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog:                     http://jroller.com/page/glongman
> Feature Updates:          http://spindle.sf.net/updates
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> _______________________________________________
> Spindle-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/spindle-developer
>
>   


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642