Geoff Howard wrote:
Berin Loritsch wrote:
What this means is that the @x-avalon-info should be considered
differently for service interfaces (element name) and for classes
("type" attribute).
No, it means that your interpretation of the configuration to get
at the short name would be differen
Geoff Howard wrote:
It takes away the need for a separate ROLES file.
Right, but we don't have our sitemap components in a roles file. We
have them in and it's not clear to me
how this concept changes in 2.2.
It doesn't change a ton of things, but to be clear, you do have a roles
file embede
Berin Loritsch wrote:
What this means is that the @x-avalon-info should be considered
differently for service interfaces (element name) and for classes
("type" attribute).
No, it means that your interpretation of the configuration to get
at the short name would be different.
Is there an easy
Berin Loritsch wrote:
Geoff Howard wrote:
I'm hoping someone with more confidence in the changes needed can
check out the simple changes below. Such a paradigm shift to give up
the marker interfaces (and I'm mourning the loss of content assist.
Don't suppose an eclipse plugin for meta info y
Berin Loritsch wrote:
Sylvain Wallez wrote:
Berin Loritsch wrote:
- What do sitemap components get for @x-avalon-info? A new made up
string like cookie-matcher? The @name/type from the default
sitemap in 2.1?
The @x-avalon-info name="cookie-matcher" line lets you define your
components
li
Sylvain Wallez wrote:
Berin Loritsch wrote:
- What do sitemap components get for @x-avalon-info? A new made up
string like cookie-matcher? The @name/type from the default sitemap
in 2.1?
The @x-avalon-info name="cookie-matcher" line lets you define your
components
like this:
configuratio
Berin Loritsch wrote:
Geoff Howard wrote:
[EMAIL PROTECTED] wrote:
ghoward 2003/10/25 14:59:50
Modified:src/java/org/apache/cocoon/matching Matcher.java
CookieMatcher.java
Log:
start fortressizing Matchers. lots of open questions already, so
I'll pause here.
Stephen McConnell wrote:
Berin:
What is you plan concerning migration to the @avalon tags?
http://avalon.apache.org/meta/tools/tags/
Take it one step at a time.
1) Get Cocoon 2.2 to a workable state with Fortress as is.
2) Finish upgrades to Fortress to allow meta tags integration.
3) With all
Berin Loritsch wrote:
Geoff Howard wrote:
[EMAIL PROTECTED] wrote:
ghoward 2003/10/25 14:59:50
Modified:src/java/org/apache/cocoon/matching Matcher.java
CookieMatcher.java
Log:
start fortressizing Matchers. lots of open questions already,
so I'll pause here
Geoff Howard wrote:
[EMAIL PROTECTED] wrote:
ghoward 2003/10/25 14:59:50
Modified:src/java/org/apache/cocoon/matching Matcher.java
CookieMatcher.java
Log:
start fortressizing Matchers. lots of open questions already,
so I'll pause here.
I'm hoping someone w
10 matches
Mail list logo