Swf, swc and the mxmlc, compc ant tasks

I'm a bit confused on the end result of the mxmlc / compc ant
tasks, or maybe the difference between swf and swc files. I have a
library of 60 or so AS3 files used for
serialization/deserialization of my Java backend (using GDS for
serialization of data between java serverside and my flex front
end). I first use the compc ant task on these AS3 files to create a
swc file. This swc is 453316 bytes. With this flash library, I use
the mxmlc ant task on my mxml file, which produces a 201,492-byte
swf file.
I have a couple questions related to the procedure above.
Shouldn't the swf file include the swc file, and hence be bigger
than the swc? I'm just wondering if I deploy the swf file, will it
have all it needs in the swc file to perform the functions
correctly?
My second question relates to setting the
keep-generated-actionscript="true" in the mxmlc task. When
doing this, I see all the AS3 code generated. However, it does not
include 55 of the 60 AS3 classes compiled in the swc. It only
generated AS3 code for those AS3 classes explicitly declared in the
mxml code (via import and actual declaration). Am I doing something
wrong here or is this the way flex does its thing?
The reason why I'm concerned about this is that I'm getting a
"ArgumentError: Error #2004: One of the parameters is
invalid" issue am I'm think its happening in the AS3 code (not
the Java server side) and I don't know how to debug this.
Any help would be appreciated. Thanks in advanced!
-los

I am also facing with the same problem.....
Is there any resolution for this problem.?
Not sure where i am going wrong.
Any help will be appreciated.
Thanks in advance.

Similar Messages

Compc ant task and external framework

I'm writing an ant task to compile a couple of libraries into
SWCs and then a shell app (that uses the libraries) into a SWF for
deployment. If I compile the libraries by hand then run just the
'mxmlc' part of my ant script it compiles fine. However when I try
and first compile a library into a SWC with 'compc' it compiles but
then the shell app complains that the classes from the library are
missing. One thing that may be causing the problem is my library
path (through flex builder) has it's framework.swc set to 'Link
Type: External' and I'm not sure how to define that with 'compc'.
The weird thing is the flex builder compiled and 'compc' compiled
SWCs are the same size. Here's my target for 'compc':

 <mxmlc
 file="${project.name}/src/Test.mxml"
 output="${build.mxmlc.dir}/Test.swf"
 static-link-runtime-shared-libraries="true"
 >
 <load-config filename="${air.config}"/>
 <source-path path-element="${project.name}/src" />
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/framework.swc">
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swz"/>
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/datavisualization.swc">
 <url rsl-url="${rsl.dir}/datavisualization_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 </mxmlc>
This also seems to work. AIR libraries are included in my output SWF. It all happens right when I have static-link-runtime-shared-libraries="true" . Why? Why does that not work when i have static-link-runtime-shared-libraries="false" ??

Unable to stream SMIL files unless the html page, swf file and the smil ffile are on the FMS server.

When I place the .swf, smil and http files on the FMS server the SMIL stream test sample works fine
But When I move the files to my web server I get Connection error.
This is the same issue discussed in http://forums.adobe.com/thread/554107
I added a ‘base’ variable but it did not work for me.
The SMIL file has the correct path to the sample files and FMS server
<meta base="rtmp://200.200.200.23/vod/" />
I am able to stream files from my html file on my webserver not the FMS server by pointing to the FMS server at rtmp://200.200.200.23/vod/mp4:sample1_1500kbps.f4v
Is this a domain security setting? If so, where do I change it?
If not How do I get FMS to stream SMIL files without installing a webserver with FMS?
Thanks,

Hi,
I think there is bug with that videoPlayer.swf which is used by index.html of webroot folder of FMS to play media files, its not able to parse smil file correctly. I used some other player and used the smil file and kept it on http server other than fms server so it was able to dynamically stream videos. So I would suggest you to create your own player which uses smil file. You can take help from the below link to create player:
http://www.adobe.com/devnet/flashmediaserver/articles/dynstream_advanced_pt1_05.html
Regards,
Amit

JSFL or SWF Panels and the ActionScript Editor

