How to use weblogic.jspc -J option

Can anyone give me an example on how to use the
          weblogic.jspc -J option? Specifically, I want
          my "-compilerclass" to use a system property
          which will be specified on the command line.
          For example:
          java ... weblogic.jspc ... -compilerclass MyCompilerClass -Dmy.text="hello world"
          or something to that effect.
          Gary F.
          Fast Track Systems, Inc.

-J only seems to work for -X-style arguments to the VM, i.e. you can say
 "-Jms64m".
 -compiler has been broken for a while (see my other post in this group on
 that).
 anders
 "Gary Fong" <[email protected]> wrote in message
 news:[email protected]..
 > Can anyone give me an example on how to use the
 > weblogic.jspc -J option? Specifically, I want
 > my "-compilerclass" to use a system property
 > which will be specified on the command line.
 >
 > For example:
 >
 > java ... weblogic.jspc ... -compilerclass
 MyCompilerClass -Dmy.text="hello world"
 >
 > or something to that effect.
 > --
 > Gary F.
 > Fast Track Systems, Inc.

Similar Messages

How to use weblogic.Deployer

I can deploy this adf application to weblogic server in jdeveloper 11.1.1.3.
How to use weblogic.Deployer in weblogic 10.3.3? I get errors as follow:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>d:
D:\>cd D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin
D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin>setDomainEnv.cmd
D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server>java weblogic.Deployer
-adminurl http://localhost:7001 -user weblogic -password welcome1 -deploy -upload E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
weblogic.Deployer invoked with options: -adminurl http://localhost:7001 -user weblogic -deploy -upload E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:70)
at weblogic.Deployer.main(Deployer.java:54)
Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:138
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:116)
... 2 more
Caused by: javax.naming.CommunicationException [Root exception is java.net.Conne
ctException: http://localhost:7001: Destination unreachable; nested exception is
java.net.ProtocolException: Tunneling result unspecified - is the HTTP s
erver at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
... 2 more
Caused by: java.net.ConnectException: http://localhost:7001: Destination unreach
able; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
... 19 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception
is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available rou
ter to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:150)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:138)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:116)
... 2 more
Unable to connect to 'http://localhost:7001': Destination unreachable; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available rou
ter to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server>

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Problem using weblogic.jspc with wls6.1

 I've got this error using weblogic.jspc on jsp that works fine with the compiler
 of 5.1, is this a bug?
 java.lang.NullPointerException
 at weblogic.management.Admin.getServer(Admin.java:1252)
 at weblogic.servlet.internal.dd.ServletEntityResolver.initServerMBean(ServletEntityResolver.java:69)
 at weblogic.servlet.internal.dd.ServletEntityResolver.resolveEntity(ServletEntityResolver.java:94)
 at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:749)
 at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:566)
 at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1139)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2215)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
 at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:175)
 at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:311)
 at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:327)
 at weblogic.servlet.internal.dd.DescriptorLoader.initialize(DescriptorLoader.java:242)
 at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:176)
 at weblogic.servlet.internal.dd.DescriptorLoader.loadDescriptor(DescriptorLoader.java:396)
 at weblogic.jspc.runBodyInternal(Compiled Code)
 at weblogic.jspc.runBody(jspc.java:169)
 at weblogic.utils.compiler.Tool.run(Tool.java:79)
 at weblogic.jspc.main(Compiled Code)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
 [java.lang.NullPointerException]
 at java.lang.Throwable.fillInStackTrace(Native Method)
 at java.lang.Throwable.fillInStackTrace(Compiled Code)
 at java.lang.Throwable.<init>(Compiled Code)
 at java.lang.Error.<init>(Error.java:50)
 at weblogic.utils.NestedError.<init>(NestedError.java:24)


Please post your full description. I can't see what you're replying to (must
 be too old).
 Alex
 "Gregory Chazalon" <[email protected]> wrote in message
 news:3c7383a8$[email protected]..
 > I've got te same problem (NullPointerException at the same line code in
 the same class). The most disturbing is that the weblogic.jspc works fine
 with wl6.1 SP2 but fails with wl6.1 SP1.
 >
 > Do you have a solution ? Can I download a CRXXXX.jar that fixes it ?
 >
 > I will appreciate any help.
 >

How to use offset for select-option parameter ?

