Re: [seam-dev] Seam 2.1 issues in Tools
On 21 Oct 2008, at 23:29, Max Rydahl Andersen wrote:
On Wed, 22 Oct 2008 00:27:22 +0200, Shane Bryzak
<shane.bryzak(a)jboss.com
> wrote:
> Ok as Pete said it may have something to do with the new multi-
> package support for namespaces. How are you doing the translation?
As described below. We simply do org.jboss.seam.[postcolonname].
[camelcaseoftagname]
Was told by Gavin et.al. that would be sufficient 99% of the time ;)
I guess we just hit the 1%
So this doesn't work if you define your own namespace? Hmm, this is
bad as people can do that (and clever people will do it a lot), and
their tooling shouldn't tell them it's an error.
The correct way to do this would be to scan the classpath for package-
info.class files, load them, and build a map of namespace:package from
the @Namespace annotation on the package, and substitute package for
org.jboss.seam in your above algorithm.
/max
>
> Max Rydahl Andersen wrote:
>> On Wed, 22 Oct 2008 00:23:45 +0200, Shane Bryzak <shane.bryzak(a)jboss.com
>> > wrote:
>>
>>> This attribute was simply moved (from identity to rule-based-
>>> permission-resolver) in Seam 2.1.0, no library requirements were
>>> changed for security. Is there a security rules file present,
>>> and is there a specific exception produced? This change was
>>> documented in seam21migration.txt in the root of the Seam dist,
>>> might be worth checking there for any other potentially breaking
>>> changes.
>>
>> The problem is the missing class...we translate security:rule-
>> based-permission-resolver to
>> org.jboss.seam.security.RuleBasedPermissionResolver;
>> that is apparently not enough anymore for the core tags.
>>
>> /max
>>
>>>
>>> Max Rydahl Andersen wrote:
>>>> Hi,
>>>>
>>>> Walking through jira issues for JBT 3 beta1 and I just stumbled
>>>> into
>>>> https://jira.jboss.org/jira/browse/JBIDE-2702 which is caused by
>>>> <security:rule-based-permission-resolver security-
>>>> rules="#{securityRules}"/>
>>>> now being in components.xml by default.
>>>>
>>>> That is for some reason failing for us - probably we are missing
>>>> a drools jar or something ;)
>>>>
>>>> Before I start finding these changes in 2.1 that might break
>>>> current tools behavior the hard way,
>>>> do you guys got a list of major 2.1 changes that changes lib
>>>> dependencies/startup sequence etc. ?
>>>>
>>>
>>
>>
>>
>
--
/max
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev