NWDS - Build EJB Archive not possible

Hi there!
Recently I updated my NWDS from version 2.0.15 to version 2.0.16.
My workspace mainly consists of 2 EJB Module projects, 1 Web Module Project and 1 Enterprise Application project.
The EAR project bundles the modules to an enterprise application.
Before updating the NWDS, everything regarding build & deployment worked fine. But now I'm facing the problem that I cannot build the EJB Archives anymore. The menu entry for building the JAR is inactive. Also, when I try to build the whole EAR application, the EJB module archives are missing in the EAR.
I've already tried to create new module projects and copy all sources to the new project. Once the archive build worked, but after restarting NWDS, the problem came up again.
Does anybody has an idea about this issue? Maybe this is a known bug of version 2.0.16?
Any help is highly appreciated!
Kind regards,
Matthias

Hi all!
I'm still having this problem. It seems to handle with a problem of org.eclipse.jface-plugin.
Because, in these corrupted projects, I cannot access ejb-j2ee-engine.xml file correctly.
Each time I'm clicking on a bean listed in this file, I get an error message "An error has occured. See error log for more details."
Ok, the details in the logs are pretty poor:
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
at com.sap.ide.eclipse.j2ee.model.ui.sapejbjar.internal.description.UISapEjbJarDescriptionEnterpriseBean.refreshSpecificUIFromData(UISapEjbJarDescriptionEnterpriseBean.java:486)
So finally, the menu entry "Build EJB Archive" is still inactive and I'm getting slightly mad with this tool.
If anybody of you has expierience with similar behavior of NWDS, PLEASE HELP!
Kind regards,
Matthias

Similar Messages

In my NWDS "Build EJB Archive" is not actitivated?

Hi all!
I created an EJB project and imported some files in to my EJB project. When i try to build my EJB Archive, it is not activated. I tried even a simple EJB project, for that also Build EJB Archive is not activated. Help me
Thanks a lot in advance!

Hi
I have done what you said in your first post, Build EJB Archive is enabled very well, but i got deployment error when deploying .ear file to J2EE engine.
Actually I build an Enterprise project and addded this EJB project to that, and built .ear file and this ear file is deployed onto SAP J2EE engine:
I got this deployment error:
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp14071Jps_Ear.ear
Aborted: development component 'Jps_Ear'/'sap.com'/'localhost'/'2006.06.01.11.40.12':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/Jps_Ear.. Reason: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.
     at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
     at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
     at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2142)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3119)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:522)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.
     at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
     at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
     at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2142)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3119)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:522)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
=======================
Which says that my JPS_EJB.jar file is not properly build.
The error meant to say it is a Bean Problem: No interfaces classes found .
Thanks

Not being able to build EJB archive

hi,
I have created an EJB Module Project and copied some java files into it from another DC project.While trying to build the project my option for 'build EJB archive' is coming as disabled...
Any clues for that?

Hi Parama,
What you have done is just copying of the files to the DC.
The EJB Module actually does not have any Bean Created. Hence, it cannot buld the EJB JAR.
If you just want to use plain Java files, then why not use a Java Project ?
Regards,
Alka.

Build ejb archive disabled - NWDS

hi ,
I am building an adapter module as per:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/da5675d1-0301-0010-9584-f6cb18c04805
But Build EJB Archive option is disabled to create the jar files. I tried many options but still the same.
Can someone help me with what to do?
Can we develop the adapter module using the WSAD(Websphere Application Developer Studio)?

Hi Satya,
just copy your java code at in someother place.....then delete your EJB prj...NWDS will ask for deleting contents....choose delete content also option.. delete both projects......
Now start creating a fresh EJB Project with a new name.....follow the "how to create adapter module" document......do all the steps.......
Then you will be able to build your ejb archive by right clicking your ejb project..
Thanks,
Rajeev Gupta

In SAPNetweaver developer Studio, I am unable Build EJB Archive

Hi,
In EJBModuleProject the Build EJB Archive option is diabled.Even all the ejb's have ejbCreate() method still the Build EJB Archive option is diabled.Also the ejb-jar.xml file is not showing its beans in explorer even it contains description for all the ejbs. Let me know is there any solution for this.

Hi,
the odds are, NWDS will only recognize EJB, which strictly adhere to (its) EJB rules, means created in the GUI, implementing directly the required interfaces, having methods, which throw RmiException, etc. If, by chance, your EJBs do not adhere to these rules, proceed as follow:
1. Create a dummy EJB, say DummyEjb by NWDS means and "secure" the xml description of it as template
2. Take the xml template from 1 and create ejb descriptors for your real EJBs and paste them to the ejb-jar.xml
This way you should get correct descriptors for your EJBs and be able to create the ejb module archive.
Regards
Gregor

