Re: Lookup & Search Redux

Hopefully Hugo will have the same situation with IntelliJ.

Good luck on the Framework library :-)

You know... I still don't grok that whole meta-key thing for
Contrib.library. With the meta-key, everything's still explicitly
declared.With the following: <meta
key="org.apache.tapestry.component-class-packages"
value="org.apache.tapestry.contrib.components"/>
I'd expect everything to flow from value down, but it doesn't. It flows
from contrib (the package) down. And this makes sense....?
[e.g.,  <component-type type="Choose"
specification-path="components/Choose.jwc"/> isn't in
...contrib.components.components.Choose.jwc, it's just
....contrib.components.Choose.jwc - but it's one of the four in
"component-class-packages"] Seems like this was a good idea gone awry to
me. (user pov, not tool pov)

Although it wouldn't help Spindle outside of Tapestry itself, I'd be for
making Tapestry the back in to the 'strict' example completely (removing
the meta tag).

4.0.3 isn't completely dead. I'm merging changes in the 4 branch up to
tapestry4's trunk, but I'm also moving forward with both possibilities
in mind - both a 4.0.3 and a 4.1 and only a 4.1. Time and interest will
tell which road we take. Up to now, there have been very few changes
toward 4.0.3 that weren't documentation. There are, however, some
remaining issues that will be code-based. As those are fixed, I'll be
applying changes toward 4.0.3 and 4.1. If 4.1 starts looking like it'll
take longer than expected, I'll already have everything in place to
release 4.0.3.

Brian

Geoff Longman wrote:
>> From the bulder POV all I need to do is ensure that a Resource exists
> and open an input stream on it. In addition, if the Resource reps a
> physical file (not jar) need to record 'problems'. Eclipse put those
> red markers - I'm sure IntelliJ has an equivalent.
>
> Eclipse is easy 'cuz both physical and jar files are represented by a
> super interface (IStorage) so I can paramterize some classes to make
> them generic enough for the non Eclipse case.
>
> I guess there is always the fallback of realizing concrete instances
> of those classes with an Object parameter - ugly but it would cover
> anything. This is exacly what I'm dong to get unit tests (outside of
> Eclipse) running.
>
> BTW I have made it past the intial assertion checks (not nulls mostly)
> and no past the "is this worth building at all?" check - I'm about to
> try building the Framework library. yay.
>
> With reference to the other thread - 4.0.3 - I just took a quick look
> at Contrib.library and I see :
>
> <meta key="org.apache.tapestry.component-class-packages"
> value="org.apache.tapestry.contrib.components"/>
>
> which is bad for me unfortunately - but there are only 4 Components in
> that package.
>
> Thing is that Framework and Contrib *used* to be very strict and
> *everything* was explicitly declared. Things got loose in T4 timeframe
> I guess.
>
> component-class-package is one, of a couple, killer for T4 support. Is
> 4.0.3 dead for sure?
>
> I'm hoping to get the new Spindle bulder to pass over Framework and
> Contrib in the next day or so - could have a list of 'tweaks' by say
> wed.
>
> Geoff
>
> Geoff


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642