Keerthi P

Ranch Hand
+ Follow
since Aug 19, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Keerthi P

It appears the Kindle version of Jeanne's book (link below) is pretty old. I hear the latest reprint of the book contains most of the errata addressed in the print. Where can I buy an ebook (any format works for me) version of the latest reprint?

is same as

9 years ago
You may want to add enctype="multipart/form-data" to your form tag. The standard h:form supports this attribute. Typical usage is as below:

You seem to be using ice faces. Check the documentation of ice:form tag.
9 years ago
I have a custom JSF component that renders navigation links. The following is a typical usage of the component:

And, the rendered content will appear as following, similar to the navigation links at the top of this page:

Primary Data | Principals | Administrators | Custodiams | Accounting Firms | Law Firms | Billing

As you notice, the navigationBar component is bounded to #{testBean.navigationBar} which is defined as below in the Backing bean:

The backing bean has an action method formSubmitted() that adds a child (HtmlNavigationLink) component to the parent (HtmlNavigationBar) dynamically. I thought that this newly added child would be the last child (as it is added to end of the children list). But, when the navigationBar renders its children, the HtmlNavigationLink 'New link' appears as the first child causing the content rendered as below:

New Link | Primary Data | Principals | Administrators | Custodiams | Accounting Firms | Law Firms | Billing

The following is the encodeChildren() method of HtmlNavigationBar

As noted in the comment above, while the link was added to the end of the list in the action method, it appears at index position 0 as the first child? Why is it so?
9 years ago

It (the Business Delegate) is passed to a remote facade.

You may want to reconsider this design.
Why not? Do not confuse JMS with MDBs.
No you don't have to. You can still take SCBCD.

but what if nothing for that bean is spesified in <container-transaction > in the <assembly-descriptor> section - does the methods run in no transaction or is it also 'Required' for all by default ?

That is solely upto the container implementation. The spec does not guarantee what the transaction will be if the attribute is not specified.
Did you search in this forum? Thats a good way to get the answer quickly.
You can do it. If you are using JAXP based parsers, you can use Classloader.getResourceAsStream() and pass a reference to the XML file to the 'InputSource' of the 'DocumentHandler'. I was able to implement this for parsing a number of XML files that contained sophisticated rules. I packaged the XML files as part of the .ear file and transformed them to Java objects from web-layer components. It worked flawlessly in OS/390 (Mainframe) too.

Note: In the case mentioned above the parser was invoked by web-layer components (Custom JSP Tags and Application Controller Servlet).
[ May 03, 2005: Message edited by: Keerthi P ]
Assume you have two clients C1 and C2 accessing an entity bean E1. C1 looksup E1 and passes the reference to the beans remote object to a C2's method as a parameter. This is just one case substantiating the point 1. Its a simple thing, but sounds so difficult in the spec - An entity bean's remote object's reference can be received as a parameter of a method.
Use it with Jboss or JoNAS.
What version of IBM Websphere are you using? 5.x is J2EE1.3 compliant. 6.x is J2EE1.4 compliant.
[ April 30, 2005: Message edited by: Keerthi P ]