How can I build EJB archive after changing java files?

hello,
I changed java beans file, and tried to build jar file again, then the "build EJB archive" context menu is disabled so I can not make EJB jar file!
So frustrated.. NWDS recognizes the changes in the java files , right? How come there 's no Build menu..
Is there any pre-requisite to enable the menu?
I have no idea how I can build jar file..
Please give me a advice.. Thanks~!

I think that in order to create a RPM, you'd need to
use some C.Nope - the RPM is all about packaging and the "magic" x.spec file. You can have anything you want in the RPM, but you have to use RPM tools to build the .rpm file. One of the features is that you can also indicate (via "install" scripts) modifications to other files or the filesystem to support the installation of whatever's in the RPM.

Build ejb archive disabled

hi ,
I am building an adapter module as per:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/da5675d1-0301-0010-9584-f6cb18c04805
But Build EJB Archive option is disabled to create the jar files. Can someone help me with what to do ...
thank you

Hi Raj,
1) Are you using NWDS for developing,
If so open J2ee development perspective from menu option windows in NWDS. In left side, choose J2ee explorer tab. Here, it shows your EJB project. Right click on it and choose Build EJB archive.
2) Check whether you have opened the right perspective when you are trying to build the EJB archive.
3)Check this : The file ejb-jar.xml does not know what is the class and rest of the details for your ejb. For checking this, go to J2EE explorer and you will see ejb candidates.Right click on it and select add to ejb-jar.xml. You should now see the Build EJB Archive option enabled.
Regards
Agasthuri Doss

"build EJB archive" context menu is disabled...

hello,
I changed java beans file, and tried to build jar file again, then the "build EJB archive" context menu is disabled so I can not make EJB jar file!
So frustrated.. NWDS recognizes the changes in the java files , right? How come there 's no Build menu..
Is there any pre-requisite to enable the menu?
I have no idea how I can build jar file..
Please give me a advice.. Thanks~!

Yes, I tried at the J2EE Development Perspective.
The Thing is I already built EJB archive once correctly,
and it worked fine. And now I changed & saved the beans java file, and the build context menu is disabled..
Just doesn't make sense...
Is there anybody who knows how-to ?
Thanks !

Build EJB Archive unsuccessfull

I was just trying my hand at Module programming and thought i wud start off with "Step by step guide to develop a module for reading file name in a sender file
adapter" by Krishnakumar Ramamoorthy.
Seems alls done but the problem is when i try to create bean archive (Page 10 of the pdf) it doesnt give me the option. Build EJB Archive link seems to be disabled in my case.
Any pointers Experts ??
ShaBZ

If you see only these 3 then it means you have already added the ejb candidate to the ejb-jar.xml. In that case i would suggest you to :
1. expand ejb-jar.xml in the same view i.e. J2EE Explorer.
2. delete the ejb entry from there.
3. this will automatically refresh the view and will now show ejb candidates. now add the same as again to ejb-jar.xml
4. Now double click on ejb-jar.xml and go to source tab.Make sure the configuration values for following tags confirm to
<home>com.sap.aii.af.mp.module.ModuleHome</home>
<remote>com.sap.aii.af.mp.module.ModuleRemote</remote>
<local-home>com.sap.aii.af.mp.module.ModuleLocalHome</local-home>
<local>com.sap.aii.af.mp.module.ModuleLocal</local>
value for <ejb-class>
should be same as the fully qualified name of your module processor class.
Hope this helps.
~Amol

Building EJB archive

How do I build EJB archive from class files in my EJB project (no source codes available) ?
Thanks in advance,
Sudarshan Chakravarty

Hi Bhavik,
thanks. The solution you gave is working fine when I have the source codes in the project. My issue is like this. I have downloaded a EAR file. I extracted the class files from the EAR file and put it in my EJB project. Now, when I try to build my EJB archive, it is disabled on the context menu. It works when we have the source codes with us, but "Build EJB archive" is disabled when we have .class files only. Please suggest a solution for this.
Thanks in advance,
sudarshan Chakravarty.

ARC1: Archiving not possible: No primary destinations

