Re: Prims not being displayed properly in thesfManagementConsole

"Goldsack, Patrick" <[email protected]> Thu, 20 Jul 2006 14:39:43 +0100
Newsgroups gmane.comp.java.smartfrog.devel
Message-ID <[email protected]>
Not sure about the management console problem, but the schema issue I
can explain.

At the time the schema is being checked (parsing), the value of the
attribute is indeed a ComponentDescriptionImpl as it has not yet been
deployed. The schema makes no guesses as to the eventual deployed
component class and just looks at the class it currently has. You could
write an assertion instead that checks that the sfClass attribute has
the right string value as an alternative to schema checking.

However I am close to releasing LAZY asserttions and schemas (in the
model of the recent release of LAZY functions, including LAZY
propagation). In this case you will be able to delay evaluation of the
schema until deployment - at which time you would be able to validate
the component type as you would like to do. The next release of SF is
pending my completion of this. 

Patrick

-----Original Message-----
From: smartfrog-developer-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:smartfrog-developer-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
Olivier Pernet
Sent: 20 July 2006 13:42
To: Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [Smartfrog-developer] Prims not being displayed properly in
thesfManagementConsole

Hello,

We're having some strange problem with the management console. A few of
our Prim components are only being displayed as attributes in the
Compound they're in, and not as Prims. But the BashShell component that
is being deployed in the same Compound shows up properly.

Maybe related to that, we're having trouble with a simple schema :
StorageBackend extends Compulsory {
   class "ch.cern.openlab.smartfrog.xen.XenDomainStorageBackend";
}

When we try to enforce this with
storageBackend extends StorageBackend;

we get a schema checking error, saying that the attribute we put is a
ComponentDescriptionImpl, and not a XenDomainStorageBackend. But if we
disable the schema check for this attribute, everything works fine.

Thanks for your help,

--
Olivier Pernet
Summer Student - CERN Openlab

We are the knights who say
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq'|dc

------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
Smartfrog-developer mailing list
Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV