Spring Console extension for weblogic 10.0

Hi,
I am trying to configure spring console extension for weblogic version 10.0 . As mentioned in some documents, I am unable to find the required jars in the server lib folder, and googled to download it, but yet no success. If any one is aware of where can I get the required jars and steps to configure spring console for version10.0, let me know.
Thanks

Hi
To my surprise, When i asked my Server team to get me weblogic support, I got a response from them stating that weblogic will not support spring framework 2.5 and they sent me the link
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs100/100_over/overview.html#1131715
And asked me to downgrade my project to the supported version.
But I think it is not correct, I don't have information if really my local team contacted weblogic support, or they are just sending me this link based on the document they have.
But I don't understand why it is so hard to get this thing working. Is there many people facing this issue ?
Or every one using apache Axis2 or CFX for web service and spring webservice is not advised ?
Some time I don't know whom should be blamed.
Thanks

Similar Messages

Building an Admin Console Extension for a Custom Security Provider

I am looking for an example or a description how to build an Administration Console extension for a custom Authentication Provider.
Especially the creation page for the provider is interesting because I am not able to create and register the required Authentication Provider MBean.
The call “mbeanHome.getMBeanServer().createMBean(className,objectname)” always throws the following Exception “javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository”
Even if I try the class “weblogic.security.providers.authentication.IPlanetAuthenticator”, that is part of the bea distribution, the same exception is thrown.
It seams that the Problem has something to do with class loaders?
When I use the standard admin console pages to create and configure my provider everything works fine.
The only example “kennedy0208.zip” I found in the net does not deal with the creation of the MBean.
It only customizes the edit pages for the provider and at that point the MBean has already been created by the standard admin pages.
Maybe the author discovered the same Problems and gave up!?
What makes me wondering is that I have to put my MBean Classes to my console extension war file to be able to import the packages in my jsp.
If I not put the classes to my war the compiler throws an exception because he can’t resolve the package.
Because I moved my provider implementation jar to the directory “WLHOME\server\lib\mbeantypes” as described in the bea documentation it should run without putting the classes to the war!?!
I am very surprised that the bea documentation does not provide any example about this topic.

Found it. Cut and paste error. I still had one of their example class
names in my code. Oops.

ActionLookupFailedException in Console Extension with Weblogic 12c

The struts config example in the console extension docs at http://docs.oracle.com/cd/E24329_01/web.1211/e24966/simpleext.htm#CNSLX197, does not include the vital content :-
<controller processorClass="com.bea.console.internal.ConsolePageFlowRequestProcessor">
<set-property property="nocache" value="true" />
<set-property property="contentType" value="text/html;charset=UTF-8" />
</controller>
Without that, you can't forward to your jsp, and you get this stack trace :-
com.bea.portlet.adapter.scopedcontent.ActionLookupFailedException
     at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.handleNullActionResult(StrutsStubImpl.java:143)
     at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:766)
     at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:265)
     at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.render(StrutsStubImpl.java:103)
     at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:292)
     at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:428)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:727)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
I hope that helps someone, or maybe even gets the docs updated!

;-)

WL70 Console extension questions

Hi,
A couple of questions about Weblogic console extension.
First, is there any "standard" way of putting that nice banner on top of my JSP
pages? I've created one using classes "banner", "title", "bannerstatus" from wl:stylesheet,
but I'm worried that links that I put in it, like
will not work in the next version of weblogic.
Second, is it possible to bring up console JSP showing the particular wl:tab rather
than the first one?
Thanks,
Mikhail.

Donwload SQLMonitor from
http://www.appfluent.com/products/sqlmonitor/
It is has console extension for both 7 and 6 and has implemented the
banner thru one servlet checking the weblogic version.
Pam S.
"Wayne W. Scott" <[email protected]> wrote in message news:<[email protected]>...
Mikhail Bogomolov wrote:
"Mikhail Bogomolov" <[email protected]> wrote:
Hi,
A couple of questions about Weblogic console extension.
First, is there any "standard" way of putting that nice banner on top
of my JSP
pages? I've created one using classes "banner", "title", "bannerstatus"
from wl:stylesheet,
but I'm worried that links that I put in it, like
> >>will not work in the next version of weblogic.
Second, is it possible to bring up console JSP showing the particular
wl:tab rather
than the first one?
Thanks,
Mikhail.
Ok, just found the answer for the second question - add a parameter ?tab=TabName
to URL, but the first question still stands.
see if the example under dev2dev helps ->
http://dev2dev.bea.com/code/codedirect.jsp?highlight=codedirect
This sample demonstrates how to extend the WebLogic Server 7.0 Administration Console.
View the readme.html file for instructions on how to deploy the sample. This is Alpha code.
ConsoleExtensionExample.zip (40 kb)
Wayne