Hi
i am getting following errors in my alert.log at Datbase 10.1 on Windows 2003
Wed Dec 08 11:50:04 2010
ARC1: Evaluating archive log 3 thread 1 sequence 3
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive log 3 thread 1 sequence 3 (4)
Wed Dec 08 11:50:04 2010
Errors in file c:\oracle\product\10.1.0\admin\dmsdb\bdump\dmsdb_arc1_2172.trc:
ORA-16014: log 3 sequence# 3 not archived, no available destinations
ORA-00312: online log 3 thread 1: 'E:\ORADATA\DMSDB\REDO03.LOG'
How I can see that file 'E:\ORADATA\DMSDB\REDO03.LOG' is available on hard disk:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>dir E:\ORADATA\DMSDB\REDO03.LOG
Volume in drive E is New Volume
Volume Serial Number is 640A-8421
Directory of E:\ORADATA\DMSDB
12/08/2010 11:48 AM 10,486,272 REDO03.LOG
1 File(s) 10,486,272 bytes
0 Dir(s) 103,370,887,168 bytes free
I think this is due to hard disk error/bad sector.
Now how can I get rid of this error?
Habib

The server was shutdown for some reason and now after starting it again I am unable to startup the database:
SQL> startup;
ORACLE instance started.
Total System Global Area 524288000 bytes
Fixed Size 789692 bytes
Variable Size 149680964 bytes
Database Buffers 373293056 bytes
Redo Buffers 524288 bytes
Database mounted.
ORA-16038: log 3 sequence# 3 cannot be archived
ORA-00333: redo log read error block count
ORA-00312: online log 3 thread 1: 'E:\ORADATA\DMSDB\REDO03.LOG'
I tried to increase the size of db_recovery_file_dest_size as suggested in replies on my question but still no luck.
SQL> alter system set db_recovery_file_dest_size=123G ;
System altered.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16038: log 3 sequence# 3 cannot be archived
What is the size of E:\oradata\flash_recovery_area now?Size of E:\oradata\flash_recovery_area now is 20.4 GB at the moment.

Build and Archive not available?

I'm trying to build an application to test on a friends (windows based) computer, so I want to do the Build and Archive function and send them the file since they are remote.
My app builds fine, loads in the simulator and everything, but this option is grayed out.
I'm using the latest sdk/xcode. Thanks

You must install the Application Tools package after installing Xcode 3.2.5. There is a link to the Application Tools package below the link to download Xcode 3.2.5 and iOS SDK 4.2.
http://developer.apple.com/devcenter/download.action?path=/ios/ios_sdk_4.2__fina l/application_tools_1.1.dmg
If you have access to Apple's forums for paid developers, read FAQ #5 at the following URL for more information:
https://devforums.apple.com/thread/75228?tstart=0

NWDS Build Error JDK_HOME_PATH not set

Hi,
I am having two problems.
1. I am getting the classic
     Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'
This is the whole log,
Jul 24, 2014 3:12:01 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ess/sg/fam: Build failed for sap.com/ess/sg/fam(sap.com_SAP_ESS_1) in variant "default": The Build terminated with errors
------------------------------------- Build log ------------------------------------------------------
Development Component Build (2014-07-24 15:11:51)
Component name: ess/sg/fam
Component vendor: sap.com
SC compartment: sap.com_SAP_ESS_1
Configuration: ND1_EHRESS_D
Location: ND1_EHRESS_D
Source code location: http://zq4c1:50100/dtr/ws/EHRESS/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/sg/fam/_comp/
DC root folder: C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\
DC type: Web Dynpro
Host: zq4c1
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
   validating dependency to public part "default" of DC "sap.com/tc/col/api"
   validating dependency to public part "default" of DC "sap.com/tc/cmi"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
   validating dependency to public part "default" of DC "sap.com/tc/logging"
   validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
   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.mw.jco"
   validating dependency to used DC "sap.com/pcui_gp/xssfpm"
   validating dependency to used DC "sap.com/pcui_gp/xssutils"
   validating dependency to used DC "sap.com/ess/per"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/webDynpro
   starting build plugin from : C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 00:51:04 CET, CL79160)
   development component: ess/sg/fam (sap.com)
      software component: SAP_ESS (sap.com)
                location: ND1_EHRESS_D
                    type: Web Dynpro
           build variant: default
         output location: C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\gen\default
       generation folder: C:\Documents and Settings\nd1adm\.dtc\1\t\9BEBB9B83BED543CBB6BD26A34D713CE
       plugin start time: 2014-07-24 15:12:00 GMT+08:00 (SGT)
                 Java VM: Java HotSpot(TM) Client VM, 11.0-b15 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Source folder "META-INF" does not exist and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.265 seconds
