Deployment Descriptor Properties: partnerLinkBinding deployment descriptor
Hi
The propertie location of sections of the partnerLinkBinding deployment descriptor does not work. In particullary I can set the location partnerLinkBinding
deployment descriptor but I cannot modify it by BPEL console once I have deployed.
Edited by: user1758242 on 20-lug-2009 4.20
Hi,
<?xml version = "1.0" encoding = "UTF-8" ?>
<process name="Descriptor_Test"
targetNamespace="http://xmlns.ora"
xmlns="http://schemas.xmlsoap."
xmlns:orcl="http://tip.pc.services.functions.ExtFunc">
<partnerLinks>
<partnerLink name="client" partnerLinkType="client:Descriptor_Test"
myRole="Descriptor_TestProvider"
partnerRole="Descriptor_TestRequester"/>
</partnerLinks>
<variables>
<variable name="inputVariable"
messageType="client:Descriptor_TestRequestMessage"/>
<variable name="outputVariable"
messageType="client:Descriptor_TestResponseMessage"/>
<variable name="Variable_1" type="xsd:string"/>
</variables>
<sequence name="main">
<receive name="receiveInput" partnerLink="client"
portType="client:Descriptor_Test" operation="initiate"
variable="inputVariable" createInstance="yes"/>
<assign name="Assign_1">
<copy>
<from expression="concat('xxxxxx','xxxxxx')"/>
<to variable="Variable_1"/>
</copy>
</assign>
<assign name="Assign_2">
<copy>
<from expression="ora:getPreference(ADD)"/>
<to variable="outputVariable" part="payload"
query="/client:Descriptor_TestProcessResponse/client:result"/>
</copy>
</assign>
<invoke name="callbackClient" partnerLink="client"
portType="client:Descriptor_TestCallback" operation="onResult"
inputVariable="outputVariable"/>
</sequence>
</process>
Edited by: user1758242 on 20-lug-2009 5.22
Similar Messages
-
BPEL Sensor Deployment Descriptor Properties Question
When a BPEL process is deployed to the container, several BAM properties are exposed at runtime via the BPEL deployment descriptor (BAM server connection properties). These can be modified via the BPEL Process Manager. The ideal being that when the BPEL process is deployed various places you can change the BAM sensor server properties without a re-compile.
Unfortunately when I tried doing this, it seemed to try to work, but not successfully. When I changed the server settings it tried to access the new server, but with the old (or otherwise invalid) credentials -- even though I updated them. This locked the user account on the BAM server. I also noticed that once the BPEL process ran, the BAM server was continually bombarded with invalid requests (causing the account on the BAM server to lock as fast as it could be unlocked) until the BPEL engine was bounced.
I'm not ruling out something weird in our environment, but has anyone else done this?
Are the settings supposed to be in effect immediately after updating them or does it require a bounce of the BPEL container to properly re-initialize them?I think this was logged as a BPEL console bug. Updating BPEL descriptor for BAM server properties, (a) will not immediately take effect (b) updating BAMserver components have to be done 1 at a time (not 3 BAM params update) (c) BPEL server needs restart after each BAM server property change. Pl log a bug with BPEL server team with Oracle support. Validate the above with 1 property change per BPEL server restart.
-
JNDI environment properties for EJB in deployment descriptor
Is it possible to deploy an EJB on weblogic 6.0 such that the EJBHome
object is bound using JNDI to a different JNDI server such as ldap
server instead of the weblogic server by specifying JNDI env.
properties like PROVIDER_URL, INITIAL_CONTEXT_FACTORY in the
deployment descriptor? That is use the weblogic built-in deployer but
bind the JNDI names to a different JNDI server. For this, can the
EJBHome objects be treated as just RMI (over IIOP) objects and bind
them (stubs of the RMI objects) using the Sun's JNDI service provider.
The goal is that thereafter the Home JNDI names can be looked up by
RMI clients and the interface methods invoked.
Thanks,
... arunMust I put the war and jar files in the same ear ?
oh..ft...my boss is killing me ..
package..repackage...package..repackage..and test ??
Could anybody tell me how to refer a SLSB without put the webApp
and the EjbApp together in an Ear file ??
thanks very much!!!! -
The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing
Hello,
I want to create web service from ejb but everytime I want to do it, I get the following error:
I'm using NWDS 7.2 and JDK 1.6
[004]Deployment aborted
Settings
SDM host : XXX
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anyone tell me why am I getting this error.
Thnx for your help.
Best regards.Hello Decio Junior,
Actually yes, I resolved my problem.
I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
The problem is that my server was using JDK 1.4 and that was the problem.
EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
Check your server JDK Version. It should be JDK 1.5 or higher.
Something else that you should check, in your project properties :
In the Build PATH : Use JDK 1.5
In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
Hope it would help.
If you need more explanations, I'm here
Good luck. -
Deployment Descriptor in Oracle 11g
Hi all,
in oracle 10g i used to create deployment descriptor property in jedeveloper and set value for it,so that i can change the value in the console at run time. Like wise i am not aware how to do the same in the oracle 11g. pls help me to sort this.Hi Kaushik,
Do you mean preference properties which you could set in bpel.xml file and then can access using ora:getPreference() ?
If so, then these properties can be defined now in composite.xml file.
http://tech-learnings.blogspot.com/2010/05/adding-preference-properties-in-11g.html
HTH,
Ketan -
Referencing EJB on remote server AND using deployment descriptor
We're using Weblogic 6.1sp2 under Windows 2000.
We have a web application on server A and several EJBs running on server B -
some of these may in the future be moved to different servers.
We would like to ensure that this only requires reconfiguring the deployment
descriptors.
In our web app, we access the EJB's like this:
AccountHome accHome = (AccountHome) (new
InitialContext()).lookup("java:comp/env/ejb/AccountHome")
- we then map ejb/AccountHome to the JNDI name in the weblogic.xml file in
the web app - the JNDI name will usually (but not always) be the class name
of the implementing class, e.g. system.billing.accounting.AccountHome
However, to make this work when the EJB is on server B, we must put a
jndi.properties file in the server A classpath containing
java.naming.provider.url=t3://server_b:7001/
to point to server B.
Now, this makes ALL JNDI lookups on server A go to server B - this is not
what we want. Especially not in the case where some EJB's move to server C -
B and C may be in separate clusters and will not be clustering the JNDI
tree. Also, other web applications on the server will need to go to
different servers.
Alternatively, we could specify a property set in the InitialContext
constructor with a provider url. But in that case, the mapping from
web.xml/weblogic.xml is apparently not applied - or rather, if we look up
"java:comp/env/ejb/AccountHome", weblogic maps it to
"system.billing.accounting.AccountHome" and then tries to look it up on the
local machine, server A.
If we look up "system.billing.accounting.AccountHome", it does correctly
look it up on the server specified in the provider url and finds the entry.
However, this would mean that we would have to specify the exact jndi name.
In addition, we would have to hard-code the server name for each lookup.
An alternative would be to "copy" the JNDI entries from server B to server A
(or to some other shared, global JNDI registry). But these would need to be
kept in sync - especially since server B is really a cluster, where
different servers may come online at different times and register their EJBs
as clusterable, so the stubs would need to be continously updated.
My best idea is to bypass the whole web.xml/weblogic.xml mapping scheme and
just add our own config file with stuff like
<mappings>
<map entry="java:comp/env/ejb/AccountHome">
<jndi-properties>
java.naming.provider.url=t3://server_b:7001/
java.naming.security.principal=jndiuser
java.naming.security.credentials=mysecretpassword
</jndi.properties>
<jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
</map>
</mappings>
We then need to wrap all the lookups in our own lookup mechanism which first
checks the config file to find any mappings.
However, this seems like reinventing the wheel and will also confuse most
deployment tools etc.
Does anybody have any suggestions where we
1. Don't put a jndi.properties file in the server classpath
2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDI name.
3. Don't hardcode the server names in the application - but potentially
in the deployment descriptor.
4. Can look up different EJB's on different machines
Niels HarremoësThere is an article on dev2dev that may explain what you are seeing...
http://dev2dev.bea.com/articlesnews/discussion/thread.jsp?thread=142
HTH
dwfa
"Niels Ull Harremoës" <[email protected]> wrote in message
news:[email protected]...
It turns out that we can make it work by entering the url of the server in
the weblogic.xml entry - e.g. instead of having
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/AccountHome</ejb-ref-name>
<jndi-name>system.billing.accounting.AccountHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
we enter
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/AccountHome</ejb-ref-name>
<jndi-name>t3://server_b:7001/system.billing.accounting.AccountHome</jndi-na
me>
</ejb-reference-description>
</reference-descriptor>
However, we are unsure on whether this will establish a new JNDIconnection
to server_b on every lookup? And it's not documented anywhere?
Does anybody have any other suggestions?
"Niels Ull Harremoës" <[email protected]> wrote in message
news:[email protected]...
We're using Weblogic 6.1sp2 under Windows 2000.
We have a web application on server A and several EJBs running on serverB -
some of these may in the future be moved to different servers.
We would like to ensure that this only requires reconfiguring thedeployment
descriptors.
In our web app, we access the EJB's like this:
AccountHome accHome = (AccountHome) (new
InitialContext()).lookup("java:comp/env/ejb/AccountHome")
- we then map ejb/AccountHome to the JNDI name in the weblogic.xml file
in
the web app - the JNDI name will usually (but not always) be the classname
of the implementing class, e.g. system.billing.accounting.AccountHome
However, to make this work when the EJB is on server B, we must put a
jndi.properties file in the server A classpath containing
java.naming.provider.url=t3://server_b:7001/
to point to server B.
Now, this makes ALL JNDI lookups on server A go to server B - this is
not
what we want. Especially not in the case where some EJB's move to serverC -
B and C may be in separate clusters and will not be clustering the JNDI
tree. Also, other web applications on the server will need to go to
different servers.
Alternatively, we could specify a property set in the InitialContext
constructor with a provider url. But in that case, the mapping from
web.xml/weblogic.xml is apparently not applied - or rather, if we look
up
"java:comp/env/ejb/AccountHome", weblogic maps it to
"system.billing.accounting.AccountHome" and then tries to look it up onthe
local machine, server A.
If we look up "system.billing.accounting.AccountHome", it does correctly
look it up on the server specified in the provider url and finds theentry.
However, this would mean that we would have to specify the exact jndiname.
In addition, we would have to hard-code the server name for each lookup.
An alternative would be to "copy" the JNDI entries from server B to
server
A
(or to some other shared, global JNDI registry). But these would need tobe
kept in sync - especially since server B is really a cluster, where
different servers may come online at different times and register theirEJBs
as clusterable, so the stubs would need to be continously updated.
My best idea is to bypass the whole web.xml/weblogic.xml mapping schemeand
just add our own config file with stuff like
<mappings>
<map entry="java:comp/env/ejb/AccountHome">
<jndi-properties>
java.naming.provider.url=t3://server_b:7001/
java.naming.security.principal=jndiuser
java.naming.security.credentials=mysecretpassword
</jndi.properties>
<jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
</map>
</mappings>
We then need to wrap all the lookups in our own lookup mechanism whichfirst
checks the config file to find any mappings.
However, this seems like reinventing the wheel and will also confuse
most
deployment tools etc.
Does anybody have any suggestions where we
1. Don't put a jndi.properties file in the server classpath
2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDIname.
3. Don't hardcode the server names in the application - butpotentially
in the deployment descriptor.
4. Can look up different EJB's on different machines
Niels Harremoës -
Deployment Descriptor - run time modification
As EJB spec states that deployment descriptor is for dynamic modification of EJB properties.
I don't understand that once we give these (EJBs) JAR files to customer, how customer can change deployment descriptors which are hidden inside JAR files.
Is there any tool which will open these JARs and modify the deployment descriptors.
Any other comments are appreciated.
I am using BAS 4.5 and JBoss 2.4.4.Greetings,
As EJB spec states that deployment descriptor is for
dynamic modification of EJB properties.Actually, the deployment descriptor allows for "post compile-time customization" of beans by means of the "declarative deployment model"...
IOW, the DD provides information that is to be made available to the bean by its runtime environment (container), which information is provided in between compile-time and runtime. Such information may provide customization data ("Environment References"), make resources available (reference links), and/or provide security information (role references). The bean ("component", actually, since web-tier components now also benefit from deployment descriptors ;), can then get access to this information during it's runtime as required. Typically, this means customization data - which, of course, allow the bean to initialize its state for the application/enterprise in which it runs - though, role-references may be used to fine-grain security authorizations; reference links, however, may be thought of as working in the opposite direction - they are handled transaparently by the container - since, in essence it is the bean that is providing link value.
I don't understand that once we give these (EJBs) JAR
files to customer, how customer can change deployment
descriptors which are hidden inside JAR files.Technically, it is the "bean descriptor", possibly the "assembly (application) descriptor", that is given to the end user (either the application assembler or deployer...), since the deployment descriptor is not created until actual deployment. ;)
Of course, the real issue here is "component customization": the customer does not modify the DD, but rather provides values for the lookups the component is making (which lookups -as well as other details about what's expected from them - are provided to the customer along with the component), during either the assembly and/or deployment phases (each of which may produce their own DD levels).
Is there any tool which will open these JARs and
modify the deployment descriptors.In a manner of speaking... the vendor's deployment tool provides the intended capability.
Any other comments are appreciated.
I am using BAS 4.5 and JBoss 2.4.4.Regards,
Tony "Vee Schade" Cook -
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)
|#] -
BPEL Process Deployment Descriptor needs to be fixed.
I made a simple hello world BPEL Process i made it using Bpel Designer for eclipse. I have BPEL Manager 10.1.3.1.0 version when i build bpel project its gives me following error kindly help me out of this problem.
deployment descriptor format error.
Error when parsing the deployment descriptor "bpel.xml", because "org.apache.xerces.parsers.XML11Configuration"
Fix the deployment descriptor.
here is my ant script
<?xml version="1.0"?>
<project name="SyncHelloWorld" default="main" basedir=".">
<property name="deploy" value="default"/>
<property name="rev" value="1.0"/>
<target name="main">
<bpelc input="${basedir}/bpel.xml"
rev="${rev}"
deploy="${deploy}"
/>
</target>
</project>
Here is my bpel.xml
<?xml version="1.0"?>
<BPELSuitcase>
<BPELProcess id="SyncHelloWorld" src="SyncHelloWorld.bpel">
<configurations/>
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">SyncHelloWorld.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>
Thanks in advance help me out its urgent. I need to move on.IS ESB/BPEL LISTENING on 127.0.0.1:8888 ?
-
Deployment descriptor configuration tool
Hi,
My company delivers a weblogic server based product.
We have the following problem: when we deliver a new version of the product
(basically, a new .ear), we overwrite the previous deployment descriptor of
each EJB, Connector, etc... This means that if our customers need to
remember their previous settings (particularly concerning caches and pools).
Is there a way to merge those descriptors (I really don't see how a program
could decide what's old, new, modified, and so on...) or at least automate
the configuration?
The only solution I see for now is having descriptor templates and creating
an ant script (would work on windows and unix) that would basically do the
following:
. extract the descriptors templates (unear, unjar, unwar, unrar)
. configure the new descriptors using an existing (previous version)
properties file
. replace the descriptors (jar, war, rar, ear)
I realize that this could be a pain to do and maintain, so I wonder if there
is not already a tool for that...
Thank you,
Patrick.
PS: we are still on WLS 6.1 for now...Patrick:
There is a feature in 8.1 called alt-dd that allows you to specify an
alternate DD to the DD's in the EAR and modules. This would allow you to
replace externally without have to over-write.
Additionaly in our next release, code named Diablo (named for a State Park),
we are working on feature in conjunction with JSR88 of J2EE 14 whereby
Descriptor values that are bindables and tunables can be over-ridden by a
Deployment Plan that sits external to the ear.
Cheers
mbg
"Patrick Martin" <[email protected]> wrote in message
news:[email protected]..
Hi,
My company delivers a weblogic server based product.
We have the following problem: when we deliver a new version of theproduct
(basically, a new .ear), we overwrite the previous deployment descriptorof
each EJB, Connector, etc... This means that if our customers need to
remember their previous settings (particularly concerning caches andpools).
>
Is there a way to merge those descriptors (I really don't see how aprogram
could decide what's old, new, modified, and so on...) or at least automate
the configuration?
The only solution I see for now is having descriptor templates andcreating
an ant script (would work on windows and unix) that would basically do the
following:
. extract the descriptors templates (unear, unjar, unwar, unrar)
. configure the new descriptors using an existing (previous version)
properties file
. replace the descriptors (jar, war, rar, ear)
I realize that this could be a pain to do and maintain, so I wonder ifthere
is not already a tool for that...
Thank you,
Patrick.
PS: we are still on WLS 6.1 for now... -
Deployment Descriptor defaults for clustering
If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
Darko Bohinc
Synergy International Limited
www.synergy.co.nz
Darko,
All EJB "homes" are clusterable by default (a request for a home interface can be routed to any server in the cluster).
In the case of stateless session beans, you also achieve load-balancing by default (method calls can be sent to any server in the cluster). Failover is achieved by default only BETWEEN method calls and not DURING method calls. In other words, the stub will retry a method call on another server in the cluster only if the stub is absolutely sure that the method call did not reach the server in the cluster during the first try. If the stub cannot determine this, it will not retry by default and you should eventually get an error. If you would like the server to retry all method calls even if the server failed in the middle of a call, then you need to write your EJB methods to be idempotent (calling any method in the EJB many times with the same parameters should achieve the same result with no side effects such as duplicate inserts in the database etc). You will then have to explicitly set the "stateless-bean-methods-are-idempotent" element in the deployment descriptor for the EJB to let WL know that all methods can be retried without any worries.
Please see the following link for additional information:
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#1046391
Hope this answers your questions.
Giri
"Darko Bohinc" <[email protected]> wrote:
>
>If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
>
>Darko Bohinc
>Synergy International Limited
>www.synergy.co.nz
-
Problem with Missing deployment descriptor [J2EE:160043]
Hi,
I am having a problem deploying an *.ear into weblogic 8.1. I get the error
J2EE:160043]Missing deployment descriptor "META-INF/application.xml" at "C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear"
even though the application.xml file is in the *.ear file. This *.ear file is
built using the following
ant script:
Note: I am integrating a Message Driven EJB with Documentum Content Server
DFC API calls (3rd party jars)
Thanks, Craig
<project name="ejb20-message" default="all" basedir=".">
<!-- set global properties for this build -->
<property environment="env"/>
<property file="../../../examples.properties"/>
<property name="build.compiler" value="${compiler}"/>
<property name="source" value="."/>
<property name="build" value="${source}/build"/>
<property name="dist" value="${source}/dist"/>
<property name="dummy" value="${source}/dummy"/>
<!--
<target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app,
-->
<target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app3"/>
<!-- compile_client"/> -->
<target name="init">
<!-- Create the time stamp -->
<tstamp/>
<!-- Create the build directory structure used by compile
and copy the deployment descriptors into it-->
<mkdir dir="${build}"/>
<mkdir dir="${build}/META-INF"/>
<mkdir dir="${dist}"/>
<copy todir="${build}/META-INF">
<fileset dir="${source}">
<include name="*.xml"/>
<exclude name="build.xml"/>
<exclude name="application.xml"/>
</fileset>
</copy>
<!-- Changed to move application.xml into ${dist}/meta-inf C. Ahtye
<copy todir="${dist}">
<fileset dir="${source}">
<include name="application.xml"/>
</fileset>
</copy>
-->
<copy todir="${dist}/META-INF">
<fileset dir="${source}">
<include name="application.xml"/>
</fileset>
</copy>
<!--<copy todir="${dist}">
<fileset dir="${source}">
<include name="dfc.properties"/>
</fileset>
</copy>-->
</target>
<!-- Compile ejb classes into the build directory (jar preparation) -->
<target name="compile_ejb">
<javac srcdir="${source}" destdir="${build}" includes="DataLoadMgrBean.java"
excludes="DSSCommand.java,GetDSSCommand.java,ImportXMLHelper.java" classpath="dfc.jar"/>
</target>
<!-- Update ejb jar file or create it if it doesn't exist, including XML
deployment descriptors -->
<target name="jar.ejb" depends="compile_ejb">
<jar jarfile="${dist}/ejb20_dataLoadMgr.jar" basedir="${build}" update="yes">
</jar>
</target>
<target name="appc" depends="jar.ejb">
<wlappc debug="${debug}" source="${dist}/ejb20_dataLoadMgr.jar" classpath="dfc.jar"
verbose="true"/>
</target>
<!-- Put the ejb into an ear, to be deployed from the ${apps.dir} dir -->
<target name="ear_app" depends="jar.ejb">
<ear earfile="${apps.dir}/ejb20_dataLoadMgr.ear" appxml="${source}/application.xml">
<!--<fileset dir="${dist}/APP-INF/lib" includes="dfc.jar"/>
<fileset dir="${dist}/APP-INF/lib" includes="dfcbase.jar"/>-->
<fileset dir="${dist}" includes="ejb20_dataLoadMgr.jar"/>
</ear>
</target>
<!-- Need to place dfc.jar, dfcbase.jar, log4j.jar into {source} and then deploy
to {dist} -->
<target name="ear_app3" depends="jar.ejb">
<jar destfile="${apps.dir}/ejb20_dataLoadMgr.ear" basedir="${dist}"/>
</target>
<target name="ear_app2" depends="jar.ejb">
<wlpackage toFile="${apps.dir}/ejb20_dataLoadMgr.ear" srcdir="${dist}" destdir="${dummy}"/>
</target>
<!-- Compile client app into the clientclasses directory -->
<target name="compile_client">
<javac srcdir="${source}" destdir="${client.classes.dir}" includes="Client.java"/>
</target>
<target name="clean">
<delete dir="${build}"/>
</target>
<!-- Run the example -->
<target name="run">
<java classname="examples.ejb20.dataLoadMgr.Client" fork="yes" failonerror="true">
<arg value="t3://localhost:${port}"/>
<classpath>
<pathelement path="${ex.classpath}"/>
</classpath>
</java>
</target>
</project>Can you show me the output of jar tvf
C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear
-- Rob
Craig Ahtye wrote:
Hi,
I am having a problem deploying an *.ear into weblogic 8.1. I get the error
J2EE:160043]Missing deployment descriptor "META-INF/application.xml" at "C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear"
even though the application.xml file is in the *.ear file. This *.ear file is
built using the following
ant script:
Note: I am integrating a Message Driven EJB with Documentum Content Server
DFC API calls (3rd party jars)
Thanks, Craig
<project name="ejb20-message" default="all" basedir=".">
<!-- set global properties for this build -->
<property environment="env"/>
<property file="../../../examples.properties"/>
<property name="build.compiler" value="${compiler}"/>
<property name="source" value="."/>
<property name="build" value="${source}/build"/>
<property name="dist" value="${source}/dist"/>
<property name="dummy" value="${source}/dummy"/>
<!--
<target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app,
-->
<target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app3"/>
<!-- compile_client"/> -->
<target name="init">
<!-- Create the time stamp -->
<tstamp/>
<!-- Create the build directory structure used by compile
and copy the deployment descriptors into it-->
<mkdir dir="${build}"/>
<mkdir dir="${build}/META-INF"/>
<mkdir dir="${dist}"/>
<copy todir="${build}/META-INF">
<fileset dir="${source}">
<include name="*.xml"/>
<exclude name="build.xml"/>
<exclude name="application.xml"/>
</fileset>
</copy>
<!-- Changed to move application.xml into ${dist}/meta-inf C. Ahtye
<copy todir="${dist}">
<fileset dir="${source}">
<include name="application.xml"/>
</fileset>
</copy>
-->
<copy todir="${dist}/META-INF">
<fileset dir="${source}">
<include name="application.xml"/>
</fileset>
</copy>
<!--<copy todir="${dist}">
<fileset dir="${source}">
<include name="dfc.properties"/>
</fileset>
</copy>-->
</target>
<!-- Compile ejb classes into the build directory (jar preparation) -->
<target name="compile_ejb">
<javac srcdir="${source}" destdir="${build}" includes="DataLoadMgrBean.java"
excludes="DSSCommand.java,GetDSSCommand.java,ImportXMLHelper.java" classpath="dfc.jar"/>
</target>
<!-- Update ejb jar file or create it if it doesn't exist, including XML
deployment descriptors -->
<target name="jar.ejb" depends="compile_ejb">
<jar jarfile="${dist}/ejb20_dataLoadMgr.jar" basedir="${build}" update="yes">
</jar>
</target>
<target name="appc" depends="jar.ejb">
<wlappc debug="${debug}" source="${dist}/ejb20_dataLoadMgr.jar" classpath="dfc.jar"
verbose="true"/>
</target>
<!-- Put the ejb into an ear, to be deployed from the ${apps.dir} dir -->
<target name="ear_app" depends="jar.ejb">
<ear earfile="${apps.dir}/ejb20_dataLoadMgr.ear" appxml="${source}/application.xml">
<!--<fileset dir="${dist}/APP-INF/lib" includes="dfc.jar"/>
<fileset dir="${dist}/APP-INF/lib" includes="dfcbase.jar"/>-->
<fileset dir="${dist}" includes="ejb20_dataLoadMgr.jar"/>
</ear>
</target>
<!-- Need to place dfc.jar, dfcbase.jar, log4j.jar into {source} and then deploy
to {dist} -->
<target name="ear_app3" depends="jar.ejb">
<jar destfile="${apps.dir}/ejb20_dataLoadMgr.ear" basedir="${dist}"/>
</target>
<target name="ear_app2" depends="jar.ejb">
<wlpackage toFile="${apps.dir}/ejb20_dataLoadMgr.ear" srcdir="${dist}" destdir="${dummy}"/>
</target>
<!-- Compile client app into the clientclasses directory -->
<target name="compile_client">
<javac srcdir="${source}" destdir="${client.classes.dir}" includes="Client.java"/>
</target>
<target name="clean">
<delete dir="${build}"/>
</target>
<!-- Run the example -->
<target name="run">
<java classname="examples.ejb20.dataLoadMgr.Client" fork="yes" failonerror="true">
<arg value="t3://localhost:${port}"/>
<classpath>
<pathelement path="${ex.classpath}"/>
</classpath>
</java>
</target>
</project> -
Hi,
I have a deployment descriptor for Axis, and I need to convert this into a jaxrpc deployment descriptor.
Here is the wsdd for Axis:
<handler name="securityHandler" type="java:handler.securityHandler"/>
<service name="my-WS-A" provider="java:RPC">
<requestFlow>
<handler type="securityHandler"/>
</requestFlow>
<responseFlow>
<handler type="securityHandler"/>
</responseFlow>
<parameter name="allowedMethods" value="*"/>
<parameter name="className" value="myWSA.MyWSA"/>
</service>
I read something about handlerChains with jaxrpc, is this what I need? If anybody has any advice, I'd be happy to hear it.
Thanks,
Dylan>
I read something about handlerChains with jaxrpc, is
this what I need? If anybody has any advice, I'd be
happy to hear it.Yep. Here's an article that summarizes the handler chains:
http://java.sun.com/webservices/docs/1.5/jaxrpc/jaxrpc-tools.html
You can add a <handlerChains> element to your config.xml file for server or client (if you build server code with wscompile first you need a config.xml), or add it to the jaxrpc-ri.xml file. The element has sub elements of type chain, and you can specify that the chain is for client or server.
Inside the chain you list the handlers and their class names. Optional attributes are SOAP roles for the handler chain, and properties and understood headers for the handlers. These properties and headers are passed into the handler's init(HandlerConfig) method at runtime.
Probably the fastest way to get handler chain help is to send email to the jax-rpc users email list from java.net if you'd like to join the group. More information is here:
https://jax-rpc.dev.java.net/
Cheers,
Bobby -
Anyone please help me solve this error. I am trying to deploy an application on weblogic 12c i am getting an error but the same application gets successfully deployed on weblogic 11g. The error is
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(gsCallbackAdapterLGTX-ejb.jar) An error occurred while reading the deployment descriptor. The error was: Error processing annotations: .
[EJB:015001]Unable to link class com.aep.gridsmart.adapters.lgtx.buslogic.deliver.xform.AdapterTransfomerDeliverSession in Jar /appl/oracle/middleware/WLS/12.1.1.0/user_projects/domains/Gridsmart/servers/ManagedServer1/tmp/_WL_user/gsCallbackAdapterLGTX/34vz4d/gsCallbackAdapterLGTX-ejb.jar : java.lang.NoClassDefFoundError: com/aep/gridsmart/adapter/deliver/CommonAdapterDeliverBeanCotton please let me know what is the mistake i am
doingThe following path does not exist.
C:\Sun\AppServer7\domains\domain1\server1\
applications\j2ee-modules\task_1\WEB-INF\web.xml -
Deployment descriptor error for an EJB 3.0 entity bean module
Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis MaggiorottoHi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto
Maybe you are looking for
-
How do I get the app store app on my phone
I have an iPhone 4. I have updated both the phone and itunes. I do not have the "App Store" app on the phone. With the phone attached to my pc I open iTunes and click on the iPhone tab in the upper right hand corner. I then click on Apps. On the left
-
Looking for a app that will go out and get all my credit card balances.
I am looking for a App that can go on all the web sites for my Credit Cards and download the balance Interest Rate Payment..... Anyone know of a good one?
-
Recovery Problem - Blue Screen error (STOP: 0x00008086)
I am working on a Toshiba Satellite laptop and need to recover back to original state. I do not have Recovery Disks, however, I have followed the Toshiba 'How to' instructions (F8 then select Repair your Computer) it show the Windows progress bar the
-
Ok, so I know you all have heard this before but I do believe my case is rather unique, and quite frustrating. I purchased an iPhone 4 and synced it to the same computer I am using now - created the playlist and used it to sync with phone. Worked gre
-
Hello all. Is there anything special at all to dual-screening mega 180? I Installed everything, the CD. Then I powered it off, plugged my second screen in the secondary VGA plug. While XP was booting, both screens showed - perfectly - the booting sc