Leonardo Uribe schrieb:
Hi
The problem with xml files to make faces-plugin test work is now fixed.
Great.
I have a question about how myfaces-metadata works.
The idea is have one file per jar, and when the model is readed, it
should scan every artifact and merge it with the generated
Problem with SheetSelection-JavaScript
--
Key: TOBAGO-642
URL: https://issues.apache.org/jira/browse/TOBAGO-642
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects Versions:
Cannot get access-scoped beans from a servlet
-
Key: ORCHESTRA-18
URL: https://issues.apache.org/jira/browse/ORCHESTRA-18
Project: MyFaces Orchestra
Issue Type: Bug
Affects Versions: 1.1
View to be restored was removed and cannot be retrieved from the map
(JspStatemanagerImpl)
--
Key: MYFACES-1847
URL: https://issues.apache.org/jira/browse/MYFACES-1847
[
https://issues.apache.org/jira/browse/TOMAHAWK-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584472#action_12584472
]
Thomas Jonsson commented on TOMAHAWK-843:
-
Hi,
I'm also facing the same problem.
[
https://issues.apache.org/jira/browse/TOBAGO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-619.
--
Resolution: Fixed
Avoid usages of javascript:false in iframe src attribute
[
https://issues.apache.org/jira/browse/TOBAGO-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-639.
--
Resolution: Fixed
Optimize layout token parsing
-
[
https://issues.apache.org/jira/browse/TOMAHAWK-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584486#action_12584486
]
Simon Kitching commented on TOMAHAWK-843:
-
Are you using session-scoped backing
[
https://issues.apache.org/jira/browse/TOMAHAWK-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584500#action_12584500
]
Simon Kitching commented on TOMAHAWK-843:
-
One thing I see from the UIData
Ping!
It seems that Orchestra has to implement a StateManager which
holds the view state in the conversationContext instead of the session.
At the moment it seems that large portions of JspStateManagerImpl can be
reused, but requires to copy it over into Orchestra.
With slight refactoring of
[
https://issues.apache.org/jira/browse/MYFACES-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584528#action_12584528
]
Simon Kitching commented on MYFACES-1326:
-
Matthias, what sort of metadata do you
[
https://issues.apache.org/jira/browse/TOBAGO-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-642.
Resolution: Fixed
Handling of the seleced was fixed:
Javacode on Server uses as format: e.
Mario Ivankovits schrieb:
Ping!
It seems that Orchestra has to implement a StateManager which
holds the view state in the conversationContext instead of the session.
At the moment it seems that large portions of JspStateManagerImpl can be
reused, but requires to copy it over into
Mario, you are not alone in hating the shared concept. ;-)
This is exactly where the myfaces-commons-xxx library comes into
play, I often mentioned before.
What we need is a module, that
1) has a super stable API
2) is used (ie. shared) by the myfaces core(!) as well as other myfaces projects
3)
Hi!
Mario, you are not alone in hating the shared concept. ;-)
Good!
1) has a super stable API
That is true, that might be the hardest part.
2) is used (ie. shared) by the myfaces core(!) as well as other myfaces
projects
Sure!
3) may be used by the experienced JSF app
Manfred Geiler schrieb:
Mario, you are not alone in hating the shared concept. ;-)
This is exactly where the myfaces-commons-xxx library comes into
play, I often mentioned before.
What we need is a module, that
1) has a super stable API
2) is used (ie. shared) by the myfaces core(!) as
Problem here again is the name of such a lib:
myfaces-commons-base?
myfaces-commons-core?
myfaces-commons-super?
myfaces-commons-commons? ;-)
I'd opt for myfaces-base, but to say the truth, I do not care about the
name, whatever name it has will be good for me as long as
Personally, I think the shared concept works fine.
fine is a bit to much, right? But, yeah it works
One problem with a commons jar used by core is that Sun Mojarra will
need two jars (jsf-api, jsf-impl) and myfaces will need three (jsf-api,
jsf-impl, commons-whatever.jar). This is
Mario Ivankovits schrieb:
Hi!
Does this qualify to move JspStateManagerImpl into shared? Or should I
better copy the source over?
There are some jira issues and email threads that might be relevant:
Thanks for the links, for me it seems there is need for
Matthias Wessendorf schrieb:
I'm also sceptical that it will be possible to create a super stable
API. Just look at what is in shared at the moment! And in addition to
the API, the *implementation* will also need to be super-stable. For
example, if a Tomahawk issue (whether bug or new
Hi,
2008/4/2, Matthias Wessendorf [EMAIL PROTECTED]:
Problem here again is the name of such a lib:
myfaces-commons-base?
myfaces-commons-core?
myfaces-commons-super?
myfaces-commons-commons? ;-)
I'd opt for myfaces-base, but to say the truth, I do not care about
Hi!
Orchestra having its own JspStateManagerImpl sounds interesting
though. Enabling this on Sun Mojarra for example will quite radically
change the way that a JSF app on Mojarra performs. That's not really
Orchestra's role.
I thought about this like an optional feature one has to
[
https://issues.apache.org/jira/browse/TRINIDAD-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584564#action_12584564
]
Paul Mander commented on TRINIDAD-992:
--
I've got a solution to this problem now. It
we already have a very raw starting point in the current commons,
not yet finished, but it's there ;-)
The started commons-(converters|validators) are IMHO a other type of commons,
not for use in jsf-impl classes but for application developper. This
is for nice and convenient utils
I largely agree with Simon here.. Myfaces Core should not be
dependent on a commons library. It has an obligation to the TCK. I
see no reason, though that if this library has universal appeal, it
can't be duplicated in commons.
Unlike everyone else though, I don't like the base name.
[
https://issues.apache.org/jira/browse/TOBAGO-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-630.
Resolution: Fixed
Selection of rows in long sheets is slow on IE
Myfaces Core should not be dependent on a
commons library. It has an obligation to the TCK.
currently we have dependencies on some apache commons lib,
that's fine, I think (we passed the TCK thing).
Or did I got you wrong ?
Unlike everyone else though, I don't like the base name. It
On Wed, Apr 2, 2008 at 3:18 PM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Orchestra having its own JspStateManagerImpl sounds interesting
though. Enabling this on Sun Mojarra for example will quite radically
change the way that a JSF app on Mojarra performs. That's not really
Sorry to be a grouch, but I am starting to wonder if people ever test
Tobago builds before checking in code. It is a continuous source of
spam by having continuum failure and success messages at least a few
days every week. Is there anything that can be done to stop this? I
suppose I could create
On Wed, Apr 2, 2008 at 4:25 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Sorry to be a grouch, but I am starting to wonder if people ever test
Tobago builds before checking in code. It is a continuous source of
spam by having continuum failure and success messages at least a few
days every
from yesterday,
== continuum
On Tue, Apr 1, 2008 at 3:24 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Online report :
http://myfaces.zones.apache.org:8080/continuum/buildResult.action?buildId=8034projectId=13
Build statistics:
State: Error
Previous State: Ok
Started at: Tue 1 Apr
this is a Trinidad one
== continuum
On Tue, Apr 1, 2008 at 10:14 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Online report :
http://myfaces.zones.apache.org:8080/continuum/buildResult.action?buildId=8030projectId=48
Build statistics:
State: Error
Previous State: Ok
Started at:
On Wed, Apr 2, 2008 at 4:30 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On Wed, Apr 2, 2008 at 4:25 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Sorry to be a grouch, but I am starting to wonder if people ever test
Tobago builds before checking in code. It is a continuous source of
PanelFrameLayout improvement to allow frames resizing and border coloring
-
Key: TRINIDAD-1038
URL: https://issues.apache.org/jira/browse/TRINIDAD-1038
Project: MyFaces Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Havelka updated TRINIDAD-1038:
Status: Patch Available (was: Open)
PanelFrameLayout improvement to allow frames
From: Kito D. Mann [EMAIL PROTECTED]
I just want to add that when we were talking about moving Shale over to
MyFaces, people were worried about resources for maintaining it. And Shale
is an *existing* code base :-). I think it'd make a lot more sense to
migrate the existing suites to JSF
Conversion issue - Schedule_editsettings.jsp not working with Schedule.Mode
setting
---
Key: TOMAHAWK-1224
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1224
I found some more (Trinidad and Tobago).
Reason (as mostly) = continuum).
Okay, thanks for looking into it. Maybe I should create a new filter
for these guys.
On Wed, Apr 2, 2008 at 5:43 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I found some more (Trinidad and Tobago).
Reason (as mostly) = continuum).
Okay, thanks for looking into it. Maybe I should create a new filter
for these guys.
yes. or check for ContinuumBuildCancelledException
ajax requests looses viewRoot locale setting
Key: TOBAGO-643
URL: https://issues.apache.org/jira/browse/TOBAGO-643
Project: MyFaces Tobago
Issue Type: Bug
Affects Versions: 1.1.0
[
https://issues.apache.org/jira/browse/TOBAGO-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-643.
-
Resolution: Fixed
Fix Version/s: 1.1.0
ajax requests looses viewRoot locale setting
Thanks Mark,
just some short notes inline
Mark Hobson schrieb:
Hi Bernd,
I've finished with the major changes in tidying up the Codehaus
apt-maven-plugin if you fancy taking a look:
http://svn.codehaus.org/mojo/trunk/sandbox/apt-maven-plugin/
Major changes:
- Manually merged in any
Yeah, I had already modified it, but it's fine with me... I've got a
fix to do anyway (because I somehow hosed the graphic) so I'll be sure
to incorporate this one.
Scott
Adonis Raduca wrote:
Hi,
In the final all MyFaces logos are finished.
I placed all of them in one image for a good
Thank you Adonis.
I think they all look great. I noticed there is one minor anomaly in
the Tomahawk logo on the far-left side, there's a portion of the green
logo that shows up as all gray whereas in the other logos, that kind
of area shows up green in the other logos.
My only request would be
Hi guys,
Iam planning to start a new Tomahawk sandbox component that generates PDF
files.
I just want to ask whether I can use (iText) java library or not.
After checking its license, I found it LGPL and MPL.
Here is the url :
http://www.lowagie.com/iText/download.html
Please tell me if I can use
On Wed, Apr 2, 2008 at 2:49 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I'm not quite clear what your description above means. I think we are
talking about the same thing, but just to be clear this is how I would
see it working:
== for goal build-metadata:
start with an empty model
If it's LPGL, nope:)
On Wed, Apr 2, 2008 at 10:57 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
Hi guys,
Iam planning to start a new Tomahawk sandbox component that generates PDF
files.
I just want to ask whether I can use (iText) java library or not.
After checking its license, I found it LGPL
Sounds like a good idea. While we are at that we could also add a general
before- and afterUpdateJSHook=jsFunction which will be executed
before and after the group has been updated. this way users could for instance
implement their own loading message display or just postprocess the updated
Thank you :).
On Wed, Apr 2, 2008 at 10:12 PM, Cagatay Civici [EMAIL PROTECTED]
wrote:
If it's LPGL, nope:)
On Wed, Apr 2, 2008 at 10:57 PM, Hazem Saleh [EMAIL PROTECTED]
wrote:
Hi guys,
Iam planning to start a new Tomahawk sandbox component that generates
PDF files.
I just want to
[
https://issues.apache.org/jira/browse/TRINIDAD-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Cooper updated TRINIDAD-822:
-
Resolution: Fixed
Fix Version/s: 1.2.8-core
1.0.8-core
Matt,
On Wed, Apr 2, 2008 at 9:33 PM, Matt Cooper [EMAIL PROTECTED] wrote:
Thank you Adonis.
I think they all look great. I noticed there is one minor anomaly in
the Tomahawk logo on the far-left side, there's a portion of the green
logo that shows up as all gray whereas in the other
After checking its license, I found it LGPL and MPL.
the MPL works, IMO
Here is the url :
http://www.lowagie.com/iText/download.html
Please tell me if I can use it or not.
Thanks all.
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
--
Matthias Wessendorf
further
Hello again,
Since I didn't see a response to my question I did a bit more searching
and noticed the following BUG listing (655), and was wondering, since it
is listed as still open, if this was something that is being looked at
or should I look for an alternative implementation? (which seems to
[
https://issues.apache.org/jira/browse/TRINIDAD-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584777#action_12584777
]
Piotr Steininger commented on TRINIDAD-997:
---
This is definitely a good example
+1 As I always said. They look great! Where's the t-shirt? :)
Bruno
On 02/04/2008, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Matt,
On Wed, Apr 2, 2008 at 9:33 PM, Matt Cooper [EMAIL PROTECTED] wrote:
Thank you Adonis.
I think they all look great. I noticed there is one minor
[
https://issues.apache.org/jira/browse/TRINIDAD-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584847#action_12584847
]
Davide Bonicelli commented on TRINIDAD-1030:
I set up a plain Trinidad page
Hi,
AFAIK the navigationTree renderer is an old UIX deprecated renderer
and doesn't handle skinning correctly as you noticed.
It should be refactored, but neither I nor somebody else found time to do
it.
But, I think you can use the normal tree component
with command components in it.
cheers
Hi
I have a design question. I'm working on generate component tag classes
using velocity.
In this part it is common to found some situations when you need utility
methods. There are several methods
to do this:
1) Implementing this methods on a java class, and use the following code
using a
58 matches
Mail list logo
