No option to create toplink-deployment-descriptor

I originally started a TopLink project that allowed me to generate a toplink-deployment-descriptor.xml by right clicking on the project's mapping file.
However, this option has recently been replaced with an option to generate toplink-ejb-jar.xml instead. There is no longer an option for toplink-deployment-descriptor.xml, yet the project will bomb if it's not there...
Apparently the two files are the same thing (although one goes to META-INF and the other goes to a subfolder under META-INF) because if I rename toplink-ejb-jar.xml to toplink-deployment-descriptor.xml, the project runs fine.
Can anyone explain why this is? I did add an EJB to the project (an MDB)... could that have messed something up?

Adding an ejb, hence presence of an ejb-jar.xml, to the jdev project will cause this.
This is a known issue and will be addressed in future releases.
Hope this helps.

Similar Messages

Haven't got submenu [generate toplink-deployment-descriptor.xml]

followed steps in the tutorial : Building a Simple JSF and TopLink App in JDeveloper 10.1.3 Preview
http://www.oracle.com/technology/products/jdev/101/howtos/jsftoplink/index.html
but at the step 8 ( Now that you've generated your TopLink Class and initial mappings, you'll want to generate the TopLink Deployment Descriptor. Locate the TopLink Mapping node and right click "Generate toplink-deployment-descriptor.xml")
i can't see the submenu [generate toplink-deployment-descriptor.xml]
please help me
thanks

and at TopLink node have 2 file : sessions.xml and "TopLink Mapping"
when right-click on "TopLink Mapping" see 3 sub-menu
+Add or remove Descriptor
Generate Mapping Status Report
Create Data Control
Help me get the sub-menu :Generate toplink-deployment-descriptor.xml ???
thanks

How to create the deployment descriptor with the sun application server

I have packaged my .war and ejb-jar files. I go to autodeploy and it says i need a deployment descriptor?

this is actually an example .ear file that i am trying to run. When i create the client with the deploytool that comes with suns application server i get
C:\appclient>appclient -client swe645-appClient.jar
Caught an unexpected exception!
javax.naming.NameNotFoundException: EditEmpBean not found
        at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.
java:185)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.ja
va:157)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialCont
extProviderImpl.java:101)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(Reflecti
veTie.java:123)
        at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tchToServant(CorbaServerRequestDispatcherImpl.java:648)
        at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tch(CorbaServerRequestDispatcherImpl.java:192)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
Request(CorbaMessageMediatorImpl.java:1709)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:1569)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(C
orbaMessageMediatorImpl.java:951)
        at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.call
back(RequestMessage_1_2.java:181)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:721)
        at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatc
h(SocketOrChannelConnectionImpl.java:473)
        at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(
SocketOrChannelConnectionImpl.java:1262)
        at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.
run(ThreadPoolImpl.java:409)

XML Deployment Descriptor question

