[JBoss JIRA] Created: (RFPL-952) Metamer - introduce inferring of nested component's ID
by Lukas Fryc (JIRA)
Metamer - introduce inferring of nested component's ID
------------------------------------------------------
Key: RFPL-952
URL: https://jira.jboss.org/browse/RFPL-952
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QA
Affects Versions: 4.0.0.Milestone4
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: 4.0.0.Milestone5
Currently, in all the samples, where you need to address component from components outside of "content" definition,
you have to use relative component's ID.
But this principle doesn't work when applying templates of container components (such as data tables), because they are changing the relative component address.
Reimplement adressing to use absolute addressing in these samples.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Commented: (RFPL-1038) knowledgebase: photoalbum conflicts between Maven build and JBoss Tools build.
by Ilya Shaikovsky (JIRA)
[ https://issues.jboss.org/browse/RFPL-1038?page=com.atlassian.jira.plugin.... ]
Ilya Shaikovsky commented on RFPL-1038:
---------------------------------------
Summary after issue discussion:
Tools team:
1) JBoss Tools team should use patched example.
1.1) believe that just libraries updates can't influence that.
RF team:
2) should fix in 3.3.4 in trunk
2.1) Task depends on what will be broken after patch is back. If we will have too much problems or too much time on corrections estimated - could be postponed because of 4.x Final works.
3) should perform 2) steps in ENT branch.
4) Should create wiki about the problem for the users who using 3.3.3.Final tag and can't use snapshots. We should explain the problem and the patch.
Additionally
5) Check resource filtering additionally. Why do we used that and not just placed resources as Snjezana written in linked issue?
> knowledgebase: photoalbum conflicts between Maven build and JBoss Tools build.
> ------------------------------------------------------------------------------
>
> Key: RFPL-1038
> URL: https://issues.jboss.org/browse/RFPL-1038
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 3.3.3.Final
> Reporter: Ilya Shaikovsky
> Assignee: Ilya Shaikovsky
> Fix For: Site
>
>
> https://issues.jboss.org/browse/JBIDE-7470 - the problem.
> revert of that https://issues.jboss.org/browse/JBIDE-5646 fix is the reason of regression.
> need to create info wiki page with solution as we can't release 3.3.4.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RFPL-882) Push: need to discuss how to create and where to deploy(if possible) push demo
by Ilya Shaikovsky (JIRA)
Push: need to discuss how to create and where to deploy(if possible) push demo
------------------------------------------------------------------------------
Key: RFPL-882
URL: https://jira.jboss.org/browse/RFPL-882
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: components
Affects Versions: 4.0.0.Milestone4
Reporter: Ilya Shaikovsky
Assignee: Ilya Shaikovsky
Priority: Critical
Fix For: 4.0.0.Milestone5
current push:
1) not supports GAE even after redesign
2) do not supports old definitions
So, seems we could have no time to prepare the demo/announces for M4 release. And currently I commented sample out of rf-showcase.
Need to discuss next important thing: When the new demo for redesigned push will appears - where we will deploy it? I believe that it's highly important feature of RF and we need to announce it with good sample(ideally available online)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months