Howdy, I'm hoping to be able to write JSFL commands or make swf panels for the Flash IDE that will work with the ActionScript Editor. Mind you, not the ActionScipt panel that is open with a .fla, but with the Flash text Editor that edits .as files directly. I've been able to get it going with the actions panel, but don't know if it's possible with the .as editor. Any ideas on how to accomplish this?
Essentially I'm hoping to create a panel that generates getters/setters automagically, like FlashBuilder does, but with some additional features, like ASDoc commenting etc. Also, I want to have it generate empty functions for any event listener callbacks as I code the listeners.
Thanks in advance!
-Ted

Never heard of that, and not sure if the hot fix addresses that, but make sure you have it - your Flash version should be 10.0.2 in Help > About
You can get the update from: http://www.adobe.com/support/flash/downloads.html

Mxmlc ant task and locales

Hi,
I have property files for several locales, for example
locale/en_US, locale/en_GB, locale/es_ES, and locale/es. Running
from within FlexBuilder I can see the various locales just fine.
However when creating the .swf file using ANT and the <mxmlc>
task, only en_US is available. I've attached a snippet from my ANT
script.
Thanks in advance,
Rich

Are you using Adobe FlexAnt?
On this
page
, there is a <compiler.library-path> node that seems to
import a bundle directory that contains locales. I believe
<compiler.library-path> is from FlexAnt, so you would need to
enable it if you haven't.
Also look on the next page from the link I posted, there is
another example on how to import bundles in an automation.

Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
I'll try to attach my WSDL file and build.xml so you can follow along.
I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
Some preliminary information about my environment.
Environment:
 Windows XP Pro SP2
 WebLogic 9.1
 Java 1.5.0_04
