Ant with Workshop

When I exported ant build script out of workshop (it creates exported_build.xml),
and run the same script at command line I am getting the following error:
UNCAUGHT EXCEPTION IN JAVELIN COMPILER!
File a pri-1 bug on knex-compilerthread: Exclusive Thread error: com/bea/xml/marshall/SchemaTypeBuilder
stack: java.lang.NoClassDefFoundError: com/bea/xml/marshal/SchemaTypeBuilder
Any help is greatly appreciated.
Thanks, Prasad

The normal "exported_build.xml" file has two hardcoded paths, one for "weblogic.home", and one for "app.dir". If either one of these is invalid when checked out by CruiseControl, then the build will fail. From what you describe, it sounds like the "weblogic.home" value is invalid.
Noting this, I set up a build process in a "build.xml" script that generates a "transformed_build.xml" file from an XSLT stylesheet, which replaces the "weblogic.home" value with the value of "env.BEA_HOME", and replaces "app.dir" with ".". The "build.xml" then runs the "build" target from the "transformed_build.xml" file.

Similar Messages

Unable to start WLS8.1sp4 after extended with Workshop& Integration Templat

Hi,
I have configured three domains of WLS8.1sp4 on
unique ports namely 6001, 7001 & 8001 but
only one domain can be started on the port 7001
but there is a problem starting the other ports.
All the three domains WLS were able to be started
without any problem at all before the domains
were being extended with Workshop and Integration
Templates from the Basic Weblogic Server Domain
in the Weblogic Configuration using the built-in Configuratino Wizard.
Could someone please assist ?
./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=:/dev_app/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/dev_app/bea/weblogic81/common/lib/log4j.jar:/dev_app/bea/weblogic81/server/lib/debugging.jar:/dev_app/bea/weblogic81/server/lib/knex.jar:/dev_app/bea/weblogic81/javelin/lib/javelin.jar:/dev_app/bea/weblogic81/server/lib/wlw-lang.jar:/dev_app/bea/jdk142_05/lib/tools.jar:/dev_app/bea/weblogic81/server/lib/weblogic_sp.jar:/dev_app/bea/weblogic81/server/lib/weblogic.jar:/dev_app/bea/weblogic81/server/lib/ant/ant.jar:/dev_app/bea/jdk142_05/jre/lib/rt.jar:::/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/dev_app/bea/weblogic81/server/lib/xbean.jar:/dev_app/bea/weblogic81/server/lib/wlxbean.jar:/dev_app/bea/weblogic81/server/lib/xqrl.jar:/dev_app/bea/weblogic81/server/lib/netui/netui-compiler.jar:/dev_app/bea/weblogic81/server/lib/wli.jar:/dev_app/bea/weblogic81/server/lib/fop.jar:/dev_app/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/dev_app/bea/weblogic81/server/bin:/dev_app/bea/jdk142_05/jre/bin:/dev_app/bea/jdk142_05/bin:/usr/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-480R/sbin:/opt/sun/bin::/opt/SUNWexplo/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Starting WLS with line:
/dev_app/bea/jdk142_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=/dev_app/bea/weblogic81 -Dwls.home=/dev_app/bea/weblogic81/server -Dwli.home=/dev_app/bea/weblogic81/integration -Dlog4j.configuration=file:/dev_app/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=/dev_app/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Stopping the Weblogic Workshop debugger...
ERROR: Proxy already running...
weblogic.debugging.comm.SocketCommException
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:53)
at weblogic.debugging.comm.ServerSocketComm.accept(ServerSocketComm.java:53)
at weblogic.debugging.engine.ProxyThread.run(ProxyThread.java:81)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.InterruptedIOException: operation interrupted
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:47)
... 3 more
Debugger Stopped.
Stopping Pointbase server...
Pointbase server stopped.

Problem solved since default ports 8453 & 9093 were occupied
But behaviour on Windows for debug is different from Unix which requires unique potr althought windows still works.