Preparing data context..
No public part descriptor found for component "tc/col/api" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/cmi" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/ddicruntime" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wd/webdynpro" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/logging" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wdp/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.proxy.framework" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.util.misc" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.exception" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.mw.jco" (vendor "sap.com"), public part "default", using legacy mode.
Error: com.sap.tc.buildplugin.util.BuildPluginException: No JDK_HOME_PATH defined for key 'JAVA_HOME'
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaCompiler(JavaMacroContextProvider.java:235)
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaEnvironment(JavaMacroContextProvider.java:180)
at com.sap.tc.buildplugin.JavaMacroContextProvider.execute(JavaMacroContextProvider.java:35)
at com.sap.tc.buildplugin.PrepareContextBuildStep.prepareTechnologySpecificData(PrepareContextBuildStep.java:187)
at com.sap.tc.buildplugin.PrepareContextBuildStep.setupBuildFileCreatorContext(PrepareContextBuildStep.java:95)
at com.sap.tc.buildplugin.PrepareContextBuildStep.execute(PrepareContextBuildStep.java:56)
at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5633)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction.buildDCs(DcCreateProjectAction.java:1027)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:299)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'
Build plugin finished at 2014-07-24 15:12:01 GMT+08:00 (SGT)
Total build plugin runtime: 1 second
So what am I doing?
I am trying to do? I am trying to sync the sources. (attachment snc2.png)
I already changed/added the java home at 3 locations,
Visual administrator (attachment snc3.png)
vmparam file (attachment snc4.png)
I downloaded all the java versions are 32 bit.
But even after doing all these I am still facing the issue.
My NWDI version and details.
are ver. 7SP15
and NWDS is 7.0.12
And the NWDS when I clicked on configuration details I noticed this log and the first few lines are really fishy..
** Date: 7/24/14 4:36 PM
*** System properties:
JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10
JDK1.4.2_HOME=C:\j2sdk1.4.2_17
JDK1.4_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10
allUserDir=C:\Documents and Settings\All Users\Application Data
awt.toolkit=sun.awt.windows.WToolkit
Notice that JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10, it is pointing to jdk1.6.0, but where to change to that? is this the issue?
Tried all possible things and solutions that I could find online but no use.
2
I have problem with the server (DTR) keep disconnecting once in a while, it says
DTR server http://<hostname>:50000 unreachable.
Socketclosed...
temporarily what i am doing is that to restart my instance from mmc and that works for a while, I believe it is the FQDN name that I have to change for the dtr, but where can I change that? and also what is the reason that it is able to connect the first few times when i restart the server but not later?
Thanks for your time.

No, that is not the issue, it was already set as well. But apparently have to change the buildpath in the build variant in the CBS

File sender adapter: archiving not possible with transp.prot "filesystem,

Hi XI gurus,
in my FILE sender adapter I want to archive the processed files to a separate sub-directory of the "in" directory.
It works if I use transport protocoll "FTP" with a specific user
but it don't works when I use transport protocoll "file system (NFS)".
the xi user has all permission on the directories.
file system is on a UNIX machine.
Has anybody an idea why archiving only works with transf.protocoll FTP ?
Thanx very much in advance
regards
Hans

Hi,
Check this thread for same problem Re: NFS Sender File Adapter Source Directory
Thanks!

Cannot build EJB jar file in NWDS

hello,
I changed java beans file, and tried to build jar file again, then the "build EJB archive" context menu is disabled so I can not make EJB jar file!
So frustrated.. NWDS recognizes the changes in the java files , right? How come there 's no Build menu..
Is there any pre-requisite to enable the menu?
I have no idea how I can build jar file..
Please give me a advice.. Thanks~!

You might check the weblogic.developer.interest.ejb.tools new group.
Make sure that the tool doesn't leave this ejbcgen directory around. It
should delete
that temp dir. When it doesn't it keeps all the old generated stuff around
and your changes won't be
reflected in the new jar.
Rodrigo Ruiz Aguayo <[email protected]> wrote in message
news:[email protected]..
Hi,
I have a problem with the EJBDeployerTool. When I want to update
a class file (for example, because I corrected any problem), the
deployer tool doesn't update the file correctly. It keeps the
old version of the class file.
In order to update a jar I have to copy the newer version in the
.ejbdeployer/provider-projects directory by hand. Is it a bug?
Is there any other way to do this? We are wasting too much time
in this task, instead of programming :_(
Thanks in advance,
José Rodrigo Ruiz Aguayo e-mail : [email protected]
I.T. en Informática de Sistemas webpage : ---------------------
"Simulation is perfect, whenever we're not talking about reality"

NWDS - Build EJB Archive not possible

Similar Messages

Maybe you are looking for