C Bell

Greenhorn
+ Follow
since Jun 29, 2009
Java programmer
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by C Bell

I would think you can use your desktop client to generate a web session, just as the online piece does. For security purposes each client should require the user to log in. Then based on existing server sessions determine your correct path of operations.
6 years ago
I had this same issue. It requires you to specify "-Dweblogic.security.SSL.protocolVersion=SSL3" in your start-up script to define your SSL protocol.
6 years ago
I have a basic home page in my ICEfaces w/ facelets application. When I view the app in Internet Explorer none of the commandlinks work. But viewing the page in Firefox everything looks fine.

The rendered markup for both browsers are the same. Has anyone else experienced this?

Internet Explorer

Firefox


Thanks for all of your help.
10 years ago
JSF
Try updating your code to this,


You put another set of double quotes in your javascript onclick method, which would break the tag.
10 years ago
JSF
Hello John,
Try using the jstl tag set, http://java.sun.com/javaee/javaserverfaces/2.0/docs/pdldocs/facelets/c/set.html, to replace your jsp:setProperty.
10 years ago
JSF
Kathiresan,
Could you please inform us of the issue you are having? I have seen error messages in my server console for WeblogicInjectionProvider but none that have stopped JSF 2.0.1FCS (Mojarra) from working.
10 years ago
Deployment System: JSF 2.0.1.FCS Mojarra Implematation on Weblogic 10.3 appserver
No Spring or Hibernate.

Synopsis:
I have a table screen where a user can click an action (ie. edit, view) link on each row of data.
1. The user clicks a link on the table and receives a page (page 1) of information.
2. The user clicks an action on page 1, the user is then directed to the next page. On this page (page 2) there is no information.

If the user was to navigate back the table page and re-execute the previous actions the issue is resolved and there is no lose of bean information.
Both page 1 and page 2 contain the same managed bean (myBean).

Managed Bean info:
Name: myBean
Scope: Session

I have been on this issue for a few weeks, if anyone can assist please do.
If it helps, I always modify the request scope map before I return my actionString. I put an updated (from DB) myBean in this map.


Thank you in advance
10 years ago
JSF