Breadcrumb navigation in console extension not working

Hi everyone,
I'm trying to get the breadcrumb navigation working in my console-extension for wls 9.2.
Currently it is displayed like this:
Home > com.bea.console.handles.JMXHandle%28%22No+context+provided+for+Loggers%22%29 ("Loggers" is the definitonLabel of my netuix:page element).
As described on [url http://e-docs.bea.com/wls/docs92/console_ext/addcontrols.html#wp1078025]page 6-15 of the "Extending the Admin Console" guide I added the <netuix:meta name="breadcrumb-context" content="handle" /> element exactly as in [url http://e-docs.bea.com/wls/docs92/console_ext/addcontrols.html#wp1078078]listing 6-7.
Do you have any idea what goes wrong here or any pointers what I might be missing?
Any help is greatly appreciated.
Btw. Is there a more appropriate place to post this question?

Chariot, unless someone decompiles that swf we cannot see
your code or how you constructed it. I did do that and took a look
but not everyone can do that. In the future, you can either post
the FLA or use the "Attach Code" button to show what you've done.
1.) first thing I noticed was that your HIT area on your
buttons is the text itself. If you make a rectangle on the HIT
frame only that is slightly larger than your text, you won't have
such jumpy behavior when mousing over or trying to find the "sweet
spot" that will actually click. You've made invisible buttons, I
see. It's the same concept. That way, you can get rid of the
invisible buttons altogether.
2.) Not sure why you have several layers on your buttons.
Looks like you have a layer per letter. They can all be on the same
layer. :)
3.) Try to put your button code on the main timeline instead
of on the buttons themselves. If you're curious why, read
this
article.
4.) You only need one arrow button... not a different one for
each section. Again, place the code on the main timeline and
specify at each keyframe what you want "leftArrow_btn" or
"rightArrow_btn" to do. I just made up those instance names but
they'll do whatever you tell them to do even if it's different than
what you told them to do before.
Other than that, I don't see what you are referring to.
There's a lot of cleaning up to be done. That will probably fix
some errors. I've posted an example of how it might work for you
here.

Trouble with console-extension using struts portlet

