<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Max Rydahl Andersen wrote:
<blockquote
cite="mid:1707376273.5883151220429811535.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">Hi Denis,
</pre>
<blockquote type="cite">
<pre wrap="">I'd not say it is good.
First of all I cannot see any reason to put it in common. El is
related
to Java Server Pages (${}) and JSF (#{}).
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">But what is major purpose of new plug-ins? It is providing replacement
for EL expressions to possible values. It should allow to show page in
VPE as close to run-time as possible. That functionality is related
only to VPE and that means there is no reason to move those plug-ins in
nether to common component nor to any other. VPE component is a right
place for it, especially org.jboss.tools.vpe plugin.
</pre>
</blockquote>
<pre wrap=""><!---->
Not true.
EL is used in non-JSF scenarios too. e.g. Seam configuration files.
I asked Eugene to split out the specific EL replacement setup to be able
to use this in non-VPE scenarios.
</pre>
</blockquote>
Are you talking about @xxxxxx@ EL like in components.xml or about
#{xxxxxxx} like in pages.xml?<br>
Could you explain non JSF scenario for for seam configuration files? <br>
<blockquote
cite="mid:1707376273.5883151220429811535.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">I objected because it seems that this resulted in two plugins which dependency
list is the opposite of what I would expect since I still do not see why EL
resolving has a dependency to something related to resource references. Just because
there are some ui components in there the EL ui uses does not make it right.
In my pov the only parts that would need "extracting" is the EL core and ui and
those could make it into org.jboss.tools.common.el.core and org.jboss.tools.common.el.ui
and at least be independent plugins which does this basic and simple task of providing
configuration for the global, project and folder level EL variables and have a simple core
api for resolving a variable in a given context.
Then if VPE needs to convert these into resource references that should be done in VPE.
/max
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks
Denis
Eugene Stherbin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Max Rydahl Andersen пишет:
</pre>
<blockquote type="cite">
<pre wrap="">good, but why does the EL variable substitution require resource
references ? Why are there VPE packages in it ?
Why put it in separate packages when there is still these hard
dependencies ?
/max
----- "Eugene Stherbin" <a class="moz-txt-link-rfc2396E" href="mailto:estherbin@exadel.com"><estherbin@exadel.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
The org.jboss.tools.common.rreferences bundle renamed to the
org.jboss.tools.common.resref in svn.
--
Best Ragards,
Eugene Stherbin
Exadel Inc.
Mob. phone: +375 (29) 705-52-59
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:estherbin@exadel.com">estherbin@exadel.com</a>
_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">1.org.jboss.tools.common.resref bundle contains of base classes.
</pre>
</blockquote>
<pre wrap="">These
</pre>
<blockquote type="cite">
<pre wrap="">classes has all necessary functionality for save/read properties,
</pre>
</blockquote>
<pre wrap="">show
</pre>
<blockquote type="cite">
<pre wrap="">popups, display table with Add/Edit/Delete functionality and e.t.c.
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">org.jboss.tools.common.el - contains of 4 classes that extends base
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">functionality and add functionality required for Global El/Vpe El.
2. Because classes in VPE package required only for VPE.
3. See point 1. It separated to two bundles because bundles has
difference logical functionality and if we will want add new similar
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">functionality only extends from org.jboss.tools.common.resref
</pre>
</blockquote>
<pre wrap="">bundle.
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>