I am upgrading from WebLogic 4.5.1 to WebLogic 5.1 on Solaris 2.6. I
have several entity beans. I created XML deployment descriptors by
running the DDConverter, then splicing the resulting files together (I
had several entity beans in one directory). I've gotten past all the
problems except this last one. I get the following errors from ejbc
when I try to compile:
ERROR: Error from ejbc: Bean provided to WebLogic RDBMS CMP system is
invalid.
Please examine the following exceptions for specific problems:
0: An unknown error occurred while parsing the Weblogic CMP RDBMS
deployment descriptor. Check that the deployment descriptor contains
well-formed and valid XML.
I've checked the weblogic-cmp-rdbms-jar.xml file, compared it to the
examples, and can't find anything wrong with it. However, the WebLogic
examples don't have an example with multiple entity beans in a jar (can
this be done?). Here is the resulting xml file:
<!DOCTYPE weblogic-rdbms-bean PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN"
"http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd">
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Address</table-name>
<attribute-map>
<object-link>
<bean-field>entity</bean-field>
<dbms-column>Entity</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>File_Cabinet</table-name>
<attribute-map>
<object-link>
<bean-field>folderContainer</bean-field>
<dbms-column>Folder_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>maxCapacity</bean-field>
<dbms-column>Max_Capacity</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByHomeDomain</method-name>
<method-params>
<method-param>Long</method-param>
</method-params>
<finder-query><![CDATA[(= homeDomain $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Folder</table-name>
<attribute-map>
<object-link>
<bean-field>documentContainer</bean-field>
<dbms-column>Document_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>fileCabinet</bean-field>
<dbms-column>File_Cabinet</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Origination_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>displayable</bean-field>
<dbms-column>Displayable</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByName</method-name>
<method-params>
<method-param>String</method-param>
</method-params>
<finder-query><![CDATA[(= name $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package</table-name>
<attribute-map>
<object-link>
<bean-field>forwardIndicator</bean-field>
<dbms-column>Forward_Indicator</dbms-column>
</object-link>
<object-link>
<bean-field>archiveFlag</bean-field>
<dbms-column>Archive_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>beenReadFlag</bean-field>
<dbms-column>Been_Read_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>deleteTimestamp</bean-field>
<dbms-column>Delete_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>sentBy</bean-field>
<dbms-column>Sent_By</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>patientName</bean-field>
<dbms-column>Patient_Name</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>folderName</bean-field>
<dbms-column>Folder_name</dbms-column>
</object-link>
<object-link>
<bean-field>importanceLevel</bean-field>
<dbms-column>Importance_Level</dbms-column>
</object-link>
<object-link>
<bean-field>creationTimestamp</bean-field>
<dbms-column>Creation_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentTimestamp</bean-field>
<dbms-column>Sent_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentOnBehalfOf</bean-field>
<dbms-column>Sent_On_Behalf_Of</dbms-column>
</object-link>
<object-link>
<bean-field>sentToAddrContainer</bean-field>
<dbms-column>Sent_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>ccToAddrContainer</bean-field>
<dbms-column>CC_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>subject</bean-field>
<dbms-column>Subject</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>readBy</bean-field>
<dbms-column>Read_By</dbms-column>
</object-link>
<object-link>
<bean-field>modifiedTimestamp</bean-field>
<dbms-column>Modified_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>readTimestamp</bean-field>
<dbms-column>Read_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>packageSize</bean-field>
<dbms-column>Package_Size</dbms-column>
</object-link>
<object-link>
<bean-field>creator</bean-field>
<dbms-column>Creator</dbms-column>
</object-link>
<object-link>
<bean-field>lastModifier</bean-field>
<dbms-column>Last_Modifier</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package_Spec</table-name>
<attribute-map>
<object-link>
<bean-field>templateContainer</bean-field>
<dbms-column>Template_Container</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>destinationAddrContainer</bean-field>
<dbms-column>Destination_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>serviceContainer</bean-field>
<dbms-column>Service_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service</table-name>
<attribute-map>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>destAddrContainer</bean-field>
<dbms-column>Dest_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Default_Doc</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Doc_Template</table-name>
<attribute-map>
<object-link>
<bean-field>dtdOid</bean-field>
<dbms-column>DTD_OID</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>viewStyleSheetOid</bean-field>
<dbms-column>View_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>defaultDocOid</bean-field>
<dbms-column>Default_Doc_OID</dbms-column>
</object-link>
<object-link>
<bean-field>editStyleSheetOid</bean-field>
<dbms-column>Edit_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Dtd</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Stylesheet</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
Have Fun!
Lea Anne Troeger
Software Engineer
Telesynthesis, Inc.
[email protected]

There is one pool per RA (ra.xml/weblogic-ra.xml). One way to get almost what I think you
          are after is to use the <ra-link-ref> facility in WLS 6.1.
          HTH.
          YiQing Yang wrote:
          > Hi there,
          >
          > I have a question about connector. In weblogic-ra.xml Deployment Descriptor, you
          > define the parameters for connection factory and connection pool. Can you only
          > define one connection factory and connection pool or you can define more than
          > one? In other words, for each deployed connector, can it have more than one connection
          > pool?
          > Your help is appreciated.
          >
          > Thanks,
          >
          > YiQing Yang
          Tom Mitchell
          [email protected]
          Very Current Beverly, MA Weather
          http://www.tom.org:8080

How to edit deployment descriptor in weblogic 9.0?

Hi ,
I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
But I'm not sure how the same can be done in weblogic 9.0.
Please guide me..!!! its urgent...
Thanks,
Smita

If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Deployment descriptor Using weblogic Builder

Hi
I am new to Ejb,
So kindly help me. can we create Deployment Descriptor from CMP bean,using Weblogic Builder.
Thanks
Satya
Edited by: satya22 on Dec 11, 2007 10:37 AM

satya22 wrote:
Hi
I am new to Ejb,Please let me know can we create an Deployment Descriptor
Using Weblogic Builder for an CMP Bean
ThanksHow many things are wrong here, hmmm.
1. Your subject line is useless
2. You posted in the wrong forum
3. You posted about an unrelated technology
4. You didn't make any attempt to do the task yourself
5. You probably haven't searched for an answer on Google
....did I miss anything?

About deployment descriptors

Hi all,
i am totally new to ejb, OAS 10.1.3.1 and jdeveloper 10.1.3.3. just i try to deploy a simple stateless session bean application in OAS. i am trying to create the deployment descriptor files through jdeveloper. what r the descriptor file(xml) i need to create. and give me the difference of orion-application.xml, orion-application-client.xml, orion-ejb-jar.xml, ejb-jar.xml
thanks & regards

Hello,
You probably made a mistake regarding the correct forum. This is the Forms forum.
Francois

Please Help With toplink deployment

Hello
I have a simple j2ee application that runs great in jdeveloper but bombs when I deploy it to my OAS server.
JDev Version 10.1.2
OAS 10.1.2
Technologies used
Struts, toplink
I have 1 table I mapped with toplink, I have a toplink-deployment-descriptor.xml, sessions.xml and a TopLink Mappings.
I have a struts action called kicker.
In kicker I do the following:
<code>
oracle.toplink.tools.sessionconfiguration.XMLLoader xmlLoader = new oracle.toplink.tools.sessionconfiguration.XMLLoader("META-INF/sessions.xml");
oracle.toplink.tools.sessionmanagement.SessionManager sessionManager = oracle.toplink.tools.sessionmanagement.SessionManager.getManager();
DatabaseSession session = (DatabaseSession)sessionManager.getSession(xmlLoader, "default", Thread.currentThread().getContextClassLoader());
Vector objects = session.readAllObjects(t3.model.NibuSalaryWorksheets.class);
System.out.println(objects.size());
request.getSession().setAttribute("results",objects);
return mapping.findForward("success");
</code>
Then in a jsp page I iterate over the results collection and print it out.
When I try to deploy this it blows up on the server with the following error :
Local Exception Stack:
Exception [TOPLINK-6007] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.QueryException
Exception Description: Missing descriptor for [class t3.model.NibuSalaryWorksheets].
Query: ReadAllQuery(t3.model.NibuSalaryWorksheets)
Can someone please help me, I am desparate to use toplink over ejb's but I can't get it to run on the server.
thanks
troy

Seems to be some kind of classloader issue.
You can check if the session has a descriptor for the class by calling,
session.getDescriptor(Class.forName("t3.model.NibuSalaryWorksheets"));
It is most likely that the class is on the classpath twice.
Instead of loading the sessions.xml with the thread class loader you could try using the classes class loader.
i.e.
DatabaseSession session = (DatabaseSession)sessionManager.getSession(xmlLoader, "default", t3.model.NibuSalaryWorksheets.class.getClassLoader());

Custom deployment descriptor

Hi there
We are in the process of deploying our standard J2EE EAR file to
WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
web.xml)
I have some doubts about resources mapping and I'd like to get some help
from experienced WL users.
Basically our EAR file is composed of an EJB module and a WEB module.
Each module declares some references such as:
WEB.XML snippet
<resource-ref>
<description>DataSource for partition 'default'</description>
<res-ref-name>jdbc/Datasource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Now the questions:
1) Is there a way to map the resources during the deployment, using the
console? This is the way followed by WebSphere and Oracle AS, for
example. If this is not possible, should I provide a Deployment Plan for
that EAR file? I tried to provide the xml Deployment Plan generated by
weblogic.PlanGenerator utility together with the EAR file while
deploying the app, but no luck. It seems the Deployment Plan should be
provided in a jar file. Is that correct?
2) If the previous options are not possible, how can I create the custom
deployment descriptor? Is there an "Assembly Tool" that imports the
standard EAR and then export the custom EAR file with the custom
deployment descriptors correctly generated?
Thank you a lot in advance.

A deployment plan is external to the ear/jar file.
It is probably easiest to deploy the application with the console, and then
use the console to change the values you want. It will automatically
generate a deployment plan for you.
"Quasar" <[email protected]> wrote in message
news:[email protected]..
Hi there
We are in the process of deploying our standard J2EE EAR file to
WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
web.xml)
I have some doubts about resources mapping and I'd like to get some help
from experienced WL users.
Basically our EAR file is composed of an EJB module and a WEB module.
Each module declares some references such as:
WEB.XML snippet
<resource-ref>
<description>DataSource for partition 'default'</description>
<res-ref-name>jdbc/Datasource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Now the questions:
1) Is there a way to map the resources during the deployment, using the
console? This is the way followed by WebSphere and Oracle AS, for
example. If this is not possible, should I provide a Deployment Plan for
that EAR file? I tried to provide the xml Deployment Plan generated by
weblogic.PlanGenerator utility together with the EAR file while
deploying the app, but no luck. It seems the Deployment Plan should be
provided in a jar file. Is that correct?
2) If the previous options are not possible, how can I create the custom
deployment descriptor? Is there an "Assembly Tool" that imports the
standard EAR and then export the custom EAR file with the custom
deployment descriptors correctly generated?
Thank you a lot in advance.

