Status: Resolved (was: Patch Available)
Thanks to Gary van Matre for the patch.
> Servlet external context wrapper missing JSF 2 API
> --
>
> Key: TRINIDAD-2457
> URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/TRINIDAD-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary VanMatre updated TRINIDAD-2457:
Status: Patch Available (was: Open)
> Servlet external context wrapper missing JS
Gary VanMatre created TRINIDAD-2457:
---
Summary: Servlet external context wrapper missing JSF 2 API
Key: TRINIDAD-2457
URL: https://issues.apache.org/jira/browse/TRINIDAD-2457
Project: MyFaces
tail without explicitly defined id and without
applied TRINIDAD-2216-2259-2302.patch (with
if(COMPONENT_FAMILIES_SHOULD_RENDER_ID.contains(family)) check)
> The partialSubmit does not work with JSF 2 RI
> -
>
>
Available)
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
> Project: MyFaces Trinidad
>
ters have the time to check this and integrate the
patch?
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
&g
.request:
source not set" still exist.
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
>
ommitting this, have you tried the trinidad trunk to
see if this is still an issue. Technically speaking, Trinidad 2.1, not
Trinidad 2.0 should be used with JSF 2.1
> The partialSubmit does not work with JSF 2 RI
> -
>
>
.
*/
// TODO Is this a bottleneck? If so, optimize!
protected boolean shouldRenderId(
...
But I can not find any code that does this really what's in the comment.
Not even in the subclasses.
Patch proposal follows...
> The part
tected boolean shouldRenderId(
...
But I can not find any code that does this really what's in the comment.
Not even in the subclasses.
Patch proposal follows...
> The partialSubmit does not work with JSF 2 RI
> -
>
>
a null
to be passed as source parameter in the jsf.ajax.request call and finally ends
as error like "jsf.ajax.request: source not set" in Mojarra.
> The partialSubmit does not work with JSF 2 RI
> -
>
>
ever be found
by the script, which searches the element in the DOM tree. This causes a null
to be passed as source parameter in the jsf.ajax.request call and finally ends
as error like "jsf.ajax.request: source not set" in Mojarra.
> The partialSubmit does not w
have attached seems to be the solution of the problem!
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
&g
ched seems to be the solution of the problem!
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
>
[
https://issues.apache.org/jira/browse/TRINIDAD-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Schoch updated TRINIDAD-2216:
Status: Patch Available (was: Open)
> The partialSubmit does not work with JS
duce the problem. Unfortunately it was reported on
February and still hasn't even been assigned to anyone.
> The partialSubmit does not work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
>
Hi
In the last year there was a lot of improvements done inside Apache
MyFaces JSF Implementation (aka MyFaces Core), thanks to the
suggestions provided by the community.
To show how good was the improvements done, an in-deep comparison was
done between JSF 2 and Wicket. The code, detailed
ot work with JSF 2 RI
> -
>
> Key: TRINIDAD-2216
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Comp
The partialSubmit does not work with JSF 2 RI
-
Key: TRINIDAD-2216
URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
Project: MyFaces Trinidad
Issue Type: Bug
Components
(was: Patch Available)
Thanks for the patch
> Missing new JSF 2 signatures on ServletExternalContext
> --
>
> Key: TRINIDAD-2151
> URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/TRINIDAD-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary VanMatre updated TRINIDAD-2151:
Status: Patch Available (was: Open)
> Missing new JSF 2 signatures
Missing new JSF 2 signatures on ServletExternalContext
--
Key: TRINIDAD-2151
URL: https://issues.apache.org/jira/browse/TRINIDAD-2151
Project: MyFaces Trinidad
Issue Type: Bug
nd resourceName would not be necessary!
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The problem is "should not be used" is not an option. I'm saying
>>>>>>>>>
gt;>>>>>>>>> ..thus producing a resource with libraryName="de/mydir" and
>>>>>>>>>>> resourceName="myresource.js". And this is exactly what is
>>>>>>>>>>> expected
>>>>>>
ult one. The first call expect the default one, but the second?.
>>>>>>>>>
>>>>>>>>> In conclusion, if the example does not fulfit the two conditions (be
>>>>>>>>> 1:1 and symmetric), for any imaginable Resource instance, it wi
>> did
>>>>>>>>> not have this filter, but I don't like that anyway (see above).
>>>>>>>>>
>>>>>>>>
>>>>>>>> Why don't you like it? do you have something better in mind?. If you
>>
s or critics.
>>>>>>>>
>>>>>>>>>> My interest is put this as a module for JSF 2.0, because there is
>>>>>>>>>> nothing that prevent us doing it, and this is the "base stone" to
>>>>>>>>
on the AdvancedResourceHandler
>>>>>>>> before (it was all my code) and it was a pretty big commit (even took
>>>>>>>> 2 commit-mails). Thus you gave me no choice to take a look at it and
>>>>>>>> discuss the changes with you. If I d
it, there is no harm
>>>>>> or you don't have to do something difficult to revert the code,
>>>>>> right?. Note the code has not released yet, so we don't have to
>>>>>> preserve the package or the class name or any structure.
>
ution:
>>>>>>>>
>>>>>>>> 1) If I have to configure a Filter in web.xml I can just as good
>>>>>>>> define a prefix mapping for the FacesServlet. I don't see why an
>>>>>>>> additional Filter is
;
>>>>>>> 2) The locale in the resource path really is essential, please do NOT
>>>>>>> remove it. I did a lot of tests with different browsers about this and
>>>>>>> you just cannot verify that every user will get the right (localized)
>&
ight change!
>>>>>>
>>>>>
>>>>> Ok, good to know that. The current code works "forcing" output the
>>>>> locale, so we can just let things as is.
>>>>>
>>>>>> 3)
>>>>>
rmore the classpath might change!
>>>>>>
>>>>>
>>>>> Ok, good to know that. The current code works "forcing" output the
>>>>> locale, so we can just let things as is.
>>>>>
>>>>>> 3)
>>&
k the opposite in this case, because the previous syntax is
>>>> ambiguous, so you can't decide how to get the libraryName and
>>>> resourceName from the resourceBasePath, and the spec requires describe
>>>> that in a explicit way. Think about a resourc
s doing it, and this is the "base stone" to make
>>> components with libraries like dojo, that requires load modules from
>>> derived base paths. After that, we can push this on the spec for JSF
>>> 2.2 and the EG will decide.
>>>
>>> regar
using #resource['..'])
>>>> b. caching resources in the client (disabled if ProjectStage ==
>>>> Development)
>>>> c. GZIP compression and local cache in tmp dir (disabled if
>>>> ProjectStage == Development)
>>>> d. i
>>>
>>> The most important one is number 3. (make it work with suffix
>>> mapping), because it limits the scope where a. (relative paths between
>>> resources) could be applied. Use a parse on some files it is not a
>>> very good solution, so
erFilter
>>
>>
>>
>> Faces Filter
>> /javax.faces.resource/*
>>
>>
>> and that's it. In this way, there is no need to any parser, just put
>> the files on a library, register it on the xml file. If you are using
&g
ry, register it on the xml file. If you are using
> prefix mapping for Faces Servlet, you will not need that entry,
> because everything will be handled from Faces Servlet.
>
> With this solution, javascript libraries like dojo that loads files or
> have css resources with url(.
:
https://issues.apache.org/jira/browse/MFCOMMONS-30
Change URL management of Advanced JSF 2 ResourceHandler
The idea was use this
http://{server}[:port]/{appPath}/javax.faces.resource/{locale}/{libraryName}/[resourceName]
Unfortunately, this syntax is ambiguous, because it is not possible to
ident
.
>>
>> That is not very hard to do, but it is a valuable contribution to do.
>> Suggestions are welcome.
>>
>> regards,
>>
>> Leonardo Uribe
>>
>> 2011/3/8 Jakob Korherr :
>>> Hi,
>>>
>>> I just committed the cod
t; Leonardo Uribe
>
> 2011/3/8 Jakob Korherr :
>> Hi,
>>
>> I just committed the code, see r1079447.
>>
>> In addition, I created the following issue for reference in the jira:
>> MFCOMMONS-29.
>>
>> Feel free to look at it, use it, change i
following issue for reference in the jira:
> MFCOMMONS-29.
>
> Feel free to look at it, use it, change it,... - input is always welcome :)
>
> Regards,
> Jakob
>
> 2011/2/23 Jakob Korherr :
>> Hi guys,
>>
>> I developed a custom JSF 2 ResourceHandler
gth to sandbox for JSF 2 module
> ---
>
> Key: TOMAHAWK-1590
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1590
> Project: MyFaces Tomahawk
> Issue Type: Task
>
Uribe
> Move s:accordionPanel to sandbox for JSF 2 module
> -
>
> Key: TOMAHAWK-1589
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1589
> Project: MyFaces Tomahawk
>
Move s:passwordStrength to sandbox for JSF 2 module
---
Key: TOMAHAWK-1590
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1590
Project: MyFaces Tomahawk
Issue Type: Task
Move s:accordionPanel to sandbox for JSF 2 module
-
Key: TOMAHAWK-1589
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1589
Project: MyFaces Tomahawk
Issue Type: Task
Components
of Advanced JSF 2 ResourceHandler
> ---
>
> Key: MFCOMMONS-30
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-30
> Project: MyFaces Commons
> Issue Type: Improvement
>
d in MFCOMMONS-30
> Advanced JSF 2 ResourceHandler
> --
>
> Key: MFCOMMONS-29
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-29
> Project: MyFaces Commons
> Issue Type: New Feature
>
Change URL management of Advanced JSF 2 ResourceHandler
---
Key: MFCOMMONS-30
URL: https://issues.apache.org/jira/browse/MFCOMMONS-30
Project: MyFaces Commons
Issue Type: Improvement
again, add invokeOnComponent code.
> tomahawk20-1.1.10 for JSF 2 does not work: aliasBean
>
>
> Key: TOMAHAWK-1562
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1562
> Project: MyFaces To
the necessary faces-config.xml
> Advanced JSF 2 ResourceHandler
> --
>
> Key: MFCOMMONS-29
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-29
> Project: MyFaces Commons
> Issue Type: New Feature
>
[
https://issues.apache.org/jira/browse/MFCOMMONS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MFCOMMONS-29.
Resolution: Fixed
Fix Version/s: 1.0.2-SNAPSHOT
> Advanced JSF 2 ResourceHand
just required to add it on the classpath.
> Advanced JSF 2 ResourceHandler
> --
>
> Key: MFCOMMONS-29
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-29
> Project: MyFaces Commons
> Issue Type:
this code in an own module, so that we can keep it
lightweight and also deliver the faces-config with the module!
> Advanced JSF 2 ResourceHandler
> --
>
> Key: MFCOMMONS-29
> URL: https://issues.apache.org/
Hi,
I just committed the code, see r1079447.
In addition, I created the following issue for reference in the jira:
MFCOMMONS-29.
Feel free to look at it, use it, change it,... - input is always welcome :)
Regards,
Jakob
2011/2/23 Jakob Korherr :
> Hi guys,
>
> I developed a cus
put on myfaces-commons-utils, so the user can
just add the resource handler on its webapp faces-config.
> Advanced JSF 2 ResourceHandler
> --
>
> Key: MFCOMMONS-29
> URL: https://issues.apache.org/jira/
Advanced JSF 2 ResourceHandler
--
Key: MFCOMMONS-29
URL: https://issues.apache.org/jira/browse/MFCOMMONS-29
Project: MyFaces Commons
Issue Type: New Feature
Affects Versions: 1.0.2-SNAPSHOT
Hi guys,
I developed a custom JSF 2 ResourceHandler for one of my current
projects and I want to "donate" it to MyFaces commons (JSF 2 branch).
The features of this ResourceHandler include the following:
- relative paths between resources (css files referencing images
without using
for t:aliasBean, so that i can move
forward.
> tomahawk20-1.1.10 for JSF 2 does not work: aliasBean
>
>
> Key: TOMAHAWK-1562
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1562
> Pro
here.
> tomahawk20-1.1.10 for JSF 2 does not work: aliasBean
>
>
> Key: TOMAHAWK-1562
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1562
> Project: MyFaces Tomahawk
>
wk12-1.1.10
> tomahawk20-1.1.10 for JSF 2 does not work: aliasBean
>
>
> Key: TOMAHAWK-1562
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1562
> Project: MyFaces Tomahawk
>
not support JSF 2 source parameter for paging
>
>
> Key: TRINIDAD-2020
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2020
> Project: MyFaces Trinidad
>
TableRenderer does not support JSF 2 source parameter for paging
Key: TRINIDAD-2020
URL: https://issues.apache.org/jira/browse/TRINIDAD-2020
Project: MyFaces Trinidad
Issue
tomahawk20-1.1.10 for JSF 2 does not work: aliasBean
Key: TOMAHAWK-1562
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1562
Project: MyFaces Tomahawk
Issue Type: Bug
g exactly what it is necessary to do for jsf.js
when it has not been rendered before.
It is still unknown it this behavior could cause problems on portlets case (at
the time I wrote this there is no any known JSF 2.0 portlet compatible
implementation yet).
> I think that MyFaces should use
text
<!--
//-->Some
text
> I think that MyFaces should use JSF 2 resource handling instead of directly
> write script resources to t
ript resources you mean (maybe provide a
facelet page and the HTML output). As far as I know MyFaces uses the resource
handling mechanism in every possible place.
> I think that MyFaces should use JSF 2 resource handling instead of directly
> write script resources to the out
I think that MyFaces should use JSF 2 resource handling instead of directly
write script resources to the output stream
---
Key: MYFACES-2949
URL
encodeAll. This should be done for Trinidad 1.2 as
well.
> Trinidad 2 CoreRenderer.encodeChild does not call the JSF 2 encodeAll method
> on the child
> -
>
> Key
In Trinidad 2, both CoreRenderer and UIXComponentBase implement their
own version of encodeAll(FacesContext). The problem that I am seeing
is that if a component overrides encodeAll, it is not always called.
Looking at the UIComponent JavaDoc for J2EE 6, I do not see that it is
clear if someone may
Trinidad 2 CoreRenderer.encodeChild does not call the JSF 2 encodeAll method on
the child
-
Key: TRINIDAD-1927
URL: https://issues.apache.org/jira/browse/TRINIDAD-1927
Hi,
Tomahawk is working now as I found out that the form tag I used was wrong.
It should be h:form.
sorry for the previous post.
Kind regards
Fiona
--
View this message in context:
http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29600755.html
Sent from the My Faces
Hi the output as attachment. nabble_a
href="tomahawk+page.html">tomahawk+page.html
--
View this message in context:
http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29600265.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
anks
Fiona
--
View this message in context:
http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29600219.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
firstStyleClass="previous-off" />
>
>
> previousStyleClass="previous-off" />
>
>
> nextStyleClass="next-off"/>
>
Fiona
--
View this message in context:
http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29577991.html
Sent from the My Faces - Dev mailing list archive at
y-of-Tomahawk-%2B-JSF-2-tp29537768p29549942.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
83)
>
>
> Could you tell me how I should config my application? And also, does this
> build work with JSF2 or I need Myfaces 2 to make it to work?
>
>
That one seems to be a problem not related to tomahawk. No special
configuration is required. You can
see an application r
e.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29549725.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
t; tomahawk version (may be latest or under development) which will work
>> with
>> JSF 2.0?
>>
>> Kind Regards
>> Fiona
>> --
>> View this message in context:
>> http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29
which will work with
> JSF 2.0?
>
> Kind Regards
> Fiona
> --
> View this message in context:
> http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29537768.html
> Sent from the My Faces - Dev mailing list archive at Nabble.com.
>
>
d of making it to
work with JSF 2.0. Could someone tell me what I can do? or Can I have the
tomahawk version (may be latest or under development) which will work with
JSF 2.0?
Kind Regards
Fiona
--
View this message in context:
http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-J
ion, expand and collapse image component manipulation does not
> work well with PSS on JSF 2
> -
>
> Key: TOMAHAWK-1540
> URL: https://issues.apache.org/ji
t:tree2 navigation, expand and collapse image component manipulation does not
work well with PSS on JSF 2
-
Key: TOMAHAWK-1540
URL: https://issues.apache.org
amp does not work well with jsf 2 ajax
> --
>
> Key: TOMAHAWK-1535
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1535
> Project: MyFaces Tomahawk
> Issue Type: Bug
t:dataTable detailStamp does not work well with jsf 2 ajax
--
Key: TOMAHAWK-1535
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1535
Project: MyFaces Tomahawk
Issue Type: Bug
Bean instead of beans defined in facesconfig.xml
- Converted JSP as view technology to XHTML (Facelets) [If needed]
- Used Composite Facelets components instead of taglib solution
No extensive testing yet.
> Create examples for JSF 2 version
> -
>
>
override configuration for test cases. I think at this
point we have all mock objects we require to be added on a test case to work
without problem.
> Update AbstractJsfTestCase to jsf 2
> ---
>
> Key: MYFACESTEST-12
>
to jsf 2
>
>
> Key: MYFACESTEST-11
> URL: https://issues.apache.org/jira/browse/MYFACESTEST-11
> Project: MyFaces Test
> Issue Type: Improvement
>Reporter: Leonardo Uribe
>
Create examples for JSF 2 version
-
Key: EXTVAL-111
URL: https://issues.apache.org/jira/browse/EXTVAL-111
Project: MyFaces Extensions Validator
Issue Type: Task
Affects Versions: 2.0.4-SNAPSHOT
Update AbstractJsfTestCase to jsf 2
---
Key: MYFACESTEST-12
URL: https://issues.apache.org/jira/browse/MYFACESTEST-12
Project: MyFaces Test
Issue Type: Task
Components: Test suites
Update ConfigParser to jsf 2
Key: MYFACESTEST-11
URL: https://issues.apache.org/jira/browse/MYFACESTEST-11
Project: MyFaces Test
Issue Type: Improvement
Reporter: Leonardo Uribe
Assignee
added a new
component called t:autoScrollPage. It attach a view listener for
PostAddToViewEvents and a component listener to viewRoot, to make the view
listener be restored each time. I think this is the cleanest solution for this
issue.
> Update autoscroll feature to JS
o work on that plugin.
>
> Fwiw it works with OWB too without any changes.
>
> LieGrue,
> strub
>
> --- On Thu, 5/20/10, Michael Kurz wrote:
>
> > From: Michael Kurz
> > Subject: Re: [JSF 2] Make jetty:run work
> > To: dev@myfaces.apache.org
> > Dat
Michael, I'll check it on the weekend.
I'm maven and codehaus committer also, so I'll try to work on that plugin.
Fwiw it works with OWB too without any changes.
LieGrue,
strub
--- On Thu, 5/20/10, Michael Kurz wrote:
> From: Michael Kurz
> Subject: Re: [JSF 2] Make jet
The problems occur with JSF 2-Annotations for configuring managed beans,
converters... With Spring everything should work fine.
regards
Michael
Am 20.05.2010 17:09, schrieb Bruno Aranda:
Mmh, jetty:run works for me out of the box. I use it all the time. Is
this because I use Spring? It can
Mmh, jetty:run works for me out of the box. I use it all the time. Is this
because I use Spring? It can perfectly fine the annotations in the
target/classes without me having to setup anything...
Bruno
On 20 May 2010 15:47, Michael Kurz wrote:
> Hi guys,
>
> I did some work on the jetty-maven-p
Hi
Ok, +1
regards,
Leonardo
2010/5/20 Michael Kurz
> Hi guys,
>
> I did some work on the jetty-maven-plugin to enabling starting MyFaces 2
> and Mojarra 2 apps with jetty:run. The problem in this case is, that
> annotation scanning looks for /WEB-INF/lib and /WEB-INF/classes which do not
> ex
Hi guys,
I did some work on the jetty-maven-plugin to enabling starting MyFaces 2
and Mojarra 2 apps with jetty:run. The problem in this case is, that
annotation scanning looks for /WEB-INF/lib and /WEB-INF/classes which do
not exist with jetty:run.
There already was an issue for Jetty regar
1 - 100 of 149 matches
Mail list logo
