|
Home > Archive > WebSphere Portal Server > March 2004 > Portlets that access EJBs inside Portal Test Environment
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portlets that access EJBs inside Portal Test Environment
|
|
| tdperez 2004-03-25, 9:45 am |
| I have a portlet application which accesses some EJBs in a separate enterprise application. It works fine inside WPS 5, but inside the Portal Test Environment (WSAD 5.1 + Toolkit 5.0.2) I got a bunch of errors.
Is there anybody out there who is able to test a portlet application that accesses EJBs and run both applications (portlet and enteprise) from within the WSAD? How can I do it?
| |
| objectus 2004-03-25, 2:34 pm |
| I'm sorry to say that it doesn't really work. There are some significant issues with the portal test environment and this is one of them. Are you getting a ClassCastException?
You might be able to get some help from IBM if you open a PMR on this issue.
Good luck.
--Kevin
http://www.SurgingSystems.com
| |
| tdperez 2004-03-25, 2:34 pm |
| This is precisely what is happening. This information about it being a limitation is a official one?
I'm trying to figure out if it is possible to deploy the enterprise application inside a normal WAS Test Environment and deploy the portlet application inside the WPS test environment and then customize the InitialContext's URL so when the EJB is called f
rom whithin the portlet application the enterprise application's JNDI tree is actually found. I didn't suceeded doing it, 'till now. Did you try some workaround like this?
| |
| objectus 2004-03-25, 5:34 pm |
| Yes, I believe that is an official limitation from IBMs point of view. Thi=
s doesn=92t mean they=92ll be unresponsive, however.
We wanted our test environment to =93look=94 the same as our production env=
ironment, which meant that we didn=92t want to have to parameterize the JND=
I context.
Instead, we opened a PMR with IBM, asking them to resolve the issue with de=
ploying a EAR within the portal test environment, and being able to referen=
ce Java projects from portlet projects, the same way you can in the WAS tes=
t environment.
Note that, when you=92re testing, you can deploy an EAR to the full portal =
server and you won=92t have any JNDI issues there. I don=92t believe this =
is a valid production configuration, of course, and it=92s a quite painful =
debug configuration.
--Kevin
http://www.SurgingSystems.com
| |
| tdperez 2004-03-25, 6:34 pm |
| Ok, Kevin, thank you a lot. We'll probably open a PMR too. If you have any new information on the subject, please post it.
Taciano
|
|
|
|
|