Missing Deployment Descriptor

Hi..
have a little Web-Project (in Eclipse with Sun Application Server 9.1_01) for Persistence i Use Toplink. All work fine, until i change a jsp for example and eclipse do a redeploy. After this Redoploy i got the following error:
[#|2008-03-03T16:33:32.829+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=18;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=dc10582e-b7f2-4c4e-8b24-bd0262149cdf;|StandardWrapperValve[data]: PWC1406: Servlet.service() for servlet data threw exception
Local Exception Stack:
Exception [TOPLINK-6007] (Oracle TopLink Essentials - 2.0.1 (Build b09d-fcs (12/06/2007))): oracle.toplink.essentials.exceptions.QueryException
Exception Description: Missing descriptor for [class dd.entities.Dreminder].
Query: ReadAllQuery(dd.entities.Dreminder)
     at oracle.toplink.essentials.exceptions.QueryException.descriptorIsMissing(QueryException.java:419)
     at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkDescriptor(ObjectLevelReadQuery.java:412)
     at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkPrePrepare(ObjectLevelReadQuery.java:494)
     at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkEarlyReturn(ObjectLevelReadQuery.java:433)
     at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:575)
     at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:692)
     at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:746)
     at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2233)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:952)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:924)
     at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:367)
     at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.getResultList(EJBQueryImpl.java:478)
     at dd.servlets.DataManager.service(DataManager.java:43)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]