RPC/SOAP-Encoded Web Service with Workshop

Is there anyway to create a RPC/SOAP-Encoded Web Service with Workshop ? There is an "encoding" attribute in the autotype ant task but no corresponding properties in Workshop.

Hi,
Thanks for the reference.
I have checked both in the wsdl and the Soap message,
rpc property effectively means rpc/encoded. Now that
would say that RPC/Literal is not supported ?
Here are what the messages looks like with rpc and
document properties
Thanks all for making this clear.
document wlw property = Document/Literal
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<ns:getEmployeeResult xmlns:ns="http://www.openuri.org/">
<ns:Address xmlns:ns="http://www.openuri.org/">
<ns:City xmlns:ns="http://www.openuri.org/">Luxembourg</ns:City>
<ns:Country xmlns:ns="http://www.openuri.org/">LU</ns:Country>
<ns:Number xmlns:ns="http://www.openuri.org/">2</ns:Number>
<ns:PostCode xmlns:ns="http://www.openuri.org/">1000</ns:PostCode>
<ns:Street xmlns:ns="http://www.openuri.org/">Bld. Royal</ns:Street>
</ns:Address>
<ns:Age xmlns:ns="http://www.openuri.org/">20</ns:Age>
<ns:Name xmlns:ns="http://www.openuri.org/">Dupont</ns:Name>
<ns:FirstNames xmlns:ns="http://www.openuri.org/">
<ns:String xmlns:ns="http://www.openuri.org/">Jean</ns:String>
<ns:String xmlns:ns="http://www.openuri.org/">Jacques</ns:String>
</ns:FirstNames>
</ns:getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
rpc wlw property = RPC/Soap-Encoded
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<getEmployeeResult xmlns:s="http://www.openuri.org/encodedTypes" xsi:type="s:Employee">
<Address xsi:type="s:Address">
<City xsi:type="xsd:string">Luxembourg</City>
<Country xsi:type="xsd:string">LU</Country>
<Number xsi:type="xsd:int">2</Number>
<PostCode xsi:type="xsd:string">1000</PostCode>
<Street xsi:type="xsd:string">Bld. Royal</Street>
</Address>
<Age xsi:type="xsd:int">20</Age>
<Name xsi:type="xsd:string">Dupont</Name>
<FirstNames SOAP-ENC:arrayType="xsd:string[2]" xsi:type="SOAP-ENC:Array">
<String xsi:type="xsd:string">Jean</String>
<String xsi:type="xsd:string">Jacques</String>
</FirstNames>
</getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Message was edited by phcollignon at Aug 27, 2004 2:54 AM

Works only with Workshop

Hi,
I have done some updates which work fine with Workshop, but when I try to deploy the application, I get :
Errors found in E:\upload_RE7\PortalApplication\Portail\WEB-INF\src\com\xxxxxxx\xxxxxx\common\Constants.java:
Error at line 3 column 8:
Description: Package com.bea.p13n.entitlements.common contains no member type of this name.
Line 3 is import com.bea.p13n.entitlements.common.EntitlementConstants;
And i can't find this class in any jar or directory, neither on my local server (which works) nor on my deploiement server...
Can I get a jar which contains this class anywhere?
Greetings.
Edited by herge89 at 04/28/2008 5:18 AM
PS : I'm using WLP 8.1.6
Edited by herge89 at 04/28/2008 8:04 AM

p13n_system.jar under weblogic/p13n/lib/platform/lib/p13n/p13n_system.jar
regards
deepak

Source control with Workshop

What is the best source control solution when working with Workshop?
thanks,
Chad

We use CVSNT as server and Tortoise as Client and these can be integrated very easliy with workshop. Works well..Try out.:-)

Unable to use Garmin Heart Rate Monitor (ANT+) with iOS 8.

