Workshop IDE for WebLogic Platform - JSF Portlet Development

Hello,
I am trying to develop JSF based portlets using BEA Workshop for WebLogic Platform IDE. The capabilities of the IDE in terms of JSF is like a simple text editor. Since the IDE is eclipse based, I wanted to to use some Third Party Plugin for JSF development.
I evaluated the following:
1. Workshop Studio for JSF
2. MyEclipse PlugIn for JSF
Problem 1:
Workshop Studio for JSF is a separate product and cannot be installed as an plugin over the Workshop IDE.
Is this acheivable?
Problem 2:
I created a Portal application Workspace through Workshop for Platform and opened the same using Workshop Studio for JSF. It crashed saying some runtime exceptions.
Problem 3:
MyEclipse PlugIn for JSF doesnt integrate properly with Workshop IDE. The Faces navigational flow view is not working properly.
Questions:
1. What is BEA's recommendation for JSF development?
2. Can you guide me how other developers are using the IDE for JSF development?
Thanks and regards,
Pazhanikanthan. P

Hi Pazhanikanthan,
Unfortunately, in the current release the JSF features cannot be used to create JSF portlets.
Please check the following URL for additional information on JSF portlet creation
http://e-docs.bea.com/wlp/docs92/portlets/building.html#wp1062147
If you are planning on building JSF web applications, you can always evaluate and purchase a copy of Workshop for JSF or Workshop Studio.
if you are planning on building JSF based pportlets, you will need to sue the tooling provided by Workshop for WebLogic 9.2
Applications built in Workshop for WebLogic cannot be imported into Workshop Studio. On the other hand, you can always create a webapp in Workshop Studio,a nd then import it into Workshop for WebLogic as a component.
hope this helps.
cheers
Raj
If you have additional questions specific to portlet development, please post to the portal newsgroup at http://newsgroups.bea.com/bea/forum.jspa?forumID=2044

Similar Messages

Need to add as a WSRP Connection in JDev for Weblogic Portal JSF Portlets.

I am trying to register WLP 10.3.4 JSF Portlets as a WSRP connection in JDev Webcenter 11.1.1.6 Portal Framework application . The below are steps:
-Created Simple WLP Application with JSF Portlets and deployed them on WLS 10.3.4 domain.
-The WSDL url available is http://localhost:7003/TEST_WEB_PORTAL/producer?wsdl
-Now Open JDev and created WCP Framwork app
-Under Application Resource, right click on Connections -> New Connection -> WSRP Producer.
-Click Next on step1 -> Enter WSDL URL on Step 2 and then click next on next 3 screens.
-It tries to register but ended up with below exception:
3-Dec-2012 12:48:03 oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil registerProducer
WARNING:
oracle.portlet.client.persistence.PersistenceException: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:473)
     at oracle.portlet.client.beanimpl.persistence.PersistenceBeanContext.commit(PersistenceBeanContext.java:128)
     at oracle.portlet.client.adapter.simple.SimpleAdapter.commit(SimpleAdapter.java:465)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.commit(PortletProviderManager.java:1487)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1647)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:597)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegistrationWizard$1.doWork(WSRPProducerRegistrationWizard.java:863)
     at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:161)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.core.UpdateableMOContent.constructConcurrentMOChangeException(UpdateableMOContent.java:1376)
     at oracle.mds.core.UpdateableMOContent.saveMOContent(UpdateableMOContent.java:1143)
     at oracle.mds.core.MDSTransaction.flushChangesToPTrans(MDSTransaction.java:851)
     at oracle.mds.core.MDSTransaction.internalCommit(MDSTransaction.java:2928)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:1022)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:850)
     at oracle.portlet.client.persistenceimpl.mds.MDSSessionWrapper.flushChanges(MDSSessionWrapper.java:61)
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:456)
     ... 10 more
Caused by: oracle.mds.persistence.DocumentExistsException: MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.internal.persistence.file.Fil
I have followed the steps given in the http://docs.oracle.com/cd/E26806_01/wlp.1034/e14235/chap_webcenter_interop.htm#BABGIIIJ for preventing User Authentication error by creating user of PortalSystemAdministrator group but did not help.
Please let me know if anyone have faced this exception or any pointers.
Thanks
Kamal Gulati

