| @NoDuplicates not trigger validation [message #643998] |
Wed, 08 December 2010 20:07  |
Eclipse User |
|
|
|
I have a property list which has following spec:
public interface IModulePublishingTarget extends IModelElement,IRemovable {
ModelElementType TYPE = new ModelElementType( IModulePublishingTarget.class );
// *** Name ***
@Label( standard = "Target Name" )
@NoDuplicates
...
}
Although
@NoDuplicates
is specified, in the rendered table UI, adding duplicated
entry does not prompt error. Am I missing anything?
|
|
|
|
|
|
|
|
| Re: @NoDuplicates not trigger validation [message #646075 is a reply to message #645898] |
Tue, 21 December 2010 15:22  |
| Eclipse User |
|
|
|
Do you consider advancing to those frameworks over time with new releases of
Sapphire?
I also work in projects based on Java 5 a lot, but officially Oracle/Sun has
declared that Dead 2 years ago, wasn't it...?;-)
Congrats on the EclipseCon session. Unfortunately even as mentor Chris and
the others picking those talks for 2011 either didn't fully understand the
power of some projects like UOMo, but what I suspect more is they totally
abandoned "Vertical" apps, or Domain Specific projects and solutions as you
may also tell them.
No Healthcare, no Automotive, no Embedded (except a few Mobile things) with
rather prominent examples like Sequoyah left aside completely.
On the other hand, all those technical Domain agnostic things and tools
dealing with Multithreading, etc. were selected.
And as you'll see, almost 5 competing solutions for Data Binding have some
talks:
- Sapphire
- E4
- Scout
- High Performance Tabular Databinding (they won the 1st audition)
- RedView
I hope I didn't miss any, but it is really a bit sad to see entropy in one
area (how many people will use more than one in their project ?;-) while
those really using those in the real world were completely left out.
Werner
|
|
|
| Re: @NoDuplicates not trigger validation [message #646253 is a reply to message #646075] |
Wed, 22 December 2010 17:00 |
| Eclipse User |
|
|
|
> Do you consider advancing to those frameworks over time with new
> releases of Sapphire?
Probably not. Moving minreq up to Java 6 would greatly reduce the number of projects that consider Sapphire. It took a very long time for many projects to minreq Java 5. I don't see prevalence of Java 6 minreq for a very long time. In the meantime, Sapphire API needs to be stabilized and polished. Even if say 5 years down the road, a Java 6 minreq is feasible, that is unlikely to have a substantial impact on Sapphire direction.
> I suspect more is they totally abandoned "Vertical" apps, or Domain
> Specific projects and solutions as you may also tell them.
Sorry to hear that your talk was rejected. It is always an unpleasant experience. In general, conferences tend to gravitate towards framework talks over verticals due to probability of wider appeal. The other thing the program committee looks for is momentum behind a technology and frankly many of the verticals at Eclipse haven't been doing that great.
At the end of the day, I don't envy the job of the program committee. No matter what you do, you are bound to make a good number of people very unhappy.
Hope to still see you at EclipseCon.
- Konstantin
|
|
|
Powered by
FUDForum. Page generated in 0.03911 seconds
Home