Service Name:
 AppRelease
Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
Now, for the issues.
1. Bug:
In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
2. Bug:
In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
[jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
3. Bug:
In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
4. Annoyance:
The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
5. Annoyance:
The WSDL generated by wsdlc has my CSS specification stripped.
Work around: I donâ€™t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
6. Annoyance:
The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
7. Annoyance:
The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
8. Bug:
The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
[jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
[jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
Work around: Use unique element names for the input parameters of the services operations.
9. Bug:
Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
This seems to be due to the weblogic.jar file not being in the System Classpath.
However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakinâ€™ jar list]". In the big freakinâ€™ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
Work around: Make sure the weblogic.jar is in the System Classpath.
10. Bug:
I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
ant build-serviceBuildfile: build.xml
build-service:
[jwsc] 1 JWS files will be processed.
[jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
[jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
[AntUtil.deleteDir] Deleting directory <some temporary directory>
BUILD FAILED
java.lang.ExceptionInInitializerError
At this point, I am completely stymied about how to proceed.
I wonder what new issues await once this 10th issue is addressed.
Really, is this tool set ready for prime time?

Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in. 
I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.

I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post. 
I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.

Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse. 
I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.

If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file.. 
Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.

Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.

Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.

Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations. 
Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.

Regards,
Mike Wooten
Thanks for the follow-up.
Mike McAngus

Changing the wldeploy ant task behaviour

wldeploy ant task while deploying the application deploys it under <configured weblogic upload dir>/<application name>/app/ application name.
Is there any way we can change this behaviour as we couldnt find the options in ant task to change it

That is all you should have to do, the ant tasks are sitting inside the
weblogic.jar.
Cheers
mbg
"Shane Witbeck" <[email protected]> wrote in message
news:[email protected]..
Rob Bennett <[email protected]> wrote in message
news:<[email protected]>...
What is required for the wldeploy ant task to function properly? I am
able to use it when I run ant from the command line and use the version
of ant that came with Weblogic 8 (I have the platform beta, not the
release version). When I try to use it inside of eclipse (which uses
its own copy of ant), the task fails.. it looks like it is trying to
generate RMI stubs. If anyone can shed light on what I am missing from
the eclipse environment, I would appreciate it.
-RobI actually just got it to work by adding the weblogic.jar to my
classpath. (Im using WL 8.1).
-Shane

Ant tasks getDestinations and getDataSourcesDescriptor conflict

I have a simple target that calls the getDestinations oracle ant task and then calls the getDataSourcesDescriptor ant task. Only the first task run ever returns data. If getDestinations is first, JMS info is returned but no data sources info. If getDataSourcesDescriptor is first, data sources info is returned but no jms info. If you have two tasks of the same type, same story; only the first task returns data.
Anyone have any ideas?

cfr wrote:
@lahwaacz,
Could you point me to documentation regarding bugs/problems with laptop-mode tools? I'm using that right now and it has always worked pretty well but I'm currently seeing higher temperatures (~10C higher on average) and trying to figure out why.
My fan operates continually but not, I think, very aggressively. But it has always done that so I assume it is normal for this laptop. (Have no idea really but it doesn't seem out of the way - it is a laptop, after all...)
I don't know anything about fan control, my laptop controls fan speed automatically, I can't even get current fan speed.
The main problem with laptop-mode-tools is that it's very huge, and the bigger the program is, the slower is the execution. Another problem is that it's connected to both battery and AC adapter ACPI events (see /etc/acpi/events/lm_{ac_adapter,battery}). On my laptop, those events are sent at the same time, resulting in running laptop-mode-tools twice. Most people once configure laptop-mode-tools to their liking and their hardware, so I think there is no need for such an extensive software like laptop-mode-tools, if something simpler does the same (or better) job.
Also laptop-mode-tools can conflict with pm-utils (which are installed on many systems as dependency for some packages):
https://wiki.archlinux.org/index.php/La … able_on_AC
https://bbs.archlinux.org/viewtopic.php?id=106989

Can i reference external flex-config in flexunit ant task?

flexunit gurus,
i'm trying to figure out how to best specify the compiler arguments for the flexunit ant task in flexunit 4.1 beta 1. from the documentation i see this sample flexunit usage:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
<testSource dir="${main.src.loc}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${lib.loc}" />
</flexunit>
in this example, the source and library paths are explicitly listed. in this simple example all the needed libraries reside within a single directory.
when i build my application, i use a custom flex-config.xml file, as the following snippet shows:
 <mxmlc file="${application.file}" output="${swf.debug.file}" debug="true" headless-server="${headless.server}">
 <load-config filename="${flex.config.file}" />
 </mxmlc>
in that custom flex-config.xml file i list all the build options (e.g. source dirs, library paths, theme, etc.) appropriate for building the application. the libraries i reference are in a number of different directories (in general each 3rd party library is in a different directory).
in the flexunit task, i could individually reference all the same libraries that are in the flex-config.xml, but that'd be a pain to keep them in sync. i suppose i also could parse the flex-config.xml to extract the library information and use that to populate the library argument. really what i want to say in the flexunit task is "build all source and tests as indicated in flex-config.xml, then run the tests", perhaps with a syntax like the following:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
 <load-config filename="${flex.config.file}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${flexunit.lib}" />
</flexunit>
i'd rather keep the flex-config.xml file free of any test specific information, so ideally i'd specify the path to the flexunit swc's and the test path in the flexunit task (as in the above example).
is there support for such usage currently or planned for in the future? recommendations on how best to accomplish my goal of not duplicating library information already present in a custom flex-config.xml?
thanks.
-mike

hi brian,
thanks for your response.
i understand the desire to avoid re-implementing the flex sdk ant tasks. i'm not sure that can reasonably be accomplished wihen the TestRunner is dynamically generated from within the flexunit task. in addition to the source path and library path, the theme setting and namespaces settings can affect successful compilation, and the runtime-shared-library-path setting can affect whether the produced swf runs correctly.
perhaps there's an alternative. what if we separate the creation of the TestRunner.mxml from the compilation and the execution of the tests. if flexunit offers an ant task that can produce (but not run) a TestRunner.mxml, i can write the mxmlc task that compiles it properly, and then i can invoke the old style flexunit specifying the swf argument. this would still accomplish my primary goal of not needing to manually enumerate every test file in a TestRunner.mxml that i have to maintain (and which neither Flash Builder nor maven builds require). to compile the TestRunner.mxml, i'd load in my custom flex-config.xml, then append to the source path and library path to include my test directory and flexunit libraries.
maybe something like the following to create the TestRunner:
<generatetestrunner output="${bin.loc}/TestRunner.mxml">
 <testSource dir="${test.dir}">
 <include name="**/*Test.as" />
 </testSource>
</generatetestrunner>
thoughts?
one other thing i noticed about the current library argument to flexunit is that it assumes a directory even if you provide an explicit path to an swc (i tried switching <library dir...> to <library file...> but that didn't seem to make a difference). in my case, there are specific swc's i need in the library path, and the task assuming i mean a directory when i specify an explicit swc is problematic. the directory my swc libraries are contained in sometimes contain multiple and conflicting versions of a library (each library directory contains various snapshot builds of the library). i need a way to explicitly indicate which library to use.
finally, could you point me to the java source for the flexunit ant tasks? i've found the flexunit action script source ok but haven't found where the java ant task is defined.
thanks.
-mike

ANT task wsgen error while deploying RPC style web service

Hi
I am trying to assemble/deploy an rpc style weblogic web service using the 'wsgen'
Ant task and the build.xml scripts provided with the samples. I get this error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>

WLS6.1, service pack 2? I didn't know there were any service packs for 6.1 and
6.0 didn't support wsgen and web services??
simon.
manoj cheenath <[email protected]> wrote:
>
>
This is a known bug which is fixed in WLS 6.1 SP2.
The workaround is to change the complex data types
to have more than one level package names.
for eg: change ....
package foo;
class Data{}
to :
package foo.bar;
class Data{}
-manoj
Praveen wrote:
Hi
I am trying to assemble/deploy an rpc style weblogic web service usingthe 'wsgen'
Ant task and the build.xml scripts provided with the samples. I getthis error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>
-----------------------------------------------------------------<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
This is a known bug which is fixed in WLS 6.1 SP2.
The workaround is to change the complex data types
 to have more than one level package names.
for eg: change ....
package foo;
 class Data{}
to :
package foo.bar;
 class Data{}
-manoj
Praveen wrote:
<blockquote TYPE=CITE>Hi
 I am trying to assemble/deploy an rpc style weblogic web service
using
the 'wsgen'
 Ant task and the build.xml scripts provided with the samples. I get
this error:
 Please help
 Thanks,
 Praveen
 -----------------------------------------------------------------
 C:\test>ant
 Buildfile: build.xml
webservice:
clean:
 [delete] Deleting directory C:\test\build
init:
 [mkdir] Created dir: C:\test\build
 [mkdir] Created dir: C:\test\build\META-INF
 [copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
 [javac] Compiling 5 source files to C:\test\build
jar_ejb:
 [jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
 Error at line:8 col:12 ':' Already got a ':' in name
 at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
 on(SAXElementFactory.java:60)
 at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
 at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
 EventStream.java:28)
 at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
 at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
 at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
 )
 at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
 :1125)
 at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
 )
 at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
 a:1415)
 at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
 at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
 at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
 at org.apache.tools.ant.Target.execute(Target.java:153)
 at org.apache.tools.ant.Project.runTarget(Project.java:898)
 at org.apache.tools.ant.Project.executeTarget(Project.java:536)
 at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
 at org.apache.tools.ant.Target.execute(Target.java:153)
 at org.apache.tools.ant.Project.runTarget(Project.java:898)
 at org.apache.tools.ant.Project.executeTarget(Project.java:536)
 at org.apache.tools.ant.Project.executeTargets(Project.java:510)
 at org.apache.tools.ant.Main.runBuild(Main.java:421)
 at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>
 -----------------------------------------------------------------</blockquote>
</html>

Servicegen ant task in weblogic 10.3

Hi,
Could you please let me know , the werbservice related ant tasks from weblogic 8.1 (say servicegen)
are supported in weblogic 10.3 ?
I am in a process of migrating application from 8.1 to 10.3. For building the application I am using 'ant'.
Thanks,
Sajan CR

Apparently the ant tasks are no longer described on the oracle doc pages as they were on the bea pages.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/overview.html#using_ant
"To view the documentation for a specific version of Ant, such as the version included with WebLogic Server, download the Ant zip file from http://archive.apache.org/dist/ant/binaries/ and extract the documentation."

Properties file not found by classloader when using wlappc ant task

I have encountered a problem with the WebLogic Ant task "wlappc". When this task compiles a webmodule that uses the struts 1.1 framework I get the below error. This struts based web module deploys and runs fine on BEA Weblogic 8.1 SP2 as an exploded EAR structure. But when I attempt to precompile all the J2EE modules the struts web module will not compile with wlappc. The project is strutured correctly in a split directory structure. The problem area seems to be that we are using the struts-el (struts-el.jar) classes which need the properties files located in the struts.jar. The classloader seems to space out when running via the wlappc ant task. I tried adjusting the classpath via the "classpath" wlappc ant task attribute - but no success. Has anyone had this or a similiar problem?
Any suggestions would be greatly appreciated!
Thanks in advance,
Scott
Error from ant task is as such:
compile:
[javac] Compiling 256 source files to C:\My Builds\WWL\build\wwlentityejb
[javac] Compiling 4 source files to C:\My Builds\WWL\build\wwlsessejb
[javac] Compiling 91 source files to C:\My Builds\WWL\build\wwlweb\WEB-INF\classes
appc:
[wlappc] [appc] Compiling EAR module 'wwltestweb'
[wlappc] [JspcInvoker]Checking web app for compliance.
[wlappc] <Jul 28, 2004 4:38:47 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "JUnitEETestServlet".>
[wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "JUnitEETestServlet".>
[wlappc] [appc] Compiling EAR module 'wwlweb'
[wlappc] [JspcInvoker]Checking web app for compliance.
[wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "wwlActionServlet".>
[wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "wwlActionServlet".>
[wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "I18NFilter".>
[wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "Security Filter".>
[wlappc] [jspc] parsing /admin/jsps/menu.jsp:
[wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
[wlappc] SEVERE: MessageResourcesFactory.createFactory
[wlappc] java.lang.ClassNotFoundException: org.apache.struts.util.PropertyMessageResourcesFactory
[wlappc] at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
[wlappc] at java.security.AccessController.doPrivileged(Native Method)
[wlappc] at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
[wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
[wlappc] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:272)
[wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
[wlappc] at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
[wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
[wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
[wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
[wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
[wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
[wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
[wlappc] at java.lang.Class.forName0(Native Method)
[wlappc] at java.lang.Class.forName(Class.java:140)
[wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
[wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
[wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
[wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
[wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
[wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
[wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
[wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
[wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
[wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
[wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
[wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
[wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
[wlappc] at weblogic.jspc.runJspc(jspc.java:550)
[wlappc] at weblogic.jspc.runJspc(jspc.java:437)
[wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
[wlappc] at weblogic.appc.compileWAR(appc.java:859)
[wlappc] at weblogic.appc.compileModules(appc.java:650)
[wlappc] at weblogic.appc.compileEAR(appc.java:733)
[wlappc] at weblogic.appc.compileInput(appc.java:458)
[wlappc] at weblogic.appc.runBody(appc.java:184)
[wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wlappc] at weblogic.appc.main(appc.java:1028)
[wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
[wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
[wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
[wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
[wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
[wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
[wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
[wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
[wlappc] SEVERE: MessageResourcesFactory.createFactory
[wlappc] java.lang.ExceptionInInitializerError
[wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
[wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
[wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
[wlappc] at java.lang.Class.forName0(Native Method)
[wlappc] at java.lang.Class.forName(Class.java:140)
[wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
[wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
[wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
[wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
[wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
[wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
[wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
[wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
[wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
[wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
[wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
[wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
[wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
[wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
[wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
[wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
[wlappc] at weblogic.jspc.runJspc(jspc.java:550)
[wlappc] at weblogic.jspc.runJspc(jspc.java:437)
[wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
[wlappc] at weblogic.appc.compileWAR(appc.java:859)
[wlappc] at weblogic.appc.compileModules(appc.java:650)
[wlappc] at weblogic.appc.compileEAR(appc.java:733)
[wlappc] at weblogic.appc.compileInput(appc.java:458)
[wlappc] at weblogic.appc.runBody(appc.java:184)
[wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wlappc] at weblogic.appc.main(appc.java:1028)
[wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
[wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
[wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
[wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
[wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
[wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
[wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
[wlappc] Caused by: java.lang.NullPointerException
[wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
[wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
[wlappc] ... 52 more
BUILD FAILED
file:C:/My Sources/WWLEar/wwlear/build.xml:128: weblogic.utils.compiler.ToolFailureException: [J2EE:160119]Appc is unable to process the file 'C:\My Builds\WWL\build'. The following error occurred:
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
at java.beans.Introspector.getBeanInfo(Introspector.java:372)
at java.beans.Introspector.getBeanInfo(Introspector.java:207)
at java.beans.Introspector.getBeanInfo(Introspector.java:193)
at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
at weblogic.jspc.runJspc(jspc.java:550)
at weblogic.jspc.runJspc(jspc.java:437)
at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
at weblogic.appc.compileWAR(appc.java:859)
at weblogic.appc.compileModules(appc.java:650)
at weblogic.appc.compileEAR(appc.java:733)
at weblogic.appc.compileInput(appc.java:458)
at weblogic.appc.runBody(appc.java:184)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.appc.main(appc.java:1028)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
Caused by: java.lang.NullPointerException
at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
... 49 more
- with nested exception:
[java.lang.ExceptionInInitializerError]
Total time: 42 seconds

Hi Rob,
I also gets this error when I deploy my application using struts 1.2.2 with struts-el.jar also.
The error is thrown when the server comile the jsp's :
<BEA-101047>[ServletContext(id=20164970,name=tracer,context-path=/tracer)] classfile up-to-date for JSP /webdatagrid/layouts/default/customize.jsp>
####<Sep 2, 2004 2:05:26 PM EDT> <Info> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
<BEA-101047> <[ServletContext(id=20164970,name=tracer,context-path=/tracer)] checking /webdatagrid/layouts/default/exceldownload.jsp:>
####<Sep 2, 2004 2:05:30 PM EDT> <Error> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
<>
<BEA-149201> <Failed to complete the deployment task with ID 0 for the application tracer-webapp-application-uncontrolled.
java.lang.NullPointerException
at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
at java.beans.Introspector.getBeanInfo(Introspector.java:372)
at java.beans.Introspector.getBeanInfo(Introspector.java:207)
at java.beans.Introspector.getBeanInfo(Introspector.java:193)
at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4908)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4886)
at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:2342)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:628)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:626)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3011)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[java.lang.NullPointerException]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2491)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
####<Sep 2, 2004 2:37:29 PM EDT> <Info> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
<>
<BEA-149059> <Module tracer of application tracer-webapp-application-1_6_3_510 is transitioning from unprepared to prepared on server sit1tracerweb
.>
####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
<BEA-101211> <tracer-webapp-application-1_6_3_510:tracer Precompiling JSPs at startup with JSP config [JspConfig: verbose=true,packagePrefix=jsp_servl
et,-compiler=javac,compileFlags=,workingDir=./applications/tracer/WEB-INF/classes,pageCheckSeconds=5,superclass=weblogic.servlet.jsp.JspBase,keepgener
ated=true,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=true,debugEnab
led=false,printNulls=true,jspServlet=null].>
I've looked at the source code ant it is actually using the current thread's classloader.
The fact is that it works fine when deployed to tomcat 4.1.30, but it fails when deploying on our weblogic managed servers.
Thanks
Julien De Santis
CGI Group

Problems with wlserver ant task for WL 8.1

hi
i have a problem with using wlserver ant task for Weblogic 8.1
basically i want to start the server that is already preconfigured and deploy
one ear.
here's what i do:
<taskdef name="wlserver" classname="weblogic.ant.taskdefs.management.WLServer">
<classpath refid="lib.classpath"/>
</taskdef>
<wlserver action="start" dir="D:/BEA/user_projects/domains/mydomain"
output="wls81.log"/>
(and then the deployment task - irrelevant here)
the classpath is generated automatically and includes all jars in the specific
project directory:
 <path id="lib.classpath">
 <fileset dir="${proj.lib.dir}">
 <include name="**/*.jar"/>
 </fileset>
 </path>
(weblogic.jar is there as well)
the problem is when i run it, the following happens:
- if i have action="start" (or no action attribute at all), i get the following
exception:
java.lang.NullPointerException
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:86)
at weblogic.Home.getPath(Home.java:94)
at weblogic.Home.getFile(Home.java:99)
at weblogic.ant.taskdefs.management.WLServer.execute(WLServer.java:260)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
- if i change it to action="startup" as specified on "wlserver Ant Task Reference"
it seems that this task is skipped completely. no error messages, no stack trace,
nothing. i tried -verbose and -debug options on ant, but there're no logs displayed
whatsoever. it takes less than a second to run this task so i presume it's just
getting skipped completely.
i run this from the standalone Ant 1.5.4 on Windows environment.
i've followed the topic "wlserver Ant task for WebLogic 8.1" where kind of similar
problem is described but putting weblogic.jar on the system CLASSPATH is not an
option for this project.
anyone has any idea about how to get this going?
cheers
Andrei

sounds bug to me. NPE should be correctly handled with appropriate error
message. Please contact BEA support to log the call.
"Andrei Rusakou" <[email protected]> wrote in message
news:[email protected]...
>
hi
i have a problem with using wlserver ant task for Weblogic 8.1
basically i want to start the server that is already preconfigured anddeploy
one ear.
here's what i do:
<taskdef name="wlserver"classname="weblogic.ant.taskdefs.management.WLServer">
<classpath refid="lib.classpath"/>
</taskdef>
<wlserver action="start" dir="D:/BEA/user_projects/domains/mydomain"
output="wls81.log"/>
(and then the deployment task - irrelevant here)
the classpath is generated automatically and includes all jars in thespecific
project directory:
<path id="lib.classpath">
<fileset dir="${proj.lib.dir}">
<include name="**/*.jar"/>
</fileset>
</path>
(weblogic.jar is there as well)
the problem is when i run it, the following happens:
- if i have action="start" (or no action attribute at all), i get thefollowing
exception:
java.lang.NullPointerException
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:86)
at weblogic.Home.getPath(Home.java:94)
at weblogic.Home.getFile(Home.java:99)
atweblogic.ant.taskdefs.management.WLServer.execute(WLServer.java:260)
atorg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
- if i change it to action="startup" as specified on "wlserver Ant TaskReference"
it seems that this task is skipped completely. no error messages, no stacktrace,
nothing. i tried -verbose and -debug options on ant, but there're no logsdisplayed
whatsoever. it takes less than a second to run this task so i presume it'sjust
getting skipped completely.
i run this from the standalone Ant 1.5.4 on Windows environment.
i've followed the topic "wlserver Ant task for WebLogic 8.1" where kind ofsimilar
problem is described but putting weblogic.jar on the system CLASSPATH isnot an
option for this project.
anyone has any idea about how to get this going?
cheers
Andrei

Ant tasks for creating ADF Library

Created an ADF declarative component, exported it as an ADF library and got it working fine. The ADF Library jar was created within JDeveloper by setting up a Deployment profile. The created ADF Library file has the TLD file and TagHandler / Component class files created on the fly and packaged.
Not sure of how We could get the same ADF library created by an Ant task. Are there Ant tasks for creating ADF library available? http://www.connotea.org/user/jdeveloper/tag/ant has some details on the JDeveloper based ant tasks but doesn't have details on creating ADF library.

You can use the ojdeply executable to create and deploy your ADF Library from the commandline:
<Jdev-install-location>/jdeveloper/jdev/bin/ojdeploy -workspace /mydirectory/yourworkspace.jws -profile yourprofile -project yourproject.jpr

Wlappc ANT task "runtimeFlags" attribute doesn't take effect

I am intermittently counter "java.lang.OutOfMemoryError" error while I am running wlappc ANT task to compile jsp pages. I have lots of jsp files (about 500). According to weblogic's document, I set runtimeFlags="-J-ms512m -J-mx1024m". So my ant task looks like this:
 <wlappc source="${websrc}" output="${output}" runtimeFlags="-J-ms1024m -J-mx1024m">
 </wlappc>
 But it doesn't work. It still complains out of memory error. I tried various approach including "-J-Xms1024m -J-Xmx1024m". But not helpful at all.
 So I gave up and ended up using weblogic.appc class to build my jsp pages. So I have fully control of jvm options. I set up -Xms1024m -Xmx1024m as JVM parameters and works well.
 It looks to me that wlappc ANT task ignore runtimeFlags at all. It doesn't take any effect.
 Is it a known bug? anyone succeeded solving OutOfMemoryError by setting runtimeFlags attribute of wlappc ANT task?

I was having the same issue.
 Try using the maxmemory argument for the standard java ant task and calling weblogic.appc:
 <java classname="weblogic.appc" fork="yes" failonerror="true" maxmemory="256m">
 <classpath>
 <fileset dir="${weblogic.home}/server/lib" includes="weblogic.jar,webservices.jar" />
 </classpath>
 <arg value="${ear.dir}" />
 <arg value="-verbose" />
 </java>

Swf, swc and the mxmlc, compc ant tasks

Similar Messages

Maybe you are looking for