hello everyone,
I'm developing a console-extension for wls9.2 but couldn't get is to work despite all the documentation available. The console-ext is a struts portlet which gathers data from custom mbeans via jmx and renders the result with a jsp. What already works is fetching the data from the MBeans in the struts action. What does not work is the display of the results in the admin console. So I removed all the stuff from the jsp to just display "Hello World" which should be displayed on the desktop in the admin console, but even this didn't work (it's just a blank spot). Having a look at the log file I get the following:
e.netui.pageflow.internal.AdapterManager ERROR ServletContainerAdapter manager not initialized correctly.
e.netui.pageflow.internal.AdapterManager INFO No ServletContainerAdapter specified or discovered; using class org.apache.beehive.netui.pageflow.DefaultServletContainerAdapter
tui.util.config.parser.NetUIConfigParser INFO NetUIConfigParser -- load config: /WEB-INF/beehive-netui-config.xml
e.netui.pageflow.internal.AdapterManager INFO No ServletContainerAdapter specified or discovered; using class org.apache.beehive.netui.pageflow.DefaultServletContainerAdapter
netui.pageflow.AutoRegisterActionServlet INFO Dynamically registering module /loggingController, config XML /WEB-INF/struts-auto-config-loggingController.xml
netui.pageflow.AutoRegisterActionServlet INFO Dynamically registering module /loggingController, config XML /WEB-INF/struts-auto-config-loggingController.xml
(...other debug output from my struts action...)
.wls.web.actions.LoggingControllerAction DEBUG Going to /ext_jsp/helloWorld.jsp using module null
flow.scoping.internal.ScopedResponseImpl INFO ScopedResponse error 404:
.netui.pageflow.PageFlowRequestProcessor WARN Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass". Page Flow actions in this module may not be handled correctly.
.netui.pageflow.PageFlowRequestProcessor INFO Attempting to instantiate SharedFlowControllers for request /console/ChangeManagerAction.do
ive.netui.pageflow.FlowControllerFactory INFO No Global.app was found in /console
Despite the errors it seems to find my struts config (struts-auto-config-loggingController.xm) and execute the action, but then it seems to have trouble findingd/displaying the jsp (helloWorld.jsp). I tried to set various controller-elements in the struts config, like this ([url http://edocs.bea.com/wlp/docs92/portals/integrate.html#wp1005659]source):
<controller inputForward="true" processorClass="com.bea.struts.adapter.action.AdapterRequestProcessor" />
but this didn't work either (and results in other errors). The log from above was created with a config without any controller element (since this is never mentioned in the eDocs for console extensions).
Despite spending several hours trying to figure out what goes wrong here I wasn't able to get one step closer to a solution. Does anyone have a clue what I did wrong (please ask if you need further information)? Thanks a lot!
Btw. Sorry if this is the wrong forum, I could't find another one which matches better. Feel free to move the topic to a more appropriate place. thx.
====================================
Struts config:
<struts-config>
     <form-beans>
          <form-bean name="loggingForm" type="...web.forms.LoggingControllerForm" />
     </form-beans>
     <action-mappings>
          <action path="/LoggingControllerAction"
               type="...web.actions.LoggingControllerAction"
               name="loggingForm"
               scope="request"
               validate="false"
               input="/ext_jsp/helloWorld.jsp">
               <forward name="success" contextRelative="true"
                    path="/ext_jsp/helloWorld.jsp" />
          </action>
     </action-mappings>
</struts-config>

The problem could be solved by adding the "handle" property (of type com.bea.console.handles.Handle) to the form bean.
This is stated on page 7-4 in the "Extending the admin console" guide or [url http://e-docs.bea.com/wls/docs92/console_ext/simpleext.html#wp1083856]here
In addition the following controller element must be used in the struts config: <controller inputForward="true" processorClass="com.bea.struts.adapter.action.AdapterRequestProcessor" />
This is not mentioned anywhere and should definitely be added to the guide.
Hope this helps someone encountering the same problem.

Capturing weblogic username and password for use in my console extension

Hi,
I have developed a console extension as a war file and it needs to capture the Weblogic username and password so internally it can use the class MBeanServerConnection that needs these during connection. I have therefore created the standard <login-config> <auth-method>FORM</auth-method> ... stuff in the web.xml to output a logon.jsp when my war is accessed in the hope of capturing username and password. My intention is that these would appear in addition to the standard logon that appears when the Weblogic console is 1st accessed.
However, my console extension logon.jsp does not appear and I think it’s because there is only one logon needed and this is when the main Weblogic console is accessed because my console extension is subordinate to the main Weblogic console.
Therefore, how can I get my console extension logon.jsp to appear so I can capture the Weblogic username and password?
Thanks,
Dave.

One approach that might work is to write a look and feel console extension that modifies the console's login jsp (vs trying to have a second login jsp).
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13745/rebrand.htm#i1070459 describes how to write look and feel extensions.
Basically, you instantiate the look and feel extension template, hand-edit login/LoginForm.jsp, then build and deploy the extension.
One tricky part is figuring out how to pre-compile the jsps. Here's part of a build script I've used for look and feel extensions. Let me know if you need a sample look and feel extension.
<project name="sample-look-and-feel" default="build">
<dirname property="this.dir" file="${ant.file.sample-look-and-feel}" />
<property environment="env" />
<property name="src.dir" value="${this.dir}/src" />
<property name="build.dir" value="${this.dir}/build" />
<property name="webapp.dir" value="${build.dir}/webapp" />
<property name="jspc.dir" value="${build.dir}/jspc" />
<property name="samplename" value="sample-look-and-feel" />
<property name="wlhome.dir" value="${env.WL_HOME}" />
<property name="consoleapp.dir" value="${wlhome.dir}/server/lib/consoleapp" />
<property name="deployment" value="${build.dir}/${samplename}.war" />
<target name="build">

<copy todir="${jspc.dir}">
<fileset dir="${consoleapp.dir}/webapp">
<include name="**/struts.jar" />
<include name="**/standard.jar" />
<include name="**/beehive-netui-tags.jar" />
<include name="**/skeleton_taglib.jar" />
<include name="**/render_taglib.jar" />
<include name="**/l10n_taglib.jar" />
<include name="**/*.tld" />
<include name="**/web.xml" />
</fileset>
<fileset dir="${webapp.dir}">
<include name="**/*.jsp" />
</fileset>
</copy>

<java classname="weblogic.servlet.jsp.jspc20" fork="true" failonerror="false">
<arg line="-noexit" />
<arg line="-d ${webapp.dir}/WEB-INF/classes" />
<arg line="-webapp ${jspc.dir}" />

<classpath>
<pathelement path="${wlhome.dir}/server/lib/wlw-langx.jar" />
<fileset dir="${consoleapp.dir}/APP-INF/lib">
<include name="*.jar" />
</fileset>
<fileset dir="${consoleapp.dir}/webapp/WEB-INF/lib">
<include name="*.jar" />
</fileset>
<pathelement path="${java.class.path}" />
</classpath>
</java>

<delete dir="${jspc.dir}" />

<jar destfile="${deployment}" basedir="${webapp.dir}" />

<delete dir="${webapp.dir}" />
</target>
</project>

Using Weblogic Console Extension tag library...

Now i am working with weblogic 8.1
I am using Weblogic Console Extension Example...downloaded from dev2dev.bea.com...
at that example console Jsp program is as below for
the development of node...
<br>
<b><wl:node
label='<%="My Console Extension"%>'
icon='/images/folder.gif'
expanded='true'>
</wl:node></b>
<br><br>
<i><b>But i want two folder icons...for open folder...and closed folder...</b></i>
<br>
i have gifs...but how i modify this
jsp...or tag library...any one can help me...
<br>
raju

"Otherwise let me know tools that can tell me threads, memory, cpu, etc and provide notification, etc." -- Hi, I'm familiar with a third-party tool that is suitable for larger deployments, it collects the data you mention for Weblogic instances and also does performance monitoring at the cluster level. Here is a description of their WebLogic integration pack -- http://www.evidentsoftware.com/products/clearstone-for-weblogic/. Hope this helps.

Perfomance Monitor Console Extension (PMCE) on WebLogic 8.1 SP3

Is it possible to run PMCE on WebLogic 8.1 SP3?
I downloaded PMCE from bea and used the installer to install the administrative console extension and an agent on my own machine. I 'm also running a WebLogic server instance on this machine.
When I go to the server's administrative console it has a new section for the performance monitor, but clicking on anything in that section doesn't work.
Any suggestions would be appreciated.
In the server's log there are NullPointerExceptions and it says the servlet failed. The text of the error is:
####<DATE> <Error> <HTTP> <MACHINENAME> <MACHINENAME-WLS> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101020> <[ServletContext(id=19875128,name=PerformanceMonitor,context-path=/PerformanceMonitor)] Servlet failed with Exception
java.lang.NullPointerException
at weblogic.management.console.tags.TextTag.getText(TextTag.java:46)
at weblogic.management.console.tags.TextTag.doStartTag(TextTag.java:56)
at jsp_servlet.__prftop._jspService(__prftop.java:339)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6452)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>

For anyone that is searching for the same problem. Bea customer support has confirmed that this is a bug in SP3. SP4 fixes the problem.
Message was edited by lngtones at Jan 31, 2005 9:36 AM

WebLogic Performance Monitor Console Extension (WL PMCE)

Hi,
Where do I download the software for WebLogic Performance Monitor Console Extension (WL PMCE)?
I saw the article at http://www.theserverside.com/news/thread.tss?thread_id=21804 and the PDF looks interesting. But I'm not able to find the place to download the software?
I'm using WebLogic Server 8.1 SP5 . Is it comes with in-built? If yes, please let me know how to enable it.
Otherwise let me know tools that can tell me threads, memory, cpu, etc and provide notification, etc.
Advanced thanks.

"Otherwise let me know tools that can tell me threads, memory, cpu, etc and provide notification, etc." -- Hi, I'm familiar with a third-party tool that is suitable for larger deployments, it collects the data you mention for Weblogic instances and also does performance monitoring at the cluster level. Here is a description of their WebLogic integration pack -- http://www.evidentsoftware.com/products/clearstone-for-weblogic/. Hope this helps.

How to debug weblogic console extension application ?

Hi,
I am developing a weblogic console extension application with web logic portal framework, I got some error, but no idea how to debug,
I can see some error on buildApplication.jsp file, but can't find __buildapplication.java file which is compiled from buildApplication.jsp,
so I can't know the error is in which line in buildApplication.jsp file. and I dont' even know which tag is tag1 tag2 tag3 in that jsp file.
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag3(__buildapplication.java:292)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag2(__buildapplication.java:260)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag1(__buildapplication.java:211)
at jsp_servlet._ext_jsp.__buildapplication._jspService(__buildapplication.java:138)
Code of buildApplication.jsp:
     <fmt:setBundle basename="detwds" var="current_bundle" scope="page"/>
     <beehive-template:template templatePage="/layouts/configBaseLayoutNoTransact.jsp">
          <beehive-template:section name="configAreaIntroduction">
          <fmt:message key="buildApplication.jsp.page.introduction" bundle="detwds"/>
          </beehive-template:section>
          <beehive-template:section name="form">
          <html:xhtml/>
          <wl-extension:template name="/templates/jmxform.xml">
          <wl-extension:form name="ExtensionForm" type="com.det.consoleext.form.ExtensionForm" action="/BuildApplication" bundle="detwds">
          <wl-extension:select
          property="contents"                                                   labelId="buildApplication.jsp.page.repositoryList.label"                                                   inlineHelpId="buildApplication.jsp.page.repositoryList.inlinehelp"
          singlechange="false">
               <wl-extension:optionsCollection                                                                  property="repositoryName"
                    label="label"
                    value="value"/>
          </wl-extension:select>
          </wl-extension:form>
     </wl-extension:template>
     </beehive-template:section>
     </beehive-template:template>
Error message:
2755> <BEA-423405> <An exception [java.lang.String] was thrown while rendering the content at [ext_jsp/buildApplication.jsp].
java.lang.ClassCastException: java.lang.String
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag3(__buildapplication.java:292)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag2(__buildapplication.java:260)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag1(__buildapplication.java:211)
at jsp_servlet._ext_jsp.__buildapplication._jspService(__buildapplication.java:138)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551)
at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__flowlayout._jspService(__flowlayout.java:281)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:188)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:142)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:377)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:253)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:206)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:191)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