Hi experts
could anybody please let me know how to use offset for select-option parameter. i can able to use offset for table fields, variabiles and all , but don't know how to use for parameters.
following is my code
SELECT-OPTIONS: s_prctr FOR vbsegs-prctr OBLIGATORY.
here "prctr" length is 10.
i'm using two tables 1. vbsegd-bupla
                                2. vbsegs-prctr
here prctr+6(4) = bupla.
"Bupla" length is 4
SELECT belnr gjahr bukrs bupla sgtxt buzei FROM vbsegd INTO CORRESPONDING FIELDS OF TABLE it_vbsegd FOR ALL ENTRIES IN it_vbkpf
                                                             WHERE belnr = it_vbkpf-belnr
                                                               AND gjahr = it_vbkpf-gjahr
                                                               AND bukrs = it_vbkpf-bukrs
                                                               AND bupla IN s_prctr.
the above statement is not working as prctr and bupla lenths are different. here i want to use offset.
SELECT belnr gjahr bukrs prctr sgtxt buzei FROM vbsegs INTO CORRESPONDING FIELDS OF TABLE it_vbsegs FOR ALL ENTRIES IN it_vbkpf
                                                            WHERE belnr = it_vbkpf-belnr
                                                              AND gjahr = it_vbkpf-gjahr
                                                              AND bukrs = it_vbkpf-bukrs
                                                              AND prctr IN s_prctr.
this is working as prctr and s_prctr lengths are equal.
could anybody please help me out in this.
Thanks in advance.
regards
satish

Below code will work for you.
SELECT-OPTIONS: s_prctr FOR vbsegs-prctr OBLIGATORY.
RANGES: s_bupla FOR vbsegd-bupla.
s_bupla[] = s_prctr[].
DELETE ADJACENT DUPLICATES FROM s_bupla.
SELECT belnr gjahr bukrs bupla sgtxt buzei FROM vbsegd INTO CORRESPONDING FIELDS OF TABLE it_vbsegd FOR ALL ENTRIES IN it_vbkpf
                                                              WHERE belnr = it_vbkpf-belnr
                                                                AND gjahr = it_vbkpf-gjahr
                                                                AND bukrs = it_vbkpf-bukrs
                                                                AND bupla IN s_bupla.

Appending a _ in front of the jsp class name when using weblogic.jspc

http://e-docs.bea.com/wls/docs60/jsp/reference.html
 java weblogic.jspc -d /weblogic/classes -keepgenerated primero.jsp
 "rb" <[email protected]> wrote in message
 news:[email protected]...
 >
 > hi,
 >
 > i do
 >
 > java weblogic.jspc -d /weblogic/classes primero.jsp
 >
 > and it only is generated a _primero.class and do not appear
 > the .java ?
 >
 > what i do bad ?
 >
 > thanks for advance
 >
 >
 > Rodrigo Fonseca da Fonseca <[email protected]> wrote:
 > >Hi,
 > >
 > >I'm using weblogic.jspc to compile some jsp fiels. The compilation is
 > >complete and successfully, but the names of generated files .java and
 > >..class are strange.
 >
 >
 >
 > >
 > >For example, compiling a file named change_login_data.jsp, the resulting
 > >files are change95_login_95_data.java and
 > >change95_login_95_data.class. Compiling a file named buy.jsp, the
 > >resulting files are buy.java and buy.class (fine situation). Why???
 > >
 > >I'm using:
 > >
 > >java weblogic.jspc -d c:\jsp_result -classpath
 > >
 >
 >c:\weblogic\myserver\serverclasses;c:\weblogic\lib\weblogicaux.jar;c:\weblo
 gic\classes
 > >-compiler jikes.exe -J-verbose -keepgenerated -verbose
 > >change_login_data.jsp
 > >
 > >
 > >thanks
 > >Rodrigo
 > >
 > >
 > >
 > >Mark Spotswood wrote:
 > >>
 > >> The namespace for java class files is more restrictive
 > >> than for JSP files. We prepend these underscores so
 > >> that if, for example, someone names their JSP "1.jsp",
 > >> we get a class file with a legal name. We did consider
 > >> not doing this for files which started with characters
 > >> we kenw to be valid (in fact we may have put it in a
 > >> service pack), but later found that this was not sufficient
 > >> because its possible to name a jsp file something that
 > >> clashes with java keywords ("class.jsp" for example).
 > >> Rather than making the scheme even more complex,
 > >> we decided to go back to the original sheme of always
 > >> prepending the underscore.
 > >> --
 > >> mark
 > >>
 > >> Mika Moilanen wrote:
 > >>
 > >> > >>>>> "Shankar" == Shankar Roy <[email protected]> writes:
 > >> >
 > >> > Shankar> Problem seems to go away with weblogic510sp4.jar in
 compilation
 > >classpath.
 > >> > Shankar> Shankar.
 > >> >
 > >> > Shankar> Shankar Roy wrote:
 > >> >
 > >> > >> Hi,
 > >> > >> Can anyone tell why when I invoke weblogic.jspc the class file
 that
 > >is
 > >> > >> generated has a _ in front of the class name
 > >> > >>
 > >> > >> java -classpath
 > >> > >>
 >
 >/space/shankar/weblogic/lib/weblogicaux.jar:/space/shankar/weblogic/classes
 /boot:/space/shankar/weblogic/classes:/space/shankar/dev/dev/lib/activation.
 jar:/space/shankar/dev/dev/lib/classes12.zip:/space/shankar/dev/dev/lib/mail
 .jar:/space/shankar/dev/dev/lib/oroinc.jar:/usr/java/lib/classes.zip
 > >> > >> weblogic.jspc -package com.careassured.jsp -commentary login.jsp
 > >> > >>
 > >> > >> produces a class file by the name _login.class
 > >> > >>
 > >> > >> Thanks for any help pointers.
 > >> > >> Shankar.
 > >> >
 > >> > Not with WLS5.1 and weblogic510sp6.jar, we still get '_' prefixed
 > >> > classes...
 > >> >
 > >> > Actually we're suffering quite a lot because of this bug in
 > >> > weblogic.jspc. Are there any plans for fix?
 > >> >
 > >> > --
 > >> > Best Regards,
 > >> > Mika
 > >> > ----------------------------------------------------------
 > >> > [email protected] phone: +358-0-511-23587
 > >> > Nokia Networks, PO box 320, FIN-00045 NOKIA GROUP, Finland
 > >> > ----------------------------------------------------------
 >