I have a new iPhone 6. On my previous iPhone 5 with iOS 7 I used Digifit to track my exercise and monitor my heart rate with a Garmin Heart Rate monitor and never had any problem with it. I use an ANT+ 30-pin transceiver attached with Apple's 30-pin to lightning connector to connect to the Garmin Heart Rate Monitor. Since getting my new iPhone 6, when I try to start an exercise program in Digifit it hangs while trying to connect the the sensors. I handed down my old iPhone 5 to my daughter and tried it with her's, which is now updated to iOS 8, with the same results. Therefore I believe it must be a problem with iOS 8.
Anyone else have similar issues?
I wonder if it is related to the HealthKit bug?
Solutions?
Thanks!

Lanza123 wrote:
I have been advised by apple that although my apple devices have Bluetooth 4 it is better to run with ANT + !!! Can I use ANT + with these new apple devices. The wahoo fitness ANT key
http://uk.wahoofitness.com/devices/wahoo-key.html
that I have been advised to buy I think is for old apple devices ?? Will this fit iphone 6 and IPad air 2 ?
As I've never seen an ANT adapter for a lightning connector, I can't imagine why "apple" would give you that advice. Sounds as if the person you were talking to might not be an athlete? I've heard that people have managed to kind of make the old Wahoo key work with the adapter that Apple sells for using older 30-pin accessories with the newer phones with lightning connectors. It sounds like a mess and a disaster waiting to happen to me. I'm also not sure why you should not use BT. I've found it works fine.
You might want to take a look at Wahoo's RFLKT+:
http://www.wahoofitness.com/devices/rflkt.html
It's not the total answer to your issue but it might help.
Also, see the link I posted above to DC Rainmaker's site. You'll find lots of great information on training gadgets there.
Best of luck.

Clearcase integration with workshop

Hi,
Has anyone done clearcase integration with workshop? Any pointers highly appreciated?
TIA,
Amit

Check out the Visual Studio Source Control Provider at
http://dev2dev.bea.com/codelibrary/code/vsscp.jsp
Josh
Amit Bhutra wrote:
Hi,
Has anyone done clearcase integration with workshop? Any pointers highly appreciated?
TIA,
Amit

Creating Singleton with Workshop

I am trying to create a Singleton with Workshop and am having some difficulties. When I try to add the <singleton-service> element to the weblogic-application.xml deployment descriptor, I get a schema error because the element is not defined in the supplied schema location of http://www.bea.com/ns/weblogic/90/weblogic-application.xsd. If I change the location to http://www.bea.com/ns/weblogic/920/weblogic-application.xsd (note the change from "90" to "920"), then the <singleton-service> element is defined, but this schema has two subelements defined as <singleton-class> and <singleton-uri>. According to the documentation (and oddly enough the comments in the schema itself), these elements should be <class-name> and <name> respectively.
There is a weblogic-application.xsd file located in a eclipse plugins folder under workshop that is the same as the old version without the <singleton-service> element. I am assuming that some eclipse builder uses this schema and may be causing the problem. I tried updating this file, but that just causes eclipse to crash on startup.
Anyone have any ideas on how to get an EAR project with a singleton to build successfully in Workshop?