It is quite easy to rewrite the plugin to work with 8.1
We have done so - please contact me if you want the plugin.
Sincerely,
Paul Nyheim
"HOs" <[email protected]> wrote in message
news:3f72ce93$[email protected]..
>
Hi,
how can I debug my weblogic 8.1 application ?
I`m using eclipse, but the plugin I´ve got, is only for versions 6.x and7.0 .
So I tried remote debugging but eclipse could not connect to the VM, I donot
know why.
Any ideas ??
Thanks
Holger

Applet loading Failed .... for diagnostics-console-extension.jar

Hi everybody,
i downloaded diagnostics-console-extension.jar from bea site. i copied this file to D:\bea9.0\user_projects\domains\mydomain\console-ext. i started weblogic server . in administration console when i clicking WLDF console extension tab it gives the Applet loading failed....and also in server console it gives an exaception as follows ""
java.lang.ClassNotFoundException: jsp_servlet._com._bea._diagnostics._dashboard.
__chartpanelapplet_class.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:512)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:224)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(Servlet
StubImpl.java:383)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:298)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:165)
Truncated. see log file for complete stacktrace
>
in Java console output Exception
Java Plug-in 1.5.0_06
Using JRE version 1.5.0_06 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\mselvan
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
java.lang.ClassFormatError: Truncated class file
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(Unknown Source)
     at java.security.SecureClassLoader.defineClass(Unknown Source)
     at sun.applet.AppletClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadCode(Unknown Source)
     at sun.applet.AppletPanel.createApplet(Unknown Source)
     at sun.plugin.AppletViewer.createApplet(Unknown Source)
     at sun.applet.AppletPanel.runLoader(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Exception in thread "Thread-5" java.lang.NullPointerException
     at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
     at sun.plugin.AppletViewer.showAppletException(Unknown Source)
     at sun.applet.AppletPanel.runLoader(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
     at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
     at sun.plugin.AppletViewer.showAppletStatus(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Exception in thread "thread applet-com.bea.diagnostics.dashboard.ChartPanelApplet.class" java.lang.NullPointerException
     at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
     at sun.plugin.AppletViewer.showAppletException(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
so kindly any one help for the same.please help me
Thanks & regards
Selvan.M

Several issues with the diagnostic console extension have been fixed in WLS 9.2. Can you try the extension from 9.2? WLS 9.2 is now ready for download from the BEA site.
Thanks

I have been getting this (or earlier version) messages every time Firefox updates for at least a year "The Java Console extension is no longer supported and will be automatically removed the next time you restart Firefox. " What should I do?

For a long time, each time Firefox updates, it invites me to install theJava Console Update. then I get a message that Java Console not supported.

You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
Disable the Java Quick Starter extension (if you have it): Tools -> Add-ons -> Extensions<br />
Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
See http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0

Read-only user for Weblogic 6.1 sp2 console

Is there a way to restrict a user to read-only priv. on the weblogic
console? Either by using acl's or other means.
Thanks in advance,
Brown

"Seb" <[email protected]> wrote in message news:3f33c3e2$[email protected]..
>
Hello,
I'd like to create a read-only user for a customer that gives him acces tothe
Console only for reading all the configuration. I don't him to modifyanything
Is there a simple way to do this ?A previous post mentioned that this is not possible in 6.1.
Brown,
This functionality is not available in 6.1. The newest version of wls
8.1 has this feature depending on the role that the user is in.
~satya

Workshop for weblogic and spring 2.0.6 not working on weblogic 92

Hi,
I try to use workshop for weblogic 10.1 to create a web project using spring mvc framework and deploy it to a weblogic 9.2 server, and it gives me the error.
Here's what I have done:
Create a 9.2 server.
Create a web project with spring facet, I downloaded spring 2.0.6.
I created a test jsp page along with applicationContext.xml and springServlet.xml spring support.
When I start the server and publish the ear to the server,
I got the following error:
Aug 28, 2007 9:18:03 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Aug 28, 2007 9:18:27 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "SpringContextServlet" failed to preload on startup in Web application: "springmvcWar".
java.lang.NoClassDefFoundError: weblogic/i18n/logging/MessageLoggerRegistryListener
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338)
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:291)
     Truncated. see log file for complete stacktrace
I couldn't find the class weblogic/i18n/logging/MessageLoggerRegistryListener anywhere.
Does anybody have seen this error before.
Thanks
maildt

Hi,
I tried the scenario against 9.2mp1 server and 9.2mp2 server and the publish worked fine.
The only difference is the jsp file you created
Can you remove your jsp file and see if the publish still fails?
Which version of 9.2 server are you using? Also, what all facets are you using other than spring?
Can you also try something and see if it helps?
1. Open a new workspace
2. In Window -> Preferences -> WebLogic -> J2EE Libraries, removed the logging bridge libraries (the 10.0 version) and re-added these libraries from a 9.2 installation.
Basically they are
wls-commonslogging-bridge 1.0/1.0
wls-commonslogging-bridge-war 1.0/1.0
wls-commonslogging-bridge 1.0/1.1
wls-commonslogging-bridge-war 1.0/1.1
and add 2 jars from 9.2_BEA_HOME/weblogic92\common\deployable-libraries
3. Create web project and follow the other steps
Thanks
Vimala

Spring Console extension for weblogic 10.0

Similar Messages

Maybe you are looking for