Releases intended for use with JSF 1. See the series of articles and the update for at JSFCentral: For now, you can mostly ignore all of the subprojects except the “core” one. Currently Sep it’s located at https: Mojarra at the current time JUN has some nasty bugs related to state saving, that MyFaces does not have because its implementation is completely different. I don’t work for Mojarra. I am – lets say -slightly- reluctant knowing how many bugs we had to fix for JSF 1.

myfaces jar jsf-2.0

Uploader: Neshicage
Date Added: 23 September 2012
File Size: 46.63 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 4573
Price: Free* [*Free Regsitration Required]

Download myfaces-api-2.0.2.jar : myfaces api « m « Jar File Download

Ideally, there would be just one “shared” project, and any other project that wishes to “import” the shared code would perform the necessary renaming. BalusC myfzces gold badges silver badges bronze badges.

myfaces jar jsf-2.0

Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. Unicorn Meta Zoo 9: Unfortunately jsr had a number of drawbacks, the most serious being that only versions of Core and Tomahawk that use the same version of the shared library could be deployed together.

Also the download page is indeed JSF Mojarra? Releases intended for use with JSF 1. Bugs often expose only later and robustness can only be evaluated during the aftermath. This allows various projects mjfaces use the shared code to be mixed without conflicts over shared code versions, and allows different release cycles for each project. And did you file bug reports? Their homepage has been moved around several times.


But give me a discount, it was late yesterday and i already wasted 6 hours trying to fix this problem. See MyFaces Mailing Lists. I’ve seen you doing work with the mojarra team.

Well, i “believe” it’s a mojarra bug couldn’t find official bug report though – Only this: The shared library versions intended for use with JSF 1. In particular, MyFaces Core and Tomahawk have quite a lot of common code.

Setting breakpoints can also be a little tricky; when debugging tomahawk for example, make sure that a breakpoint set in a class from the shared project is set on the version with package name “org. However rather than relying on custom classloaders to implement this as OSGi requiresa simple package hack is being done.

Download myfaces-apijar : myfaces api « m « Jar File Download

I am starting on JSF2. Documentation About Core Javadocs. The answer comes from my blog: What are the main disadvantages of Java Server Faces 2. All it took was exchanging the JARs and removing Myfaces-specific entries in web. The compatibility would not only need to avoid breaking any APIs, but would also need to ensure that no behaviour changed between releases.


Subscribe to RSS

That’s hard to do. This is the numbers for closed issues over the time: All i know is that the code looks ok. There are two primary reasons why shared is not just a jarfile that other projects put on their classpath.

Asked 8 years, 9 months ago.

Download – JavaServer

Email Required, msf-2.0 never shown. How do you know it was Mojarra’s fault and which version and not you doing something wrong where Mojarra rightfully failed and MyFaces is unrightfully accepting something that was against the specs? If a user wanted to upgrade myyfaces a newer release of Tomahawk to fix a bug, then they had to upgrade to the matching version of the shared lib – which then meant upgrading to the matching version of Core too.

In that case, the project declares a dependency on the JSF1.

myfaces jar jsf-2.0

At that moment aroundMyFaces was definitely the more stable alternative.