I test it in a very ! Simple Program. Just one Servlet and One Entity, her ist my Code. I hope somebody could help me.
Entity:
@Entity
@Table(name="dreminder")
public class Dreminder implements Serializable {
     @Id
     @GeneratedValue
     private int id;
....+ getter & setter
My Servlet:
@PersistenceUnit
     private EntityManagerFactory factory = Persistence.createEntityManagerFactory("default");
     @Override
     protected void service(HttpServletRequest arg0, HttpServletResponse arg1) throws ServletException, IOException {
          EntityManager em = factory.createEntityManager();
          Query query;
          query = em.createNativeQuery("select * from Dreminder", Dreminder.class);
          for (Dreminder reminder:(List<Dreminder>) query.getResultList()) {
               arg1.getWriter().write("ID: " + reminder.getId());
          em.close();
my Persistence.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="default" transaction-type="RESOURCE_LOCAL">
<provider>oracle.toplink.essentials.PersistenceProvider</provider>
<class>dd.entities.Dreminder</class>
<properties>
<property name="toplink.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="toplink.jdbc.url" value="jdbc:derby:C:\DerbyDatabases\dreminder2;create=true"/>
<property name="toplink.jdbc.user" value="admin"/>
<property name="toplink.jdbc.password" value="admin123"/>
<property name="toplink.logging.level" value="INFO"/>
</properties>
</persistence-unit>
</persistence>
thanks for helping !!!
D

...have the first mistake...i really don't know where eclipse has stored the Persistence-Unit name "default", but if i change it in persistence.xml, he get the Factory i thing. But now i have my old Problem: "missing deployment descriptor" (only with eclipse)
Exception:
[#|2008-03-12T16:12:27.954+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=6547fbd4-c661-4d2a-960d-e9cd78ab290d;|StandardWrapperValve[data]: PWC1406: Servlet.service() for servlet data threw exception
Local Exception Stack: Exception [TOPLINK-6007] (Oracle TopLink Essentials - 2.0.1 (Build b09d-fcs (12/06/2007))): oracle.toplink.essentials.exceptions.QueryException
Exception Description: Missing descriptor for [class dd.entities.Dreminder].
Query: ReadAllQuery(dd.entities.Dreminder)
at oracle.toplink.essentials.exceptions.QueryException.descriptorIsMissing(QueryException.java:419)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkDescriptor(ObjectLevelReadQuery.java:412)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkPrePrepare(ObjectLevelReadQuery.java:494)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.checkEarlyReturn(ObjectLevelReadQuery.java:433)
at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:575)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:692)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:746)
at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2233)
at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:952)
at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:924)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:367)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.getResultList(EJBQueryImpl.java:478)
at dd.servlets.DataManager.getData(DataManager.java:107)
at dd.servlets.DataManager.service(DataManager.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]

