Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
MIME-Version: 1.0
Sender: hedhman@gmail.com
In-Reply-To: <tencent_536F43580D00218666F8DFB2@qq.com>
References: <tencent_536F43580D00218666F8DFB2@qq.com>
From: Niclas Hedhman <niclas@hedhman.org>
Date: Sat, 22 Oct 2016 11:14:03 +0800
Message-ID: <CADmm+KdskPozkc=ffzePh5BwWw0eeZDCNe_cNsSQvoBM7ZTnPA@mail.gmail.com>
Subject: Re: Listing composite properties
To: dev <dev@zest.apache.org>
Content-Type: multipart/alternative; boundary=001a11c16b1834e401053f6b8eab
archived-at: Sat, 22 Oct 2016 03:14:37 -0000

--001a11c16b1834e401053f6b8eab
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Quite right.

The idea with SPI is roughly; If you don't create Extensions (or advanced
libraries), then you should normally not depend on the core.spi module at
all, to ensure that you are not in too deep.

Yes, the Qi4j -> ZestAPI and Qi4jSPI -> ZestSPI.
One other major issue is that Iterables are being replaced with Java 8
Stream API just about everywhere.


Cheers
Niclas

On Sat, Oct 22, 2016 at 10:28 AM, zhuangmz08 <zhuangmz08@qq.com> wrote:

> Thanks all.
> I'm using "org.qi4j.core:org.qi4j.core.api:2.1". Then, I need to replace
> org.apache.zest.api.ZestAPI with org.qi4j.api.Qi4j, replace
> org.apache.zest.spi.ZestSPI with org.qi4j.spi.Qi4jSPI. I've get my
> PropertyDescriptors.
> SPI extends from API. And SPI is designed for building extensions. Thus,
> I'd better use SPI rather than API.
> Is my understanding right?
>
>
>
>
>
>
> ------------------ =E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6 -----------------=
-
> =E5=8F=91=E4=BB=B6=E4=BA=BA: "Niclas Hedhman";<niclas@hedhman.org>;
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2016=E5=B9=B410=E6=9C=8822=E6=97=A5=
(=E6=98=9F=E6=9C=9F=E5=85=AD) =E4=B8=8A=E5=8D=888:11
> =E6=94=B6=E4=BB=B6=E4=BA=BA: "dev"<dev@zest.apache.org>;
>
> =E4=B8=BB=E9=A2=98: Re: Listing composite properties
>
>
>
> Note that the EntityDescriptor (and its siblings) extends
> StatefulCompositeDescriptor, which allows you to obtain the
> StateDescriptor/
> AssociationStateDescriptor where you can get the PropertyDescriptors and
> AssociationDescriptors, which is what you were asking for. If you have th=
e
> Property, you can get the PropertyDescriptor directly from the ZestAPI,
> without trying to locate it inside the CompositeDescriptors.
>
>
> There are a whole set of good methods in the ZestAPI class for regular
> code. There are additional methods available in ZestSPI, more suitable fo=
r
> use when you are creating Extensions and very generic libraries.
>
> HTH
>
> On Sat, Oct 22, 2016 at 1:06 AM, Paul Merlin <paul@nosphere.org> wrote:
>
> > Hi,
> >
> > zhuangmz08 a =C3=A9crit :
> > > Hi, I'm trying to persist my Value/Entity Composite into database. Ca=
n
> I
> > list all the properties (name, type) of the composite? Thanks.
> >
> > Yes! You need to get hold of your Value/Entity descriptors.
> > This can be done through the ZestAPI, e.g.:
> >
> > @Structure ZestAPI api;
> >
> > void someMethod()
> > {
> >     EntityDescriptor descriptor =3D api.entityDescriptorFor( someEntity=
 );
> > }
> >
> > HTH
> >
> >
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>


--=20
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

--001a11c16b1834e401053f6b8eab--