Hi,
I tried creating a simple JSF portlet and I can able to register and it is working Fine, but my teammet got the same issue like you :) . While Analyzing what I found is , the location where we created the portlet in weblogic portal. If you created your portlet directly under WebContent folder then this issue is coming up, so try to create the portlet in a folder inside the WebContent folder, say create a folder with name portlets under webcontent and create the JSF portlet inside that portlets folder.
Now start the server and register the same in WebCenter, you will not get that exception. I am going to raise a ticket with Oracle about this issue and get the root cause.
Thanks
Karthikeyan

WSRP Support Kit for WebLogic Platform 8.1 SP2

The WSRP Support Kit for WebLogic Platform SP2 has just been released at
http://dev2dev.bea.com/products/wlportal81/articles/wsrp_support_kit.jsp.
Please note that this is a preview release, and requires WebLogic
Platform 8.1 SP2.
Regards,
Subbu

There is a release planned for mid Summer, but it is too early to confirm.
In case you must add WSRP support to apps in platform domain, you can do
so manually, and here are the steps.
- Create a platform domain before installing WSRP Support Kit.
- Create a portal domain after installing WSRP Support Kit.
- Replace <Security> element in config.xml in the platform domain with
the one from portal domain.
- Add wsrp-common.jar file to the system classpath for the platform domain.
Let me know if this helps.
Subbu
Murtaza Sonaseth said the following on 01/07/2004 02:51 PM:
Is there an planned final release date for WSRP or at least a rough timeframe?
Thanks,
M Sonaseth.

Workshop IDE for Oracle Service Bus

Hi,
I have installed Oracle WebLogic Server 11gR1 (10.3.3) + Coherence - Package Installer (downloaded from http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html). And I downloaded oepe from net for using it as IDE for Oracle service bus. But when i open the eclipse, i do not get any option for creating the oracle service project.
Is there any plugin i need to put in eclipse for this to show up ??
John

You need to download Oracle Service BUs from here : This installer contains only OSB components and is not bundled with WLS and I think includes the eclipse plugins for Service bus projects.
http://www.oracle.com/technology/software/products/osb/index.html
There is a pre-requisite to download and install weblogic 10.3.3 + coherence +OEPE separately.

Ideas for Symbian Platform

If you have some ideas how make symbian better and you want to share with it please join to the symbian community
http://ideas.symbian.org/homepagelight
http://www.symbian.org/

Symbian is simply ****UGLY**** Take a look at the s^3 interface in N8 reviews, its just as ugly as the N97 interface. and it still looks as if it's just S60v3 ported to a touch device, the "options" and the "back" button on the bottom of the display are still there like in S60v3. Duhhhh, I mean seriously, there are better ways of controlling a touch interface than putting a touch sensitive version of the S60 "soft key" concept. Instead of copying the "non user-replaceable battery" idea from apple, they could have attempted copying the UI. But there's a problem, apple won't sue nokia if they copy a drawback of the iphone, but would definitely take steps if they copy an USP of the apple product I won't post an idea in that link you provided, instead I'd post an idea for nokia here, Dear nokia decision makers, Symbian is nonsense. Please drop symbian rubbish. You made a bad investment in symbian and you are punishing your loyal customers for a mistake that you made. There's still time, you are still number one. Please drop symbian while there's time. Best of luck.
Laugh, and the world laughs with you. Cry, and the world laughs louder :-)

Best IDE for WebLogic

Hi there,
Can anybody recommend the best IDE (JBuilder, WebGain, ...) for
developing EJBs on a WebLogic Server?
Any ones that are no good? Which is the one you would recommend?
Chris