Hi Vimala,
I tried your example and got the deployment problem as well. I don't think the way you have your schema defined is correct. By putting xmlns:xls="http://www.bea.com/ns/weblogic/90", you are associating all tags that begin with "wls:" with that namespace. By specifying the schemas location for http://www.bea.com/ns/weblogic/920, you are telling it where it can find the "920" schema, but it is never stated where you find the "90" schema. This effectively turns off schema checking for the "90" namespace. By not putting "wls:" in front of singleton-service, you are putting it at the default namespace which is not defined. This all seems to make Eclipse happy because it cannot fully validate the document.
I did find a jar file in the weblogic install that contains the schemas that weblogic uses internally. The jar file is at \beahome\weblogic92\server\lib\schema\weblogic-container-binding.jar. The schema for weblogic-application.xml is in this jar and is different from either the "90" or "920" schemas that is online. I believe this is why there is an error when you try to deploy your app. It must validate against this schema.
I have found as long as I match this schema, I can just leave the schemaLocation out of my weblogic-application.xml file and get it to build and deploy. I do get problems reported by eclipse that I need to define library references because it is needed by dependent projects. I believe this is because internally eclipse has its own copy of the schema which predates the <singleton-service> element. The builder is trying to validate the document against this schema and is failing because of the <singleton-service> element, so it cannot find the <library-ref> elements that are in the document. I did not get the same problem with your example application and I haven't figured out why yet. Funny thing, I can make a change to some other file in the project and save and all the reported problems disappear.
I believe using this work-around, I am able to get a good EAR file to build and deploy. It just seems that after I deploy and define my singleton using the admin console that nothing happens. I get no indications that the singleton is working or not in the logs. This did cause me to try a little experiment in that I configured a singleton service using the admin console to a singleton that did not exist. It acts identically to the one that did exist. No warnings or errors at all. I would hope that if I configured a singleton that I would get an error if weblogic could not start it.
Thanks for your efforts. Let me know if you find out anything else,
Jeff

Creating a WebService with Workshop on NT and deploying to UNIX

Are there any problems with a webservice (created with Workshop on NT) being deployed(
as an ear file) on a WL 7.0 instance? Does the instance have to be a Workshop
type domain or not?

Hello Ron,
The EAR file generated on a Win NT machine, can be deployed on a Workshop
enabled server running on a UNIX machine.
Please refer to the link provided by Anurag for steps on Workshop enabling a
WebLogic Domain.
http://e-docs/workshop/docs70/help/guide/howdoi/howWLW-enableExistingWLSDoma
in.html
For information on supported platform please refer to the following URL.
http://e-docs/platform/docs70/support/index.html
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Anurag Pareek" <[email protected]> wrote in message
news:[email protected]..
Ron,
A Workshop webservice EAR file should only be deployed on a Workshopenabled
domain.
Please refer the Workshop docs for 'How to Workshop enable an existing
WebLogic Server domain', or 'How to create a new Workshop domain'.
Let me know if you have further questions.
Thanks,
Anurag
"Ron" <[email protected]> wrote in message
news:3e8d9480$[email protected]..
Are there any problems with a webservice (created with Workshop on NT)being deployed(
as an ear file) on a WL 7.0 instance? Does the instance have to be aWorkshop
type domain or not?

Experience with workshop and ant

Are you using workshop? Are you using ANT? What techniques are you using
for build automatiion? Is is possible to build the project and EAR file
from the command line? How?

Carl,
Workshop provided a command line utility named wlwbuild which allows you to
build the applications and generate the EAR file from the command line.
Please refer to the following document for more information on this
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/reference/commands/cmdWlwBuild.html
Hope this helps.
Regards,
Raj Alagumalai
Backline Workshop Support
You can now "AskBEA" Customer Support questions on the web and get immediate
responses. "AskBEA" is available on http://www.bea.com/support/index.html
"Carl" <[email protected]> wrote in message news:[email protected]..
Are you using workshop? Are you using ANT? What techniques are you using
for build automatiion? Is is possible to build the project and EAR file
from the command line? How?

Using Ant with Oracle

I am trying to create tables using Ant build scripts for deployment purposes. I am able to create the schema and the sequences. It seems to be able to create tables except for triggers. I cannot create triggers after creating the tables. Ant displays an error whenever it reaches the part of a script which involves the trigger part. I am using the Oracle JDBC thin driver with Ant. Am I missing any files that should be included to support triggers? Is there a work-aorund? I appreciate the help...
Thanks!

