Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » 3 metadata files are all required after refactoring?
3 metadata files are all required after refactoring? [message #474192] Thu, 24 May 2007 16:50 Go to next message
Eclipse User
Originally posted by: dhampson.usa.net

After refactoring, it looks to me that there are 3 metadata files for each
comp lib, right? CM metadata is totally changed and it doesn't have
<cm-element tag anymore. Is configs/cm/jsfhtml.xml still neccessary?


Thanks

Dan
Re: 3 metadata files are all required after refactoring? [message #474193 is a reply to message #474192] Fri, 25 May 2007 00:53 Go to previous messageGo to next message
Gerry Kessler is currently offline Gerry Kessler
Messages: 125
Registered: July 2009
Senior Member
These files are currently required.

When Sybase contributed the Web Page Editor, they used a different
mechanism for providing metadata. Actually they had more than one. We
replaced some of the Sybase infrastructure and metadata with our new
Design-Time Metadata framework. Unfortunately we ran out of time to
replace some of what you see in these files, which is the metadata that
the properties view for the WPE is using. We will be replacing this in a
future release and the current property sheet metadata will not be
supported. This work will be tracked using
https://bugs.eclipse.org/bugs/show_bug.cgi?id=189058.

Were you planning on providing property sheet metadata using this release?

On the topic of there being three metadata files per comp lib, this need
not necessarily be the case. The framework will perform a merge of the
"standard" metadata files into a single, in-memory model for each taglib
uri. You can make your own choice on how to structure these files.

The old "CMAnnotations" metadata framework is now deprecated. If you
were using that framework, you will see that it can be easily converted to
the new one.
Re: 3 metadata files are all required after refactoring? [message #474280 is a reply to message #474193] Wed, 30 May 2007 22:00 Go to previous messageGo to next message
Eclipse User
Originally posted by: dhampson4.usa.net

Thanks! appreciate.

I have another question regarding the relationship between dti metadata
and the implementation of ITagConverter. For example the relationship
between jsf_html_dti.xml and converter classes in converter.jsfhtml
package. It looks to me they are duplicated. I am just curious that the
approach of using dti metadata only is powerful enough to define custom
component?

Thanks

Dan
Re: 3 metadata files are all required after refactoring? [message #474281 is a reply to message #474280] Thu, 31 May 2007 21:39 Go to previous message
Ian Trimble is currently offline Ian Trimble
Messages: 137
Registered: July 2009
Senior Member
The ITagConverter implementations are no longer used (OK, they are
currently "fallen back to" in the case of missing design-time information
metadata, but they will eventually go away). Instead, the "dti" metadata
describes how to perform tag conversion. If you look at jsf_html_dti.xml,
and look at the first entity (id="column"), you'll see that it is possible
to provide a custom transform operation by specifying a fully-qualified
classname to be used. This allows for cases where dti is simply not
capable of fully describing the tag conversion.

- Ian
Re: 3 metadata files are all required after refactoring? [message #610968 is a reply to message #474192] Fri, 25 May 2007 00:53 Go to previous message
Gerry Kessler is currently offline Gerry Kessler
Messages: 125
Registered: July 2009
Senior Member
These files are currently required.

When Sybase contributed the Web Page Editor, they used a different
mechanism for providing metadata. Actually they had more than one. We
replaced some of the Sybase infrastructure and metadata with our new
Design-Time Metadata framework. Unfortunately we ran out of time to
replace some of what you see in these files, which is the metadata that
the properties view for the WPE is using. We will be replacing this in a
future release and the current property sheet metadata will not be
supported. This work will be tracked using
https://bugs.eclipse.org/bugs/show_bug.cgi?id=189058

Were you planning on providing property sheet metadata using this release?

On the topic of there being three metadata files per comp lib, this need
not necessarily be the case. The framework will perform a merge of the
"standard" metadata files into a single, in-memory model for each taglib
uri. You can make your own choice on how to structure these files.

The old "CMAnnotations" metadata framework is now deprecated. If you
were using that framework, you will see that it can be easily converted to
the new one.
Re: 3 metadata files are all required after refactoring? [message #611561 is a reply to message #474193] Wed, 30 May 2007 22:00 Go to previous message
Eclipse User
Originally posted by: dhampson4.usa.net

Thanks! appreciate.

I have another question regarding the relationship between dti metadata
and the implementation of ITagConverter. For example the relationship
between jsf_html_dti.xml and converter classes in converter.jsfhtml
package. It looks to me they are duplicated. I am just curious that the
approach of using dti metadata only is powerful enough to define custom
component?

Thanks

Dan
Re: 3 metadata files are all required after refactoring? [message #611563 is a reply to message #474280] Thu, 31 May 2007 21:39 Go to previous message
Ian Trimble is currently offline Ian Trimble
Messages: 137
Registered: July 2009
Senior Member
The ITagConverter implementations are no longer used (OK, they are
currently "fallen back to" in the case of missing design-time information
metadata, but they will eventually go away). Instead, the "dti" metadata
describes how to perform tag conversion. If you look at jsf_html_dti.xml,
and look at the first entity (id="column"), you'll see that it is possible
to provide a custom transform operation by specifying a fully-qualified
classname to be used. This allows for cases where dti is simply not
capable of fully describing the tag conversion.

- Ian
Previous Topic:f:loadBundle doesn't contibute it's "var" variable to EL
Next Topic:Eclipse content assist
Goto Forum:
  


Current Time: Wed Oct 22 12:20:27 GMT 2014

Powered by FUDForum. Page generated in 0.02464 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software