How to use weblogic on jdk 5?

Does anyone know, how to use weblogic and jdk 5?

Supported on version 9.0 Beta, only.
http://e-docs.bea.com/platform/suppconfigs/configs90/90_over/overview.html#1122259
Bill
"Fauzi Mubarok" <[email protected]> wrote in message
news:2966888.1105597574948.JavaMail.root@jserv5...
Does anyone know, how to use weblogic and jdk 5?

How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
Neeraj

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Using weblogic.jspc

We are trying to use weblogic.jspc for precompiling the jsps in our application. Following the ANT task for doing the same.
 <target name="runJspc" depends="runAssembler">
 <path id="jspc.path.id">
 <path refid="class.path"/>
 <fileset dir="${weblogic.gws.app}/APP-INF">
 <include name="**/*.jar"/>
 </fileset>
 </path>
 <java classname="weblogic.jspc" fork="yes" failonerror="yes">
 <classpath refid="jspc.path.id"/>
 <arg line="-webapp ${weblogic.gws.app}/web -compiler ${javac.exec} -classpath ${gws.cl} -compileAll -d ${weblogic.gws.app}/web/WEB-INF/classes -depend -k -keepgenerated -verbose -verboseJavac"/>
 </java>
 </target>
 For some reason, this target runs forever, without printing any logs or anthing. It simply hangs at "runJspc :".
 To dig into details, I modified the target as follows :
 <target name="runJspc" depends="prepare">
 <path id="jspc.path.id">
 <path refid="class.path"/>
 <fileset dir="${weblogic.gws.app}/APP-INF">
 <include name="**/*.jar"/>
 </fileset>
 <pathelement path="${weblogic.gws.app}/web/WEB-INF"/>
 </path>
 <java classname="weblogic.jspc" fork="yes" failonerror="yes">
 <classpath refid="jspc.path.id"/>
 <arg line="-d ${weblogic.gws.app}/web/WEB-INF/classes -classpath ${gws.cl} -compiler ${javac.exec}" />
 <arg value="-k" />
 <arg value="-compileAll" />
 <arg value="-depend" />
 <arg value="-verboseJavac" />
 <arg value="${weblogic.gws.app}/web/retail/jsp_app/home/ft_home.jsp"/>
 <jvmarg line="-Xms512m"/>
 <jvmarg line="-Xmx512m"/>
 </java>
 </target>
 Now it throws below error & stops.
 runJspc:
 [java] [jspc] warning: expected file /WEB-INF/web.xml not found, tag libraries cannot be resolved.
 [java] <Apr 14, 2005 11:49:19 AM PDT> <Warning> <HTTP> <BEA-101181> <Could not find web.xml under WEB-INF in the doc root: ..>
 Is there any way to resolve one of the above two problems ?