Visual Slick Edit. Mmm. Donuts.
Do they still sell it?
Cameron Purdy
[email protected]
http://www.tangosol.com
Consulting Services Available
"Jesse E Tilly" <[email protected]> wrote in message
news:[email protected]...
[email protected] (Christof Prenninger) wrote in <3986a8c5
@newsgroups.bea.com>:
Hi there,
Can anybody recommend the best IDE (JBuilder, WebGain, ...) for
developing EJBs on a WebLogic Server?
Any ones that are no good? Which is the one you would recommend?
Chris
WARNING: Questions such as these can be akin to asking what is the onetrue
religion at a UN Assembly.
I have been desparately trying (for 4 months) to properly review four IDEs
in the hopes of finding something to beat Emacs (or Visual SlickEdit), a
command-line, and a third-party profiler/debugger (like JProbe). I have
and I've stopped. Here's why:
(1) When I started WebGain 4.0 didn't exist. Was I to suddenly trust a
buggy IDE (VisualCafe) being attached to what may or may not be a well
integrated suite of tools. I know StructureBuilder rocks, but how wouldit
work within these confines? My evaluation lasted two days. I counted the
number of crashes and where. I timed how long VC could stay open on my
machine (PIII 866/512MB). Final result? StructureBuilder (not an IDE,but
a class wizard that really does kick butt), over VisualAge, JBuilder,
Forte' and WebGain, offered the best bang for my buck in terms of
developing EJBs. Did we get it? No, but the reasons are not technical.
We already had Together/J to create class templates and didn't want to
spend $1000 per seat for a program that consolodates file templates and
command-line programs.
(2) Which brings me to cost. $3k (the usual street price for the
"enterprise" IDEs) is just too much. I told my company that I'd rather
have everyone handed a $3k bonus than to be saddled with an IDE (I'll
explain later). Java 2 SE and EE and all the libraries are free.
Furthermore, WebLogic wants you to use their compilation of the EE
libraries. Why should I pay $3k just to be able to compile theseprograms?
Only JBuilder and Forte allow you to compile EE programs, and only by
adding the libs yourself. VisualAge Pro won't let you import the library
and Cafe Pro balks as well. WebLogic has a plug-in for VAJ which allows
Pro, at $150 a good deal, to compile EE but the plug-in has its ownissues.
This, of course, does not address the reality of what you want, and thatis
wizards to create these special classes.
(3) Which brings me to code generation. Has anyone analyzed Visual Cafe's
generated code? It's pathetic. Monolithic, wasteful and very touchy.Any
manual adjustment may or may not break the IDE's interpretation of the
logic. JBuilder is no better. Forte' usually crashes before I get tocode
generation. Visual Age generates some dynamite (and complex) code.
(4) Which brings me to VisualAge. I think a lot of developers would agree
with me that if VisualAge had a "use repository/file system" toggle it
would be the hands-down, most kick-ass IDE in the land. It's a current
"change request" at IBM, but no promises have been made, that I know of.
The debugger is hands down the best of the big 4, it's visual composer is
easy to use, visualizes beans and components very well (considering the
limitations Java's AWT places on visual coding), and generates the best
component initializing code. If it wasn't for the repository. For the
unitialized, the repository is IBM's way of convincing (strongarming)
developers into having version control and on-the-fly code compilation.If
you begin and end your project in VisualAge and everything VAJ gives youis
fine, then VAJ is the way to go. However, if you already have a corporate
version control system (please tell me you do), you're at a loss as to how
to integrate with it. I worked at IBM and was told to use VisualAge. I
replied "How can it interface CMVC (IBM's workflow and VCS, which rules,
btw)?" The reply "Uh...we didn't think of that. Keep using Emacs". That
was 1997. Little has changed, apparently. That little is IBM'senterprise
repository, a way to let an entire group of developers have VAJ's
repository features across a network. Course, it's only available on the
enterprise version, don't pass go, cough up the $3k/seat. Oh, if you want
to not use the repository or need to have actual file system files (the
repository is one big file) you have to import and export your source
regularly. Not fun.
(5) Which brings me to version control. None of the offerings connect to
version control very well. That's not their fault. On Solaris, there is
no "scc" (windows' universal source control API, like ODBC cept forversion
control) so you go back to command line world. The IDE makers didn'tspend
a lot of time considering non-SCC solutions so you're pretty much screwed
on non-Wintel platforms. SCC? It sucks. It relies on the VCS vendor's
dlls. PVCS' SCC interface is buggy, slow and hard to use. Visual Source
Safe? I refuse to use it to manage source code, although it has thesecond
best SCC interface. The first? Perforce's. Course, it mimmicks RCS/CVS.
Concurrent version control has seem to have lost favor with people (BSD
uses it, you should too) and its concept is not reflected in the SCC
interfaces built on IDEs. Bottom line? SlickEdit + Perforce or Emacs +
CVS (or CMVC, a lisp module exists within IBM) is still the best
"integrated version control" development platform with propers given to
VisualAge and its repository for an alternative solution with no prior VCS
in place.
Trying to tell a group of eclectic and highly motivated (and paid) people
to settle on one development environment is very hard. Properly done, you
must settle on an IDE, have everyone trained (I can't stress thatenough.
Handing a hammer to a monkey usually results in broken skulls) in it and
use it religiously. For small startups like mine or fixed-budgetprojects,
this is just not feasible and thus we settled on a development environment
rather than an IDE.
Was that a long (it could be thorough) enough answer?
Jesse

