Ejb module with dependecies
Hi,
I have an EJB module (a .jar) which has runtime dipendencies with a few other jars I have. How can I put all (EJB and dependencies) in one module (be it jar,ear, war or whatever)?
At the moment I'm unjarring my dependences and then putting all toghether in the final jar, but I hope there's a better way to do that.
The EJB module is then put aside a war in an ear, which is my application.
Can someone help?
Thanks
Put all your jar files inside your ear file, then it should work. You can also put all these jar files in library folder of your application server (if one exists).
Your application.xml will contain only the following parts.
<application>
<module>
<ejb>yourejb.jar</ejb>
</module>
<web>
<web-uri>yourWeb.war</web-uri>
<context-root>/yourWebRoot</context-root>
</web>
</application>
Similar Messages
-
What is the best way to use EJB modules with JAX-WS?
Hi.
I am doing a project that returns EAN13 encoded data to external java clients.
I think I need to use a webservice that send response, a webservice client that send the request, and other project that transforms a data to an EAN encoded data, returns it and store it in MySql database.
It is possible that I need to authenticate users for every request made.
-I have created a EJB module contained into Glassfish for the webservice
-I have created a Common Java project with 3 layers: Entities, bussines and data access layer for mysql database
-I have a project for the webservice client with JAX-WS ( is the best choice? or Would be better JAX-RPC? )
**How would you suggest me create the structure of the project with all the java power?*
**Could you help me with goods tutorial of design patterns about webservices using EJB and the best way for use databases for this kind of projects ( I have heard about JNDI, Hibernate, Session EJB, ... )?*
**Would be better use other EJB module instead of a Common java project that has classes?*
h3. {color:#333399}I shall be pleased with your help{color}Kappy is dead on correct about Bridge Mode as a requirement for the Time Capsule.
Do you know how to check to see if the Time Capsule is configured this way?
Next question.....you really should not try to have two wireless networks....one Arris and another Time Capsule.....unless it is absolutely necessary. Two wireless routers in close proximity can create wireless interference effects that can cause problems with either...or both...networks.
Best to turn off the wireless on one router to keep the chances of wireless interference between routers minimized.
Are both the Arris and Time Capsule providing wireless signals? -
Unable to load the EJB module. DeploymentContext does not contain any EJB.
I'm writing an enterprise application to familiarize myself with Glassfish 3.1.2 and EJB 3.1. I've created several local, stateless beans, and injected one into a JSF managed bean. The ejb and web modules compile fine, but when I launch the application with Glassfish I get the following startup error and the application does not deploy. I don't understand what it means, can someone ellaborate?
SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer prepare method
SEVERE: Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
org.glassfish.deployment.common.DeploymentException: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:166)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:722)My guess is that you deployed an ejb without bean in it. when you have an ejb module, be sure you have at least one bean present.
Are you sure you have implementend some beans? Or did you do this only in the web module?
Try adding an @Stateless bean doing nothing in you ejb module, redeploy and let me know if that works -
How to reference an External Library (Server Side) in a DC-EJB Module ?
Hi:
I start working with hibernate in a DC component, so I create my DC project and EJB module inside. I Make an external library following this
Thanks a lot for your time on this thread.
Rocío.Hi Rocío!
Umm, I don't usually use DC's... I don't know if this will work... you can make an EAR (New Proyect -> J2EE -> Enterpise Application Module), add your EJB Module to the EAR (right click on EJB Project and choose Add to EAR proyect), and you'll find a j2ee-engine file on it, and you can add the reference there.Then deploy the EAR.
I normally do something similar to your issue, I make a EJB calling XI via Java Proxys, and the reference to the XI libs are allocated on the EAR, not on the EJB. This is only for runtime, for compilation you must reference the hibernate jar with an external jar file, as always.
A dirty solution could be this one: open your generated EAR with de-compressor, and copy your hibernate jar on it (at root). This way you'll load hibernate classes at runtime (I know this is an horrible solution, this is only for testing).
As I said before, I'm not used to DCs, so this could be wrong, and be a waste of time... I don't know further...
Good luck
Eneko. -
Med Rec medrec tutorial 10 deployments-- EJB Modules EJB is not shown
This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console. -
Converting existing ejb module project into DC
Hi,
1. I have created a local Ejb Module Project
2. Also a web service is created using that ejb(stateless) && deployed on the server.
3. I want to convert this local ejb module project into DC
4. I have copied everything from local ejb module project(eg.ejb,classes,virtual Interface & web service dif etc) & pasted in the DC structure.
5. While creating web service, it shows me a deployment error, regarding web service name (which is already exists).
6. I can create web service with different name & it works fine,
but I don't want to use different name for web service.
7. Is it possible to again create web service with the same name?
8. Or is there another way for doing this?
Best regards,
NileshHave you tried to undeploy the old project? This should work out.
\-- Vladimir -
Lack of modularity in Projects for EJB module
Problem
For a project you have many enterprise bean components. In JDeveloper, currently, all the information like persistence-type,
resource-reference, etc reside in the ejb-jar.xml which is project specific.
(1) In the real-world, developers work on different modules with small individual work spaces with a small number of
enterprise components and web compoents with a CVS system to manage version of the source code
(2) The developer works on the source and check it in the CVS repository
(3) A packager will take components from the CVS repository and make a build for a customer according to the order
(Build-to-Order approach)
(4) In JDeveloper he might have to make the ejb-jar.xml again which is very cumbersome and timeconsuming
Suggestion
(1) The current system of maintaining ejb-jar.xml in the project is OK
(2) But the information in the ejb-jar xml ABOUT EACH EJB COMPONENT should also be maintained at the EJB component level like
a small ejb-jar.xml file specific to the one and only one component.
(3) Whenever the EJB component id edited, this modular ejb-jar.xml file will be edited too.
(4) Later while making the main ejb-jar xml for deployment, the info in these small modular xml files will be read, the main
project level ejb-jar xml will be prepared.
(5) The main project level ejb-jar.xml can also be prepared when the project is rebuilt (clean/force compile) and all te
small modular files are updated.
With regards
AmitHello,
Yes we do read every OTN message, though we often have some internal discussion before we post a reply.
In your specific situation, you could just break up the EJBs into different projects:
- Each EJB module in a separate project.
- Each EJB project builds a separate EJB JAR.
- When assembling the EAR, pull in as many EJB JAR files as necessary to support the WAR and other pieces.
JDeveloper already has support for the above setup. Starting with JDev 9.0.3, you can also establish dependencies between projects to make the classes built by one project visible to another project's classpath.
For us to implement a complete solution where small ejb-jar.xml files are merged into one large ejb-jar.xml file, we'd like to understand how you'd go about resolving conflicts in elements being merged:
- conflicting <method-permission>
- conflicting <container-transaction>
- conflicting <relationship-role>
- conflicting <env-entry>
- ... a number of other potential conflicts ...
We could do automatic merges when there are no conflicts. For the situations where there are conflicts, can you describe some solutions that you would consider acceptable? -
Hi all ,
We have written a EJB module (Successfully deployed) and that we are using in the Sender comm Channel (file)
**Part of the code
Message msg = (Message) inputModuleData.getPrincipalData();
AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"Entered method process");
if (msg == null) {
throw new ModuleException("No XI Message found");
XMLPayload xp = msg.getDocument();
Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"Retrieve payload document");
if (xp == null) {
throw new ModuleException("XMLPayload not found");
// get Audit message Key for Inbound messages
byte fileContent[] = xp.getContent();
//String fileString = new String(fileContent);
Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"Retrieved payload");
JCO.Client client = null;
client = JCO.createClient("001", // SAP client
"aaaa", // userid
"*****", // password
"EN", // language
"gcrsap.comp.com", // host name
"00"); // system number
// Open the connection
client.connect();
****Part of the code ****
When use the module in adapter , we are getting the error in Communication Channel Monitoring (RWB) " Attempt to process file failed with com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process"
Regards
GoutamAlso, can you check the log files in J2ee engine
you will have the stack trace
regards
krishna -
How to call RFC using EJB module.
hi,
I want to call the RFC using EJB module in java. how to do it.
if someone having the code plz post it.
regards,
Shanthakumar./***Start of JRA specific code***//
// Retrive connection factory
InitialContext initialcontext = new InitialContext();
connectionfactory = (ConnectionFactory) initialcontext.lookup("java:comp/env/ConnFactory");
//Request a connection handle:
connection = connectionfactory.getConnection();
//Create a RecordFactory object to get a metadata description
// of the RFC SALERT_CREATE
RecordFactory recordFactory = connectionfactory.getRecordFactory();
// Create Record objects containing all
// necessary information about the RFM.
MappedRecord input = recordFactory.createMappedRecord("SALERT_CREATE");
//Fill in the import parameters and the import table structure data here
input.put("IP_CAT", "ALRT_CAT"); // alert category
// Refer to the SW_CONT structure of the table of RFC SALERT_CREATE
ResultSet inputITContainer = (ResultSet) input.get("IT_CONTAINER");
int tabIndex = 0;
inputITContainer.moveToInsertRow();
inputITContainer.updateString("ELEMENT", "CONT_1");
inputITContainer.updateString("TAB_INDEX", "" + tabIndex++);
inputITContainer.updateString("ELEMLENGTH", "250");
inputITContainer.updateString("TYPE", "C");
inputITContainer.updateString("VALUE","Container_1 value");
inputITContainer.insertRow();
inputITContainer.moveToInsertRow();
inputITContainer.updateString("ELEMENT", "CONT_N");
inputITContainer.updateString("TAB_INDEX", "" + tabIndex++);
inputITContainer.updateString("ELEMLENGTH", "250");
inputITContainer.updateString("TYPE", "C");
inputITContainer.updateString("VALUE","Container_N value");
inputITContainer.insertRow();
interaction = connection.createInteraction();
// execute the call with the input parameters.
interaction.execute(null, input);
}catch(Exception e){
// Error handling code goes here
}finally{
try {
if (interaction != null)
interaction.close();
if (connection != null)
connection.close();
} catch (Exception ignored) {
// Do nothing
// Pass on module data to the next module in chain, unaltered
return moduleData; -
Defining cmp-relation to EB contained in different ejb module project
Hello,
I have to migrate an existing J2EE Application to SAP NetWeaver and WebAS. My task is to keep the structure as similar as possible to increase the recognition factor although using Developer Studio as IDE.
In this application there are cmp relations defined that reference EntityBeans from other sub projects (that I tried to create in different ejb module projects).
References in the same ejb module project seem to work fine but I cannot select referenced EntityBeans of other projects as relation target.
Another remark:
In the given application the ejb-jar.xml-file of the referencing component contains entries of the referenced one. The Developer Studio allows to Add EJBs to ejb-jar.xml, even referenced Beans. But when I select to add referenced EJBs only the Beans of the current project can be chosen. (I did not forget to enter an ejb-local-ref from the referencing to the referenced Bean in ejb-jar.xml as well)
Can anyone give me a hint on how to solve this task? Or where I have forgotten to add a reference?
Thanks
DanielHello Viliana,
Hello everybody else!
I'm currently writing the corresponding masterthesis to my project. That's why I have to deal with this "problem" again.
I tried to look up the part of the spec Viliana's hint ("When you create and use cmp-relationships your beans must be included in one and the same JAR file (that's according to the EJB specification)") bases on.
But the only thing I found addressing this issue tells something else:
"[...]Container-managed relationships can exist only among entity beans within the same local relationship
scope,[...]" (EJBSpec2.1, section 10.3.2)
In my opinion this does not necessarily mean that they have to be in the same JAR but in the same EAR file...
This would mean, that the chosen cmp-relationships strategy with ejb-module-projects is too restrictive.
Can anyone help me with this... Does anyone know further hints on how Entity Beans have to be deployed when belonging to cmp-relationships?
Thanks a lot for any hint on this
Best regards,
Daniel -
EJB Module creation in case of Java proxy
Hello
This question might look irrelevant in this forum but its required when we are dealing with Java proxy. I generated Java proxies of my interface which creates around 8 java classes and which supports EJB 2.0 specifications.
In Netweaver Developer Studio (NWDS) I tried to create a EJB Module project and imported these classes into that.Also I manually modified ejb-jar.xml to include the references of Home and Remote Interfaces and bean class.The problem is its not allowing me to create ejb jar of it (the option Built EJB Archive is disabled when right clicked on EJB Module Project).
Waiting for your reply.
Regards
RajeevSame thing I solved by closing NWDS, restarting cluster, open NWDS.
You assigned your bean to ejb-jar.xml?
If you have any errors in task list then the option is also disabled.
Dominik -
EJB Modul: SAP Enterprise Connector, configuring build path
Hello,
first of all I'm using SAP NW CE.
I created an 2 Development Components, an EJB Module and a Enterprise Application(EAR). In the EJB Module I use the SAP Enterprise Connector to generate Java Proxy Classes to do RFC calls.
In the EAR-DC I add in Properties-->J2EE Module Dependencies the needed jar-files. And in the EJB-DC I reference this.
When I don't work with DCs and I create a "normal" EJB and EAR project that is the way it works.
But with DCs I have a problem when I want to build the DC. I have this error:
package com.sap.aii.proxy.framework.core does not exist
So the build-process don't realize the J2EE Module Dependencies. How can I solve this problem?
Regards,
ArminDid you mean the Development Infrastructure Perspective? If yes I don't find DC -> DC Metadata -> DC Definitino -> Right-click Used DCs -> Add Used DC... if I browse through my DC.
Apart from that I don't want to reference DCs as I write above. I want to reference only jar-files. Because the DCs com.sap.aii.proxy.framework, com.sap.aii.util..misc and com.sap.mw.jco are deprecated. And if I reference DCs I have to use this DCs to use the proxy classes made by the SAP Enterprise Connector. So I want to reference the jar-files where the needed source isn't deprecated.
By the way I use SAP NW CE. -
Hi All,
I am trying to build an Entity Service in CAF. But it is unable to create the EJB Module.
Error:
JDO enhancer failed because of internal Error.
Error: Build stopped due to an error: JDO enhancer failed because of internal Error.
Can any one tell wht the exact problem is and how to rectify it.
Thanks,
Chaitanya.Development Component Build (2008-06-10 19:04:46)
Component name: sample/ejbmodule
Component vendor: sap.com
SC compartment: MyComponents
Configuration: LocalDevelopment
Location: local
Source code location: szp7rn@w2szp7rn01
DC root folder: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\DCs\sap.com\sample\ejbmodule\_comp\
DC type: J2EE
DC subtype: EJBModule
Host: w2szp7rn01
DC Model check:
All used DCs are available locally
validating dependency to build plugin "sap.com/tc/bi/bp/ejbmodule"
validating dependency to public part "default" of DC "sap.com/ejb20"
validating dependency to public part "default" of DC "sap.com/jdbc20"
validating dependency to public part "default" of DC "sap.com/jms"
validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
validating dependency to public part "CAFRuntimeAPI" of DC "sap.com/caf/runtime/impl"
validating dependency to public part "compilation" of DC "sap.com/caf/runtime/api"
validating dependency to public part "default" of DC "sap.com/bi/mmr/core"
validating dependency to public part "compilation" of DC "sap.com/caf/metamodel"
validating dependency to public part "default" of DC "sap.com/com.sap.security.api.sda"
validating dependency to public part "default" of DC "sap.com/tc/logging"
validating dependency to public part "default" of DC "sap.com/com.sap.exception"
validating dependency to public part "default" of DC "sap.com/com.sap.jdo"
validating dependency to public part "compilation" of DC "sap.com/bi/mmr/cwm_1.0_source"
validating dependency to public part "jmi" of DC "sap.com/bi/mmr/jmi"
validating dependency to public part "ClientApi" of DC "sap.com/caf/km.proxyjava"
validating dependency to public part "default" of DC "sap.com/bi/mmr/db"
validating dependency to public part "ClientAPI" of DC "sap.com/caf/runtime/security"
validating dependency to public part "ClientAPI" of DC "sap.com/caf/core/services"
validating dependency to used DC "sap.com/caf/runtime/connectivity/base"
validating dependency to used DC "sap.com/caf/runtime/connectivity"
validating dependency to used DC "sap.com/applocking"
validating dependency to public part "default" of DC "sap.com/com.sap.engine.client.lib"
validating dependency to public part "default" of DC "sap.com/jta"
DC model check OK
Start build plugin:
using build plugin: sap.com/tc/bi/bp/ejbmodule
starting build plugin from : C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\ejbmodule\_comp\gen\default\public\ejb\
Build Plugin 'EJBModulePlugin', Version 7.00 SP 9 (NW04S_09_REL, built on 2006-10-25 22:26:50 CEST)
development component: sample/ejbmodule (sap.com)
software component: MyComponents (demo.sap.com)
location: local
type: J2EE, subtype EJBModule
build variant: default
source location: szp7rn@w2szp7rn01
plugin start time: 2008-06-10 19:04:46 GMT+05:30 (IST)
Java VM: Java HotSpot(TM) Client VM, 1.5.0_12-b04 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Source folder src exists but is empty.
Plugin initialized in 0.063 seconds
Preparing data context..
No 'default' JDK defined, will use running VM.
Data context prepared in 0.031 seconds
Executing macro file..
Using macro file: C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\ejbmodule\_comp\gen\default\public\ejb\macros\build.vm
Creating output file: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\DCs\sap.com\sample\ejbmodule\_comp\gen\default\logs\build.xml
Macro file executed in 0.172 seconds
Starting Ant..
Using build file: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\DCs\sap.com\sample\ejbmodule\_comp\gen\default\logs\build.xml
Using build target: build
Generation folder: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\t\81C8304DFA221C7AF5F2C84019FF3C43
Using Ant version: 1.6.2
compile:
[echo] Starting Java compiler
[echo] Settings:
[echo] debug: on
[echo] optimize: off
[echo] deprecation: off
[echo] verbose: default
[echo] encoding: UTF8
[echo] source: default
[echo] target: default
[echo] source path: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\DCs\sap.com\sample\ejbmodule\_comp\ejbModule
[echo] class path:
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.perf.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\ddic\metamodel\content\_comp\gen\default\public\default\lib\java\SapMetamodelDictionaryContent.zip
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.jdo\_comp\gen\default\public\default\lib\java\jdo.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.jdo\_comp\gen\default\public\default\lib\java\sapjdoapi.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\jmi\_comp\gen\default\public\jmi\lib\java\sap.combimmrjmijmi.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\core\_comp\gen\default\public\default\lib\java\sap.combimmrcoredefault.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\km.proxyjava\_comp\gen\default\public\ClientApi\lib\java\sap.comcafkm.proxyjava~ClientApi.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\applocking.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\frame.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\applocking\_comp\gen\default\public\default\lib\java\jdbc.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel_JMI.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\metamodel\_comp\gen\default\public\compilation\lib\java\sap.comcafmetamodel_JMI_src.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.engine.client.lib\_comp\gen\default\public\default\lib\java\sapj2eeclient.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\connectivity\base\_comp\gen\default\public\com.sap.caf.mp.base\lib\java\sap.comcafruntimeconnectivitybase~com.sap.caf.mp.base.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\security\_comp\gen\default\public\ClientAPI\lib\java\sap.comcafruntimesecurityClientAPI.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\api\_comp\gen\default\public\compilation\lib\java\sap.comcafruntimeapicompilation.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jdbc20\_comp\gen\default\public\default\lib\java\jdbc.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source_JMI.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\cwm_1.0_source\_comp\gen\default\public\compilation\lib\java\sap.combimmr~cwm_1.0_source_JMI_src.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\impl\_comp\gen\default\public\CAFRuntimeAPI\lib\java\sap.comcafruntimeimplCAFRuntimeAPI.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\ejb20\_comp\gen\default\public\default\lib\java\ejb20.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jms\_comp\gen\default\public\default\lib\java\jms.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.perm.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\jta\_comp\gen\default\public\default\lib\java\jta.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\core\services\_comp\gen\default\public\ClientAPI\lib\java\sap.comcafcoreservicesClientAPI.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.exception\_comp\gen\default\public\default\lib\java\exception.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\CAF\DCs\sap.com\caf\runtime\connectivity\_comp\gen\default\public\com.sap.caf.mp.core.api\lib\java\sap.comcafruntimeconnectivitycom.sap.caf.mp.core.api.jar
[echo] C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\BI_UDI\DCs\sap.com\bi\mmr\db\_comp\gen\default\public\default\lib\java\sap.combimmrdbdefault.jar
[echo] output dir: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\t\81C8304DFA221C7AF5F2C84019FF3C43\classes
[javac] Compiling 9 source files to D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\t\81C8304DFA221C7AF5F2C84019FF3C43\classes
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[timer] Java compilation finished in 1.672 seconds
[echo] Starting JDO enhancer
[jdo.enhance] Using classfile: D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\t\81C8304DFA221C7AF5F2C84019FF3C43\classes\com\sap\sample\besrv\test\testJDO.class
[jdo.enhance] Using metadata : D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\DCs\sap.com\sample\ejbmodule\_comp\ejbModule\com\sap\sample\besrv\test\testJDO.jdo
[jdo.enhance] Using dst : D:\Documents and Settings\szp7rn.GEMSCONSULT\.dtc\LocalDevelopment\t\81C8304DFA221C7AF5F2C84019FF3C43\classes
[jdo.enhance] Error while enhancing: JDO ENHANCER: At least one error occurred while enhancing input class for Transparent Persistence; detailed message(s): I/O error while reading input stream or input stream does not denote a valid Java class.
[jdo.enhance] ERROR: com.sap.jdo.enhancer.EnhancerUserException: JDO ENHANCER: At least one error occurred while enhancing input class for Transparent Persistence; detailed message(s): I/O error while reading input stream or input stream does not denote a valid Java class.
[jdo.enhance] ERROR: at com.sap.jdo.enhancer.filter.Enhancer.enhanceClassFile(Enhancer.java:238)
[jdo.enhance] ERROR: at com.sap.jdo.enhancer.Main.enhanceClassFile(Main.java:514)
[jdo.enhance] ERROR: at com.sap.jdo.enhancer.Main.enhanceInputFiles(Main.java:474)
[jdo.enhance] ERROR: at com.sap.jdo.enhancer.Main.process(Main.java:137)
[jdo.enhance] ERROR: at com.sap.jdo.anttasks.JDOEnhance.run(JDOEnhance.java:99)
[jdo.enhance] ERROR: at com.sap.jdo.anttasks.JDOEnhance.execute(JDOEnhance.java:82)
[jdo.enhance] ERROR: at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[jdo.enhance] ERROR: at org.apache.tools.ant.Task.perform(Task.java:364)
[jdo.enhance] ERROR: at org.apache.tools.ant.Target.execute(Target.java:341)
[jdo.enhance] ERROR: at org.apache.tools.ant.Target.performTasks(Target.java:369)
[jdo.enhance] ERROR: at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[jdo.enhance] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:111)
[jdo.enhance] ERROR: at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:62)
[jdo.enhance] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:222)
[jdo.enhance] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:199)
[jdo.enhance] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[jdo.enhance] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[jdo.enhance] ERROR: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[jdo.enhance] ERROR: at java.lang.reflect.Method.invoke(Method.java:585)
[jdo.enhance] ERROR: at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
[jdo.enhance] ERROR: at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
[jdo.enhance] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
[jdo.enhance] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
[jdo.enhance] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
[jdo.enhance] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5615)
[jdo.enhance] ERROR: at com.sap.caf.designer.actions.DcBuildAction.buildDCsForDevConfig(DcBuildAction.java:764)
[jdo.enhance] ERROR: at com.sap.caf.designer.actions.DcBuildAction.access$300(DcBuildAction.java:78)
[jdo.enhance] ERROR: at com.sap.caf.designer.actions.DcBuildAction$1.run(DcBuildAction.java:499)
[jdo.enhance] ERROR: at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
[jdo.enhance] aborted with errors.
Ant runtime 2.187 seconds
Ant build finished with ERRORS
JDO enhancer failed because of internal Error.
Error: Build stopped due to an error: JDO enhancer failed because of internal Error.
Build plugin finished at 2008-06-10 19:04:48 GMT+05:30 (IST)
Total build plugin runtime: 2.531 seconds
Build finished with ERROR -
EJB Model Builder: class is not available in the ejb module archive file.
Hi,
We are testing
SAP NetWeaver Developer Studio and
SAP NetWeaver Application Server, Java(TM) EE 5 Edition.
We created a sample EJB project(EJB 2.1) with an ejb and an EAR project, we deploy it using SAP NetWeaver Developer Studio.
But when we see in the log of the server , there is a message like this:
"EJB Model Builder: Bean class com.saptest.ejb.TestEJBBean is not available in the ejb module archive file., file: TestSAPEJB.jar#TestSAPEJB.jar"
The jar contains this class, we don't know what is wrong.
Thanks
Germán Santana
Bogota,ColombiaYou should place the file at:
C:/JRun4/servers/default/default-ear/default-ejb/com/zbeans/Entity1Bean.class
[]s
Michael -
I am trying to deploy an EJB module and it is giving me the below exception :-
####<Feb 17, 2009 12:29:04 PM EST> <Error> <Deployer> <serv23> <pr_6j2_Managed1> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 153 for the application WLITimerEMS
java.lang.NullPointerException
* at weblogic.management.deploy.slave.SlaveDeployer$Task.getTargetedComponents*(SlaveDeployer.java:2201)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.refine(SlaveDeployer.java:2364)
at weblogic.management.deploy.slave.SlaveDeployer.createTask(SlaveDeployer.java:1952)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:863)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Can anyone help me on this???Hi,
Yes, I agree we need to update this paper or at least blog about a change in ADF Swing 10.1.3 that is needed for AM pooling support. Here is what you need to know:
In order to run ADF Swing in batch mode you must have a "Server side configuration". This configuration is used by server side of the application, i.e. by BC EJB running in oc4j context to do am pooling, which in this case is called "remote am pooling" .
This configuration is called AppModuleLocal1. Actually from ADF BC point of view it is local, hence it is used in the same jvm where ADF BC are running.
There two places where you can create this "Server side configuration" (named as AppModuleLocal1) in one of two places:
1) on the Remote tab of AM Editor when you shuttle EJB Session Bean
to the right.
2) on step 3 of "Create Business Components Deployment Profiles" wizard.
To create it:
At the bottom of "EJB Session Bean" panel see "Local Configurations" dropdown and the "New" button close to it. Click the button.
Let me know if this works
Frank
Maybe you are looking for
-
Raise_Exception in CL_CGPL_STATUS_MANAGEMENT=====CP
Hello Expert, Please help me with Raise_Exception dump.Customer is facing this problem daily .we have debugged program many time and all but we are not able to find any clue.Its based on Fund plan id and campaign. And i have checked SAP Note-1475108.
-
Assamese language India in Adobe PageMaker 7 in Windows 8.1 Pro x64 environment
How can I type 'Assamese language, India' in Adobe PageMaker 7 in Windows 8.1 Pro x64 environment ? http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/assamese-language- india-in-adobe-pagemaker-7-in/3f97fbde-332c-48f1-a7f0-62f61
-
Organizing pdf files on an iPad[ was: Barry177]
How can you organise files into folders in adobe reader on an iPad?
-
Hi ExpertALL, I need support, check the source and target structures. Source structure below: Target structure: As you can see the structure "item" it´s unbound, means repeat many times, inside <item> there is a tag <TYPE> that´s cointains two values
-
1.1.3 crashed 23 times and counting
i upgraded to 1.1.3 (bad decision) and i cant even listen to 30 seconds of my song because it will crash. the phone app crashed once. and the ipod app crashed about 7 times in 5 mins. i tried to restore restart and all of those thing it will work fin