About EJB deployment descriptor

Hello. I am developing EJB3 with glassfish and weblogic 10. I know I can use annotations to simplify
deployment without using ejb-jar.xml , sun-ejb-jar.xml, weblogic-ejb-jar.xml. However, I do want to know
how to write these files correctly because they have higher priority when used.
Somebody may give me a template about writing these files? (ejb 3 specification, for ejb2, I can
use xdoclet to generate them).Thanks a lot.

Hi Martin,
you're are right, XDoclet support for OC4J is lacking the most important stuff. In my case I needed explicit mapping of CMR-fields. Of course, manually editing orion-ejb-jar.xml either by using a text editor or JDeveloper is no option at all.
So I've added support for explicit CMR-mapping to the OC4J XDoclet templates. It works but wasn't fun to do as Oracle's documentation of CMR-mapping is highly inconsistent (e.g. text, figures, and example code are not in sync).
As I've done this as part of a services contract, I cannot easily publish the results. I'll ask my client and let you know.
Anyway, orion-ejb-jar.xml will be obsolete by default in OC4J 10.x as Oracle switches to Toplink as the default persistence manager. So again, XDoclet support is needed for generating the Toplink-specific deployment descriptor.
I'd really appreciate Oracle to provide OC4J-specific XDoclet enhancements. This would help OC4J in gaining wider acceptance.
Stefan

Creating and deploying ejb 3.0 session bean with annotated pojo

I try to create and deploy a EJB 3.0 stateless session bean (and associated webservice) with the following steps:
1) Create Interface "Repository"
package de.xxx.config;
import java.rmi.Remote;
import java.rmi.RemoteException;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public interface Repository extends Remote {
     @WebMethod(operationName = "findCampaignByChannel")
     public String findCampaignByChannel(String channelName) throws RemoteException;
2) create dummy "RepositoryImpl"
package de.xxx.config;
import java.rmi.RemoteException;
import javax.ejb.Stateless;
import javax.jws.WebService;
@WebService(endpointInterface="de.xxx.config.Repository")
@Stateless
public class RepositoryImpl implements Repository {
     public String findCampaignByChannel(String channelName) throws RemoteException {
          return null;
3) The two class files are packaged into a jar without any further descriptors
4) The jar is deployed with admin_client into the oc4j instance using the commands:
-deploy -file <jarfile> -deploymentName <name>
Result:
An ear was constructed and started but no session bean or webservice is found (using the console). But according to to the docs a jar file without a ejb-jar.xml should be recognized as a EJB 3.0 ejb-jar file and the necessary steps to create session bean and expose webservice should be done automatically.
My question:
Which step do i miss here ?
Tools used:
Eclipse 3.2 for the jar file
SoaSuite 10.1.3.1 for oc4j

another strange problem.
i have an APplication server added ( JBOSS ).
when i create deployment profile (EAR ) application server is showed in the ComboBox .
But when i create Java Test Client for some EJB and when i check " Connect Remote Application server" there is 2 comboboxes
J2EE Application
App Server Connection.
first combo is ok there is EJB applicaiton
Secound is empty .. but i Have App Server.
Another think is that when i create EJB 3.0 its BAD to see J2EE app it must be J EE 5 app or just Java EE app

Challenges in deployment descriptors