Looking for ideas for a: Photo Gallery portlet

Hey all,
I'm wondering if anyone out there uses any special code or 3rd party apps, or anything to fancy-up a portlet to display photos?
For the last few hours I've been working to integrate CoolIris (http://www.cooliris.com) with a Publisher portlet but have run into a snag that I'm having some difficulty debugging. But rather than spinning my wheels on this one solution, I figured I'd reach out to all of you to see how you display event/holiday/etc types of pictures within your portals.
Ideally I'd love for our users to be able to submit images directly through a Publisher portlet and create something more flashy than just a static image that they have to scroll through.
Any thoughts?
Thanks!
Geoff

I'm looking for the same functionality.
What I'm thinking of doing is to use a document library component for users to upload and manage images. Then use Content Presenter to display the images.
Problems:
- Content Presenter doesn't do folders well.
- default templates don't show images
- icon view only shows an icon representing the type of content
Another option is to use the wiki as at http://wiki.oracle.com/photos/albums . Don't know if that can be done yet but cuold be easier for users.

Corruct VMWare for WebLogic Platform 8.1 SP4 for Red Hat Linux

Hi,
I have downloaded the image *.zip file following instructions in http://dev2dev.bea.com/wlplatform/vmware/index.html
(I have try all the download locations Asia, Europe and Noth America) BUT when I try to unziped it, one of the files is corrupt?
Does any one know how do I contact BEA support to inform them and where can I download an error free *.zip image?
Cheers,
Carlos
Message was edited by:
carestra

Hi,
I've got the same problem. dbassist and svrmgrl give me the same errors.
I'm using Oracle 8.1.6.1.0 on Mandrake 7.1. With the 2.2.15-4mdksecure kernel.
SVRMGR> CONNECT INTERNAL
Connected
SVRMGR> STARTUP NOMOUNT
ORA-00445: background process "PMON" did not start after 120 seconds
SVRMGR> (SQL stuff...)
ORA-03114: not connected to ORACLE
Any ideas?
This is driving me nuts!!!
Thx
Johan
null

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

All,
sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
Thanks,
-john

Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
Any thoughts? I'm completely stuck!
<Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>

Faces Servlet no getting called when accessing JSF portlet

Hi,
I have a JSF web application and I am exposing the functionality of this JSF web application using native Weblogic Portal JSF portlets. I have configured this JSF web application as a simple producer and I am consuming these portlets in my portal using WSRP.
I have written a custom FacesServlet and configured it in the web.xml of the producer web application. When I access the pages in the producer web app like a normal web app, I see that my faces servlet is being called but when I consume these pages via the JSF portlet and view the portlets in the portal then the Faces servlet is not being called.
Is this normal behavior or is WSRP causing this problem or am I missing something. Your help is greatly appreciated.
Regards,
Hitesh

Hi Hitesh,
What I was asking you to give a try was, configure the standard faces servlet for example if you are using JSF RI
the configuration will look like
    <servlet>
        <servlet-name>FacesServlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>100</load-on-startup>
    </servlet>I am not very sure whether this can solve the problem.
Thanks
Sreeram
Edited by sreeram.jonnalagadda at 06/10/2008 4:46 AM

Weblogic platform 8.1.4

Where can I find installation for weblogic platform 8.1.4?

All the easy to get WebLogic server version are listed here: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
When you need other versions, you have to contact support and see if you can get it through those channels.