Hi Arun,
 It seems that in the second ant target, you decide to compile just a single jsp, while in the first you were trying to compile the complete jsps in a application.
 But in the second target, you forgot to mention -docroot / -webapp target. As a result, the specific error!!.
 To actually debug the first target, try running the program first on commandline , using weblogic.jspc directly passing the arguments.
 This way , you would have a better control over the target, and may be able to isolate the issue easily.

Problem when using weblogic.jspc from an IDE

I am trying to call JSPC from an IDE (as part of an Eclipse Builder). To optimize performance I want to avoid to spwan a new process. So I am trying to call weblogic.jspc's main method directly from the IDE. Everything works fine for simple simple pages.
 But when the page refers to a tag library with a tag providing a TagExtraInfo class, weblogic.jspc complains about the class not extending the TagExtraInfo base class although it does:
 Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
 Translation of /rentalcar/tiles/i18n/CarCapacityView.jsp failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
 I could not figure out what exactly causes the problem. Using exactly the same settings workes just fine.
 Any suggestions?

The full stack trace reads as follows:
 
 Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
 
 Translation of /common/include/i18n/definitions.inc failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
 
 at weblogic.jspc.runJspc(jspc.java:559)
 at weblogic.jspc.runBodyInternal(jspc.java:410)
 at weblogic.jspc.runBody(jspc.java:319)
 at weblogic.utils.compiler.Tool.run(Tool.java:146)
 at weblogic.utils.compiler.Tool.run(Tool.java:103)
 at weblogic.jspc.main(jspc.java:708)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.compileJSP(PresentationBuilder.java:1173)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.checkResource(PresentationBuilder.java:718)
 at tui.vrp.tools.presentation.builder.PresentationBuilder$PresentationDeltaVisitor.visit(PresentationBuilder.java:102)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.incrementalBuild(PresentationBuilder.java:1268)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.build(PresentationBuilder.java:677)
 at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:593)
 at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
 at org.eclipse.core.runtime.Platform.run(Platform.java:783)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
 at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
 at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
 at org.eclipse.core.runtime.Platform.run(Platform.java:783)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
 at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
 at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
 at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139)
 at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:200)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
 
 Unfortunately it doesn't really give any real reason - it is a general piece of code in jspc to report problems.
 
 But I dug a lot bit deeper into the code and realized that the original problem is a ClassCastException in line 1290 of class StandardTagLib, which reads as follows:
 
 tagextrainfo = (TagExtraInfo)Beans.instantiate(classloader, s3);
 
 This looks quite obvious that the class named by s3 simply is no extension of TagExtraInfo, but unfortunately the only class with that name being referenced by the class path does extend this class. I wondered what the problem might be and came up with the following answer:
 
 The class of the bean instantiated by Beans.instantiate extends a class with the name "javax.servlet.jsp.tagext.TagExtraInfo" which is cast to another class with exactly the same name, but a different class loader. Since neither of the class loaders is parent of the other one, both classes are not considered being the same class although they have the same name. Sounds weird, but exactly this is the problem!
 
 Where does it come from and why it works fine when the tool is executed in a separate thread or on the console?
 
 From my understanding the problem is caused in line 395 of the class weblogic.jspc:
 
 GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder);
 
 This line of code creates a class loader not knowing a parent class loader by which the class weblogic.jspc was loaded. All classes weblogic.jspc is using or calling will be loader by either the same or a parent class loader - this is important to understand. Since TagExtraInfo is directly referenced by StandardTagLib one instance of the class object (the object of type class) will be generated and linked when the class StandardTagLib is instantiated for the first time by the class loader which loaded weblogic.jspc (or by its parent). This is consequence which can not be avoided.
 
 But now look at line 1290 of class StandardTagLib: It explicitly requests the class to be loaded by the GenericClassLoader instantiated in line 395 of the class weblogic.jspc. This class loader, off course, is not aware of the same class just being loaded by another class loader since it has no knowledge of it. It simply creates a fresh copy of the class object, which only differs in the reference to the class loader which created this class object.
 
 Actually, I figured that the following line of code replacing the upper one, would resolve the problem:
 
 GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder, this.getClass().getClassLoader());
 
 Doing this, the GenericClassLoader would know its logical parent by reference and would implicitly - thanks to the implementation of java.lang.ClassLoader - try to find the class using its parent first, would find a valid class, and hence use the same instance of the class object instantiated by the parent class loader. The problem would be solved.
 
 It works fine in the console or under a running application server, because they will always have the weblogic jar in their system class path. ClassLoaders not having a parent are implied to have the system class loader as their parent - the piece of code does work in this case.
 
 Under Eclipse this is no option, off course. We would restrain us to exactly this version of the APIs used by the weblogic version in the system class path.
 
 I was trying to patch this myself by extending weblogic.jspc by my own class to pass on a proper class loader knowing its parent, and I was sort of successful: The problem disappeared. But I can't gain exactly what I am looking for, because the method runJspc with four parameters (around line 447) of weblogic.jspc is private to the class and its public brother always passes true to this method as the fourth parameter - causing jspc to recompile all JSPs instead of just the requested ones.
 
 Everything refers to WL81SP3.
 
 That's were I got stuck currently. I have read some postings about this problem in the internet - some dating far back into the history. So, I have the impression that there have been some folks around with the same problem. I think the patch I suggested does not any harm and I could simply use jspc in my builder without any problems.
 
 Regards,
 
 Elmar Schwarz