First of all, for me, this is a complete wrong approach. You should just issue a "drop table <your_tablename>;" and then look if it succeded or not. You can catch the exception and handle it, so the build will not fail.
If you really want do it with PL/SQL, then never do it the way you have tried to do it. Read the net about SQL injection.
Remember, dbms_output will write to an output buffer on the server, not on your client. The client had to read from the buffer.
set serveroutput on is a SQL*Plus command, it will fail if not issued there.
It would probably make sense to return a value, indicating if the command succeeded or not. So you could code something like:
SQL> get t
1 create or replace function sidd ( p_tablename in varchar2 ) return varchar2 as
2 begin
3    for rec in ( select table_name
4                 from   user_tables
5                 where table_name = p_tablename
6               ) loop
7      begin
8        execute immediate 'drop table ' || rec.table_name;
9        dbms_output.put_line( 'table ' || rec.table_name || ' dropped.' );
10        return 'SUCCEEDED';
11      exception
12        when others then
13          dbms_output.put_line( 'table ' || rec.table_name || ' coud not be dropped.' );
14          return 'FAILED';
15      end;
16    end loop;
17    return 'FAILED';
18* end;
SQL> /
Function created.
SQL> exec :ret := sidd ( 'my_t1' );
PL/SQL procedure successfully completed.
RET
FAILED
SQL> exec :ret := sidd ( 'MY_T1' );
table MY_T1 dropped.
PL/SQL procedure successfully completed.
RET
SUCCEEDED
SQL>

Using ant with ejbjar

I am trying to specify a manifest file in the <ejbjar> element, and it appears
that weblogic.ejbc is overwriting the manifest (ant does find the MF, but weblogic
seems to be clobbering it)
has anybody run into this before?
thanks

I tried this and it doesn't work. It will include the file Manifest.mf in
the jar along with the default manifest file MANIFEST.MF. If you try to use
the support tag to include a file MANIFEST.MF, an IOException is received.
Has anybody found a way to get ejbjar to use a custom manifest file?
"Nils Winkler" <[email protected]> wrote in message
news:[email protected]..
I'm using pretty much the same combination, and it works just fine.
Here's what I'm doing:
<ejbjar srcdir="${build}"
descriptordir="${dd}"
destdir="${dist}">
<support dir="">
<include name="META-INF/Manifest.mf"/>
</support>

<weblogic destdir="${dist}"
newCMP="true"
compiler="jikes"
args="-g">
<classpath>
[snip...]
</classpath>
</weblogic>

<include name="**/*-ejb-jar.xml" />
<exclude name="**/*weblogic*.xml" />
</ejbjar>
As you can see, I add the manifest file using the support nested tag.
The manifest file is on my harddisk, in a directory called "META-INF",
which is in the project's main directory.
Hope that helps,
Nils
john wrote:
I am using 6.1 with sp1, and version 1.4.1 of ant
Rob Woollen <[email protected]> wrote:
Make sure that you are running WLS 6.1 (I believe earlier versions will
clobber the
manifest.)
-- Rob
john wrote:
I am trying to specify a manifest file in the <ejbjar> element, andit appears
that weblogic.ejbc is overwriting the manifest (ant does find the MF,but weblogic
seems to be clobbering it)
has anybody run into this before?
thanks
============================
[email protected]

Problem with WorkShop 3.2 when lanching tomcat