Developing JSF Portlets with WebLogic Portal (Oracle White paper May 2009)

I have created a simple JSF Portlet following the steps delineated in paragraph 3.1.1 Creating a JSF Enabled WLP Web Project of the white paper mentioned above. I used Workshop for Weblogic 10gR3. When I tried to deploy that very simple portlet and portal I got this error message :
"!MESSAGE Unable to register J2EE shared library C:\bea\wlportal_10.3\samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war".
Clearly the folder and file "samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war" are not under my "C:\bea\wlportal_10.3". My question is where do I download it? Where does it come from?
Thanks in advance.

Maybe you did not include the samples when you installed Oracle WebLogic Portal? Now that this is an Oracle product, samples are not installed or configured by default. This is a change in policy from when WebLogic Portal was a BEA thing, so it takes some getting used to and there are probably plenty of places where documentation and papers could be enhanced to emphasize this.
In addition, it looks like there might be an error in the white paper with respect to configuring your web app to include samples. I don't see any mention of taking an extra step to include the sample facets in your portal app. This oversight may have been caused by the author working with a pre-release of Oracle WebLogic Portal that had not yet been "Oracle-ized" enough to get the default samples out of there. In the old days, I think the samples were automatically included in your portal web app.
To get the samples in a new portal web app while you are creating it with the IDE you can click the "Modify..." button on the first dialog. It is next to the "Configuration" text area. This pops up a dialog that lets you select the "Weblogic Portal Samples" facet for your web app.
To get the samples in an existing portal web app after it has been created, right click the app in the IDE, click "Properties...", click "Project Facets", and select the "Weblogic Portal Samples".
Sorry, I'm not sure what the remedy is for getting samples into an installed product that was not installed with the samples. Unfortunately, I think that is the problem that you need solved. Sorry about that. Hopefully you are working in a test or dev environment that makes it easy to blow away old installations and start over? If not, then maybe install it with samples someplace else and copy the samples/... dir over to your other install?

Example JSF Portlet Project for WebLogic Portal 10.3.2

Hi,
does anyone have an example JSF Portlet Project for WebLogic 10.3.2 using the default JSF implementation 1.2.
I tried to implement the example of the document "Developing JSF Portlets with WebLogic" but I always get a ClassCastException.
java.lang.ClassCastException: com.bea.portlet.container.RenderRequestImpl
Thx in advance
Edmund

My approach was to programmatically redirect to the page again with _nfpb=false. I do this in the handlePostbackData() method in the portlet's backing file.
redirectUrl = redirectUrl.replaceAll("_nfpb=true", "_nfpb=false");
PortletBackingContext.getPortletBackingContext(request).sendRedirect(redirectUrl);
Matthias Rohe
[email protected]
Edited by: user7964913 on 29.09.2010 04:06

Is the Bea weblogic workshop IDE develop use the Java?

is the Bea weblogic workshop IDE develop use the Java?
beautiful UI.I like it.
but i think it develop use C#!

Dear carls:
Thank you very much.I'm look forward to the day it is released!
"Carl Sjogreen" <[email protected]> wrote:
Thanks for the compliment!
At the current time, BEA is not planning to release the workshop look and
feel to third parties, or make it available via open source. However, its
all standard swing code -- just a lot of custom drawn controls!
In a later release we may open up these libraries to partners who want to
work closely with the Workshop environment.
-Carl Sjogreen, Product Manager
"andiyang" <[email protected]> wrote in message
news:3cff0bc5$[email protected]..
Dear Anurag Pareek:
Thank u very much,I want to know to do it?is it Open and standard ?where has develop
resource about it?
thank u very much!
andiyang
"Anurag Pareek" <[email protected]> wrote:
Hi,
As beautiful as it looks, it has been developed entirely using Java Swing
components:-)
Regards,
Anurag
Workshop Support
"andiyang" <[email protected]> wrote in message
news:3cfd727d$[email protected]..
is the Bea weblogic workshop IDE develop use the Java?
beautiful UI.I like it.
but i think it develop use C#!

Workshop IDE for WebLogic Platform - JSF Portlet Development

Similar Messages

Maybe you are looking for