> I only deprecated it for now, so that
we could figure out how to fix up all the old code that used it. If we can
reverse that decision, I'd love it!
Actually,
I will not argue if IAttribute will be able to have different types of
value, so, we need to add the following
methods to IAttributeModel:
Iterator
getValueModels()
getValueModel(URI
valueType)
boolean hasMultipleValues()
getValueModel() - returns value
model if hasMultipleValues() is false, otherwise throws an exception
If you do not agree or will not be able to add it today,
I'll just temporary add IAttributeComplexValueModel interface to
idas.cp.jena2 project to make it buildable for the release.
Thanks, Sergey Lyakhov
----- Original Message -----
Sent: Tuesday, June 17, 2008 6:36
PM
Subject: Re: [higgins-dev] Higgins 1.1 M2
release status - 13-June-08
This
is branching into another topic.
IAttributeModel can no longer have a method getValueModel. Why?
Because the group decided that each value of an attribute is allowed to
be of a different type. Daniel and Mike were the main proponents of
this. I don't like it and I pretty much caved to group consensus.
If you'd like to re-raise that argument, feel free. To me, it's
much simpler to say that all values of an attribute are of the same
type.
I only
deprecated it for now, so that we could figure out how to fix up all the old
code that used it. If we can reverse that decision, I'd love it!
Jim
>>> "Sergey Lyakhov"
<slyakhov@xxxxxxxxxxxxxx> 06/17/08 8:26 AM >>>
Actually, IAttributeModel should return the model of its value, because
in HOWL, each attribute can have exactly one type of
value. IAttributeModel.getValueModel() (which now is deprecated by some
reason) returns IAttributeValueModel (complex or simple). So, I
think, we need IAttributeComplexValueModel interface.
By the
way, because IAttributeModel.getValueModel() is now deprecated,
how should we obtain the model of value now?
----- Original Message -----
Sent: Tuesday,
June 17, 2008 5:02 PM
Subject: Re:
[higgins-dev] Higgins 1.1 M2 release status - 13-June-08
I
removed it because consensus was that we wanted attribute values to either
return an IAttributeSimpleValueModel or an IEntityModel from their
getModel() methods.
Jim
>>> "Sergey Lyakhov" <slyakhov@xxxxxxxxxxxxxx>
06/17/08 7:11 AM >>>
>
What was the fix for this? I opened this project and it doesn't
build for me.
Sorry, I forgot to ask you to add
org.eclipse.higgins.idas.api.model.IAttributeComplexValueModel interface to
idas.api project (see attachment). You removed this interface, but this
is required interface, because IAttribute should be able to return
a value model for both simple and complex value. I can commit this interface
if you do not have any objections.
----- Original Message
-----
Sent: Tuesday,
June 17, 2008 2:56 AM
Subject: Re:
[higgins-dev] Higgins 1.1 M2 release status - 13-June-08
What was the fix for this? I opened this project and it
doesn't build for me. I will try to keep all the CPs happy
during idas refactors if they build for me. Right now I'm
getting IAttributeComplexValueModel can't be resolved
>>>
"Sergey Lyakhov" <slyakhov@xxxxxxxxxxxxxx>
06/16/08 12:23 PM >>>
>
org.eclipse.higgins.idas.cp.jena2 - can't be build because it
hasn't > been updated yet to support changes in IdAS
API.
Fixed.
Thanks, Sergey Lyakhov ----- Original
Message ----- From: "Valery Kokhan"
<vkokhan@xxxxxxxxxxxxxx> To: "Higgins (Trust Framework) Project
developer discussions" <higgins-dev@xxxxxxxxxxx> Sent: Friday,
June 13, 2008 6:10 PM Subject: Re: [higgins-dev] Higgins 1.1 M2 release
status - 13-June-08
> Hi All, > > During last
few weeks we had a lot of problems with our build system. > It look
like now those problems is resolved but at least two our >
components are still unbuildable: > >
org.eclipse.higgins.crpps - can't be build because it uses of java
1.5 > methods Element:get/setTextContent > >
org.eclipse.higgins.idas.cp.jena2 - can't be build because it
hasn't > been updated yet to support changes in IdAS
API. > > Owner of this components please take a look and make
sure these > problems are fixed. > > -- >
Thanks, > > Valery > > Friday, June 13, 2008,
4:31:07 PM, you wrote: > >> Hi All - update on 1.1 M2
release status. We are still working on >> fixing broken
component builds: > >> http://www.eclipse.org/higgins/ver2/downloadsnew.php?loc=downloads > >>
This is gating the release of M2. At this point we are going
to >> postpone M2 release to (hopefully early) next
week. > >> If there are any additional critical check-ins
that must be checked in >> - please let me know the bugzilla
number so we can track it to include >> in M2
build. > >> Updates to follow. > >>
regards...Brian > > >> Brian Walker >>
=brian.walker >> VP of Engineering >> Parity
Communications Inc >> cell:
781-801-0254 > > > >>
_______________________________________________ >> higgins-dev
mailing list >> higgins-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/higgins-dev > >
_______________________________________________ > higgins-dev
mailing list > higgins-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/higgins-dev
_______________________________________________ higgins-dev
mailing list higgins-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/higgins-dev
_______________________________________________ higgins-dev
mailing
list higgins-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/higgins-dev
_______________________________________________ higgins-dev
mailing
list higgins-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/higgins-dev
_______________________________________________ higgins-dev mailing
list higgins-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/higgins-dev
|