hi!I met a problem with debugging projects in WorkShop.
I'm using tomcat 5.5.17 in WorkShop studio 3.2.All my server configurations are default!When debugging,I just right clicked on the project and chose "debug on server",then tomcat lanched.During that time,something weird happened.I found my project was deployed twice,and I also found that one was deployed as context "dms"(project's directory name),another as context "web"(project's real context).
I tried all means to solve this problem.Finally I got one.I set two attributes of host tag to false from server.xml,deployOnStartup and autoDeploy.It works.But I don't think it is the best way.so my questions is: is this a workshop deploy bug?
I guess it is.This is what I found from tomcat document.I think it may help us to slove this problem.
"When using automatic deployment, the docBase defined by an XML Context file should be outside of the appBase directory. If this is not the case difficulties may be experienced deploying the web application or the application may be deployed twice.
Finally, note that if you are defining contexts explicitly, you should probably turn off automatic application deployment. Otherwise, your context will be deployed twice each, and that may cause problems for your app. "
Maybe workshop should use the web context name as project directory name when deploying and do not define the context explicitly in server.xml.

hi, I just do the same thing as you do!The problem still exists!
if you go to Tomcat Web Application Manager page and have a look at the applications you deployed. You will find your project is deployed twice with two different context(context root and project directory name as context root).
note:if you don't have access to the manager page,you can try the following:
-edit the settings for the server
-find 'Run modules directly from the workspace(do not modify the Tomcat installation)' setting and uncheck the checkbox before it
-then save your changes.
Doing this you can deploy your project directly to the appbase of your tomcat server directory.Then you will have access to the manager page with the url "http://localhost:8080/manager/html".
Also you may take a closer look at the output of your workshop console,you will find some output messages duplicated.
This problem originally starts from workshop 3.1.There is no such issue before 3.0 and lower versions.
Workshop studio was once an fatastic tool.But after integrated with WTP things have been changed.The biggest trouble is it costs too much memory.and some import features such as AJAX support,javascript debugger aren't available to us.I feel a little disappointed.:(
Hope you guys will fix those defects.
Regards!

Cannot use Spring 2.0 final with Workshop Studio 3.2_569

It seems to be impossible to use Spring 2.0 final with the latest Studio. When attempting to define an alternate Spring library (the Studio download is still a CR release), you'll receive an error dialog complaining about a missing OJB jar file from the Spring distribution.
This jar file is missing, but on purpose--it appears that with the 2.0 final release, support for Apache OJB was removed from the main Spring distribution and moved to the Spring modules project.
Any chance we'll get a Studio update to resolve this issue, or provide a final Spring 2.0 version download within Workshop?

The BEA Workshop release 3.2 & 3.2.1 (build 569 & 589 respectively), does not bundle Spring 2.0 final and is also not aware of this release.
However, this should not stop you from manually importing the Spring 2.0 libraries into Workshop.
Preferences | Workshop Studio Facet Libraries | Spring Library is used by the "New Web app" and "Project Facet" wizard to import the libraries on creation. Instead you can manually copy/overwrite Spring 2.0 libraries in your existing project.We will keep you posted on the Spring 2.0 support release.

Ant with jDeveloper, reading the environment

I should like to use Ant to build and deploy our J2EE applications.
The main reason is to get better control of what's put inside the WAR and EAR files eg. correct application.xml/orion-application.xml, correct property-files which might exist in different versions for development, test, production etc.
The best solution is perhaps to use standalone Ant, but since we use jDeveloper we'll try to use ant from jdev 903.
To control the behaviour of Ant I was planning to read the environment in the build script.
When running in jDev, I have problems with reading the environmet settings, like:
<property environment="env" />
<property name="oc4j.home" value="${env.OC4J_HOME}"/>
Anyone that has a solution?
thanks, Trond R.

Trond,
One way to handle this situation is to put all of your developer properties in a separate properties file, then load this file using the file attribute of the Ant property task. For example, you could create a file named build.properties, which contains the following line:
oc4j.home = c:\oc4j
Then, in your Ant buildfile, use:
<property file="build.properties"/>
This allows the developer to customize the build.properties file for their specific machine, but still use the standard build.xml file from the source control.
Using this mechanism, the developer can also override properties on the Ant command line for a specific build using the -D option. For example,
ant -Doc4j.home=d:\oc4j
This would override the value in the build.properties file for this build. You can specify Ant command line options in JDeveloper using the Ant panel under Project Properties.
Using a properties file instead of environment variables makes your Ant buildfile more portable. It can be used within an IDE such as JDeveloper, and can be run on any platform.
-Matt Hawkins, JDeveloper Team

Ant with Workshop

Similar Messages

Maybe you are looking for