Java.io.IOException using weblogic.jspc

I've seen a number of similar questions on this but no answers. Can
 anyone provide some insight?
 I have a JSP containing a custom tag library that compiles and executes
 successfully when deployed as a war file under wls 5.1 sp8 but running
 the weblogic.jspc compiler from the command line produces a
 java.io.IOException: cannot resolve '/WEB-INF/tlds/struts-template.tld'
 into a valid tag library.
 The web.xml file includes:
 <taglib>
 <taglib-uri>/WEB-INF/tlds/struts-template.tld</taglib-uri>
 <taglib-location>/WEB-INF/tlds/struts-template.tld</taglib-location>
 </taglib>
 The command I'm using is:
 java -Dweblogic.home=/opt/weblogic
 weblogic.jspc
 -d /home/wmeier/java/StrutsTemplate/build/jsp
 -docroot /home/wmeier/java/StrutsTemplate/web
 -contextPath StrutsTemplate
 -encoding default
 -keepgenerated
 -g
 introduction.jsp
 I can get the jsp compiler to work when I change the taglib uri
 declaration from
 <%@ taglib uri='/WEB-INF/tlds/struts-template.tld'...
 to
 <%@ taglib uri='/tlds/struts-template.tld'
 This modified uri also works as a war file under WebLogic but fails
 under the Tomcat 3.2 reference implementation.
 Does anyone have any ideas how I can get the compiler to work without
 hacking the taglib uri?
 Thanks,
 Bill Meier


CeciNEstPasUnProgrammeur wrote:
Hm, well... the API docs say for non-existing files you get an IllegalArgumentException, and IOException is for "no application registered" or "application won't start"...
Just a guess: is the firewall blocking the execution?I don't think it is a fire wall issue since everything runs on the same machine (the file is created and invoked on the same machine)
Any other ideas?

How to use Weblogic Server 6.1 build.xml with ant

Hi Java's
I have downloaded the latest version of BEA Weblogic server 6.1,they have changed the build.cmd to build.xml for compiling and building the ejb applications.they are telling that we have use $ant to run the build.xml but i couldn't able to do that.i'm getting "command not found error"..i'm using winnt.please help me how to use $ ant.Is it a seperate exe or batch file that i have to download ?if so where to download it.how to use it.please help.
Regards
Balaji

To use it after installation, set your path to your
<ant_installation_dir>\bin, then navigate to the diectory containing the build.xml. then follow the instructions in the weblogic documentation for running ant.

How to use the scene deconstruction option for Avatar

I am able to access all the iTunes extras feature for Avatar except the Scene Deconstruction feature. Whenever I use any of the 3 options available in scene deconstruction it just opens up a blank grey screen with Final, picture in picture, template and capture text and the pause sign. Nothing shows or plays I have been at it for over 2 days now. Will someone help me or guide me to a video where I can learn how to use this feature?

