Hi Piyush,
behind my firewall (same as yours ;) ) it works fine.
The file was downloaded from here:
Downloading:
http://stacy27.us.oracle.com/mirrors/www.ibiblio.org/maven2/com/jcraft/jsch/0.1.27/jsch-0.1.27.pom
965b downloaded
Since that is a mirror, the file is available here as well:
f:param should display a warning if name=id
-
Key: MYFACES-1723
URL: https://issues.apache.org/jira/browse/MYFACES-1723
Project: MyFaces Core
Issue Type: Improvement
Components: General
Tobago.registerCurrentScripts in standard tobago.js misses a null check
---
Key: TOBAGO-484
URL: https://issues.apache.org/jira/browse/TOBAGO-484
Project: MyFaces Tobago
[
https://issues.apache.org/jira/browse/TOBAGO-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-484.
-
Resolution: Fixed
Fix Version/s: 1.0.12
child.src is checked by typeof:
... typeof
tc:menu and links
Key: TOBAGO-485
URL: https://issues.apache.org/jira/browse/TOBAGO-485
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Reporter: adam
tc:menuBar
tc:menu label=Home
Hello Jeanne,
Personally you won't break anything with my projects, but it's only because
I fully converted the skin to use the new Trinidad URL system (well it's
more Trinidad URL system than new actually). However, preventing the '..'
will most likely make the passage between ADF Faces and
Hi,
I like to remove the ajax-enabled option from tobago-config.xml.
Or at least change default to true.
This option cames from the beginning of ajaxifying tobago and is just
ignored on most ajax components, but some components (e.g. sheet) did
not work when loaded by ajax if ajax-enabled is
, but in FF2 it does.
(no Trinidad isn't rendering something like autocomplete=off)
A simple test-case for that is:
1) Go to (in FF2):
http://example.irian.at/trinidad-demo-20070912/faces/components/inputText.jspx
clear out the value Some text and enter a new value, like ABC and
press submit.
2
Hi!
I noticed that this doesn't show up in IE7, but in FF2 it does.
(no Trinidad isn't rendering something like autocomplete=off)
Christian Swoboda already posted about a bug in IE
His text:
Hi!
We are developing a new application with myfaces 1.1.5 and discovered
that there's a
Also, but not directly linked to this, autoSubmit is no longer triggered
from selection from the autocomplete list with FF 2.x while it was in FF 1.x
Regards,
~ Simon
On 9/12/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I noticed that this doesn't show up in IE7, but in FF2 it does.
+1
On 9/11/07, Simon Lessard [EMAIL PROTECTED] wrote:
+0
On 9/11/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
+1
Matthias Wessendorf wrote:
+1
On 9/11/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi all,
this is the official vote for MyFaces Maven 1.0.6 and MyFaces
Do such URLs in skins actually result in incoming URLs containing
.., or does it get resolved out when we generate the .css?
-- Adam
On 9/12/07, Jeanne Waldman [EMAIL PROTECTED] wrote:
Hi Simon,
Very good point. I have seen skin's have .. in the background-image path.
I forgot about
Hi Christian,
please file an issue, that we keep at least track of this problem.
Perhaps the work around should only be done, when the app actually runs in IE.
Greetings,
Matthias
On 9/10/07, Christian Swoboda [EMAIL PROTECTED] wrote:
Hi!
We are developing a new application with myfaces
IE7 - AutoComplete Does Not Work When You Use Script to Submit a Form
-
Key: TRINIDAD-704
URL: https://issues.apache.org/jira/browse/TRINIDAD-704
Project: MyFaces Trinidad
I tried it, and it resolves out the "..". It doesn't call
ClassLoaderResourceLoader.
This is what I tried:
In purple skin:
af|selectOrderShuttle::reorder-bottom-icon {
background-image: url('../../adf/images/tab3-start-selected.gif');
width: 16px;
height: 16px;
}
and it is this in the css
[
https://issues.apache.org/jira/browse/TRINIDAD-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526852
]
Matthias Weßendorf commented on TRINIDAD-700:
-
this is true for timeStyle=#{bean.style} as well.
The
DirectoryResourceLoader doesn't restrict access outside the root directory like
it advertises
-
Key: TRINIDAD-705
URL: https://issues.apache.org/jira/browse/TRINIDAD-705
[
https://issues.apache.org/jira/browse/TRINIDAD-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-700.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Assignee: Matthias
Getting Started Needs Updating
--
Key: MYFACES-1724
URL: https://issues.apache.org/jira/browse/MYFACES-1724
Project: MyFaces Core
Issue Type: Improvement
Components: website
Affects Versions: 1.2.0
Hi all,
Shuttle behavior is not the same as other selectMany components for purpose
of retrieving the submitted values in two way. Firstly, shuttles submit a
single parameter with values separated by ';'. That difference cannot really
be changed. However, shuttles also do a first validation in
[
https://issues.apache.org/jira/browse/TRINIDAD-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-705.
-
Resolution: Fixed
SVN on trunk 575024
DirectoryResourceLoader doesn't restrict
On 9/12/07, Simon Lessard [EMAIL PROTECTED] wrote:
Hi all,
Shuttle behavior is not the same as other selectMany components for
purpose of retrieving the submitted values in two way. Firstly, shuttles
submit a single parameter with values separated by ';'. That difference
cannot really be
The CSSUtils code isn't perfect. If you have a bunch of ".." in the
string, then it doesn't resolve them all out:
.af_selectOrderShuttle_reorder-bottom-icon {
background-image:url(/trinidad-demo-context-root/skins/purple/tmp/xyz/abc/def/../../foo/
Oups it seems that I stripped some important information when I reread
myself (one of the few times I did).
The size check is done in getSubmittedValue so it's called mainly during
conversion which is correct, but I don't think getSubmittedValue should do
any validation, just return the String[].
Hi all,
I would like to add two facets to statusIndicator: busy and ready, each
with an attached styleClass placed on a child span element. I think it would
make the component much more customizable as it would allow something like:
tr:statusIndicator
f:facet name=busy
tr:outputText
+1 great idea
I would also like to suggest javascript support as well:
tr:statusIndicator onbusy=alert('starting ajax');
onready=alert('ajax done'); /
This would probably be a simple hook around:
TrPage.getInstance().getRequestQueue().addStateChangeListener(func);
But it would be easier to
I like the facets a lot too, but I'm not thrilled with adding
extra JS attributes when we already have a JS hook.
Two ways of doing things only makes sense when the second
is much easier, not just marginally easier.
-- Adam
On 9/12/07, Andrew Robinson [EMAIL PROTECTED] wrote:
+1 great idea
You're right, it'd be good if the Renderer did the check in
getConvertedValue(), but not
in getSubmittedValue().
-- Adam
On 9/12/07, Simon Lessard [EMAIL PROTECTED] wrote:
Oups it seems that I stripped some important information when I reread
myself (one of the few times I did).
The size
JSF 1.2: Non-EL attributes of tags are always generated as Strings
--
Key: TRINIDAD-706
URL: https://issues.apache.org/jira/browse/TRINIDAD-706
Project: MyFaces Trinidad
Issue
Do you plan to toggle the styleclass display property depending upon
the state?
Simon Lessard wrote:
Hi all,
I would like to add two facets to statusIndicator: "busy" and "ready",
each with an attached styleClass placed on a child span element. I
think it would make the component much more
Hi Jeanne,
statusIndicator already does that on clientId::ready and clientId::busy
elements, the skin won't have to do it.
~ Simon
On 9/12/07, Jeanne Waldman [EMAIL PROTECTED] wrote:
Do you plan to toggle the styleclass display property depending upon the
state?
Simon Lessard wrote:
Hi
31 matches
Mail list logo