We currently have an EJB (called CD) that is contacted "remotely" by a web service
(called CA) for some processing. The two (CD and CA) are deployed on different
WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar) whereas
CA is part of an EAR file and is deployed as an application. We ran into the necessity
of making CD as part of EAR (much like CA). However, as part of the CA package,
there is currently an initialization class (we're using a servlet) that saves
some entries in JNDI for both CA and CD. We want to mimic the functionality of
that class in CD when we create the ear for it.
I just ran into some settings that could be made in the weblogic-application.xml
deployment descriptor as follows:
<startup-class>startup class name</startup-class>
We're hoping this can help us mimic CA's init process. However, we need to pass
that class some parameters upon load (which in the case of CA was done by using
the <init-param> in its web.xml). We came across the following tag:
<application-param>
     <param-name>someparam</param-name>
     </param-value>somevalue</param-value>
</application-param
However, we have the following questions:
1. How do we make the startup class fetch those param values at load time? (for
CA, the servlet was using the appPropLoc = getInitParameter("someparam") in its
init method
2. We needed to perform the remote lookup from CA to CD. Would enclosing CD in
an EAR affect our ability to do so? If so, then how do we go about doing that?
Thanks much,
Sami

Hi sami,
Enclosing the EJB (CD) in an EAR file is not going to stop you from Remotely accessing
it.
As CD and CA are in different application package and moreover in different JVM,
you have to package the interface classes as client jar with in CA for type casting.
Joe
"sami titi" <[email protected]> wrote:
>
We have resolved the first part of this problem by using a startup servlet
much
like we do in CA. However, we still face the issue of question number
2 below.
Please provide some feedback.
Thanks,
Samir
"sami titi" <[email protected]> wrote:
We currently have an EJB (called CD) that is contacted "remotely" by
a web service
(called CA) for some processing. The two (CD and CA) are deployed on
different
WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar)
whereas
CA is part of an EAR file and is deployed as an application. We raninto
the necessity
of making CD as part of EAR (much like CA). However, as part of the
CA package,
there is currently an initialization class (we're using a servlet) that
saves
some entries in JNDI for both CA and CD. We want to mimic the functionality
of
that class in CD when we create the ear for it.
I just ran into some settings that could be made in the weblogic-application.xml
deployment descriptor as follows:
<startup-class>startup class name</startup-class>
We're hoping this can help us mimic CA's init process. However, weneed
to pass
that class some parameters upon load (which in the case of CA was done
by using
the <init-param> in its web.xml). We came across the following tag:
<application-param>
     <param-name>someparam</param-name>
     </param-value>somevalue</param-value>
</application-param
However, we have the following questions:
1. How do we make the startup class fetch those param values at load
time? (for
CA, the servlet was using the appPropLoc = getInitParameter("someparam")
in its
init method
2. We needed to perform the remote lookup from CA to CD. Would enclosing
CD in
an EAR affect our ability to do so? If so, then how do we go about doing
that?
Thanks much,
Sami

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

1) Since JSTL libraries are provided as Web application libraries, they must be deployed before the Web application that is using JSTL functionality is deployed. The libraries can be deployed using the Administration Console or with the command-line weblogic.Deployer tool.
Here’s an example of deploying a JSTL 1.2 library using the weblogic.Deployer command-line:
java weblogic.Deployer -adminurl t3://localhost:7001
-user weblogic -password weblogic
-deploy -library
d:/beahome/wlserver_10.3/common/deployable-libraries/jstl-1.2.war
This command deploys the JSTL 1.2 library using the default library-name, specification-version and implementation-version defined by the MANIFEST.MF in the library.
After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console. This information can also be found in the MANIFEST.MF file of the library WAR file.
For more information on deploying a Web module refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/deployment/deployunits.html
2) To reference a JSF or JSTL library, a standard web application can define a <library-ref> descriptor in the application’s weblogic.xml file. Here is an example:
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2.0</implementation-version>
<exact-match>false</exact-match>
</library-ref>
For more information on referencing a Web application library refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/programming/libraries.html
3) Create a sample JSP in your application and JSP should look as shown below
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<html>
<head>
<title>TestJSTL</title>
</head>
<body>
<c:set var="topic" value="JSTL" />
<c:out value="${topic}" />
</body>
</html>
4) Create WAR and deploy and test.
Edited by: Murali Veligeti on Jul 26, 2012 9:00 AM

How to specify OAS instance in deployment descriptor

Hi
I've got OAS 10.1.3.1.0, where exist home, home1, home2... instances. In JDev I've developed web app. and deployment descriptor for it. How to specify correct instance in depl. descriptor?
Thank you

Sorry, it's still not clear. You have a deployment profile. Now:
Are you right-clicking that profile and saying "deploy to <app server>?" If so, you define the instance when you created the app server connection.
Otherwise, if you're using some other way of deploying (e.g., AS control), you explicitly navigate to the instance and deploy the app from there.
John

No option to create toplink-deployment-descriptor

Similar Messages

Maybe you are looking for