Compare is not exposed via any API.

Precompiling JSPs using weblogic.jspc

Hello,
My question has more to do with getting the Weblogic precompiler to understand <%@ include file="myFilejsp" %> directives.
Test scenario:
In our application, we have used a common JSP page say 'commonJSP' as a header and have included 'commonJSP' in all our other JSP pages.
Suppose my commonJSP is like this:
<%
String hello= "Hello";
%>
and suppose my index.jsp is like this
<%@ include file="commonJSP" %>
<%
System.out.println(hello);
%>
Now when I serve index.jsp to clients it compiles correctly because the commonJSP is included in the source before compiling.
HOWEVER, when precompiling the JSPs in my web application using the <java weblogic.jspc ..> tag in my ant build file, I am getting errors on compiling index.jsp that 'hello' cannot be resolved.
When using the WebLogic JSP compiler, is there any way to tell the compiler to not treat JSP pages as individual 'servlet' classes but look at the 'big picture'?

Anybody ?

How to use weblogic.Admin to set JMS ErrorDestination property on WLS 7?

This thread is talking about using weblogic.Admin to set the ErrorDestination property.
 http://forums.bea.com/bea/thread.jspa?threadID=200036378&messageID=202187327&start=0
 We run the script against the WLS 7.0 server, script get 'OK' result but it didn't work (property wasn't set). Some error is reported in the admin.log on the server.
 We also run the scipt against the WLS 8 server. It worked perfectly.
 Does anyone know whether this works at all on WLS 7?

The reason we are using weblogic.Admin is that we are using conf2admin to generate the scripts. weblogic.Admin seems to be the only option for WLS7. Thanks for your suggestion and will definitely check out WLST.
 The full error message is:
 ####<Aug 27, 2004 8:55:20 AM NZST> <Emergency> <Management> <rbd1> <admin> <ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <141067> <The value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue specified for the ErrorDestination attribute is not valid. MBean: n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue. Method: setAttributes. Exception: javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
 Target exception: java.lang.NullPointerException
 .>
 javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
 Target exception: java.lang.NullPointerException
 at weblogic.management.internal.DynamicMBeanImpl.checkAttributeValueIsLegal(DynamicMBeanImpl.java:1517)
 at weblogic.management.internal.DynamicMBeanImpl.prepareForModification(DynamicMBeanImpl.java:1440)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1004)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:353)
 at weblogic.management.internal.DynamicMBeanImpl.setAttributes(DynamicMBeanImpl.java:827)
 at com.sun.management.jmx.MBeanServerImpl.setAttributes(MBeanServerImpl.java:1475)
 at weblogic.management.internal.RemoteMBeanServerImpl.setAttributes(RemoteMBeanServerImpl.java:905)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
 at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

Error Using weblogic.jspc --- java.lang.ExceptionInInitializerError

Hi,
 I am trying to use the weblogic.jspc compiler to pre-compile my jsp
 files so that I can verify that they compile w/o having to visit the
 page. I am using Weblogic 4.5.1. I am encountering the following
 error:
 java.lang.ExceptionInInitializerError
 at java.lang.Throwable.<init>(Compiled Code)
 at java.lang.Error.<init>(Compiled Code)
 at java.lang.LinkageError.<init>(Compiled Code)
 at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
 at java.beans.Beans.instantiate(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
 at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
 at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
 at weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled
 Code)
 at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
 at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
 at weblogic.jhtmlc.runBody(Compiled Code)
 at weblogic.jspc.runBody(Compiled Code)
 at weblogic.utils.compiler.Tool.run(Compiled Code)
 at weblogic.jspc.main(Compiled Code)
 Have any of you seen this? Can you tell me what I am doing wrong
 (Classpath, etc.)?
 Any and all help would be greatly appreciated.
 The command line I am using is:
 java -verbose -classpath
 $CLASSPATH:/apps/weblogic/license:/apps/weblogic/classes:/apps/weblogic/lib/weblogicaux.jar
 weblogic.jspc -d $HOME/weblogic/myserver/classfiles/examples
 100-Welcome.jsp
 Regards,
 Richard


Fixed with a patch CR0737797 and CR062538 for the 6.1 sp3 source line
 Prasanna Yalam

How to use weblogic.jspc -J option

Similar Messages

Maybe you are looking for