Eclipse/EMF developer in India

Hello,
Looking for a experienced Eclipse developer with EMF knowledge in India (preferably Bangalore).
Please email [email protected]
Thanks

Better you check vEmployee. They provide Java services in Bangalore http://www.vemployee.com/hire-java-programmers.html

Similar Messages

Hello..i am new to ATG. Kindly help me in setup of eclipse to develop,deploy and run new ATG project.

Kindly help me in setup of eclipse to develop,deploy and run new ATG project

Install ATG eclipse plugin following steps in below location
Oracle ATG Web Commerce - Appendix D. Development Tools for Eclipse
Then follow steps in following link to setup build environment
Reassembling Your Application Using Ant

TimesTen and Eclipse java development problem

Hello all
Using TimesTen with JDBC in from a Java code developed on Eclipse I encounter a problem: when running the program in debug mode, everything works fine. Running without debug, or outside Eclipse, results in the following error:
java.sql.SQLException: [TimesTen][TimesTen 7.0.5.0.0 ODBC Driver][TimesTen]TT0837: Cannot attach data store shared-memory segment, error 8 -- file "db.c", lineno 7891, procedure "sbDbCreate"
Does anyone know the cause of this, or can point me to logs or other resources I can look into?
Regards,
Shaul Peled
Nuance Communication Inc.

Okay, it is almost certainly an address space issue. Unfortunately 32-bit Windows is about the most problematic platform from this perspective. A TimesTen datastore is a single, contiguous memory region of size approximating PermSize+TempSize+LogBuffSize+DS header. In your case that will be about 1098 Mb. To 'connect' to this datastore, it is necessary to map the datastore memory (it is a shared mapping allocated from the Windows paging file) into your process (in this case the JVM) as a single region. Unfortunately, unlike most O/S, in Windows shared libraries (DLLs) have to be loaded at fixed locations in the address space defined when the DLL was linked. This means that although your process has a 4 GB address space (with quite a bit reserved for WIndows and other uses) that space is often highly fragmented with various DLLs (system and application) located all over the place. This means that often it is hard to find a single contiguous address space region to map a large datastore.
into.
To verify that this is the issue, could you try reducing the datastore size to say PermSize=128, TempSize=64 and see if you can connect then. If you can then you will have to experiment by slowly increasing Perm and Temp until you find the maximum size store you can accomodate. If you are using no logging (Are you sure that is what you want? You will end up with a single threaded datastore if you do that...) you could reduce LogBuffSize to the smallest allowed value (128 Kb).
If it does turn out to be an address space issue then you have 3 options:
1. Live with a smaller datastore size.
2. Try and re-arrange the memory map by rebasing DLLs to create a larger contiguous region. Note that ijn any event it is very unlikely you will ever be able to exceed ~1.5 Gb for a datastore.
3. Switch to 64-bit Windows, 64-bit TimesTen and a 64-bit JVM. Then the only limit on datastore size is available RAM.
Let me know the outcome.
Regards,
Chris

Can i use ADF faces in Eclipse to develop JSF applications

Hi,
i have used Jdeveloper to develop JSF based application but for some reasons
i need to run this application in Ecplise. Is there any possibility for that.

Yes,
you can run ADF Faces applications in Eclipse. However, if you use ADF for binding then this may be a bit more complicated
Frank

Eclipse Plugin development

I want to build a eclipse plugin which can add some source to .jsp page.
the plugin should add code for some TAG by asking properties values through wizard kind of thing.
it should add the generated code for that TAG to current position of the cursor.
Can anybody help me .....I have no idea about plugin development.
Thanks in advance.

read the eclipse documentation. this isn't an eclipse forum.

Creating Dynamic Wizard components in Eclipse Plugin Development

Am developing an Eclipse Plug in with Wizard and Wizard Page Extension.
Right now I am able to build static Wizard Pages with components like Buttons, Text Boxes etc.
How can I build dynamic Wizard Pages? i.e., Wizard Pages with Components like Buttons and Text Boxes added during Run-Time?
Thanks!!

read the eclipse documentation. this isn't an eclipse forum.

Eclipse plgin development

hi am trying to develop a plug in on eclipse
and i want to get the path for the class(project)
that eclipse editor(on focus) is currently opining ...???!!!
is there anyway to do this ???
actually i believe there is cause many plugins
on eclipse uses that but how?????
thanks in advance :)

Have a look at the javadocs for org.eclipse.core.resources.ResourcesPlugin and org.eclipse.core.resources.IWorkspace. You can register listeners somewhere in there that will be notified of what is currently in the editor. I can't remember exactly how to do it, but that's the area you're interested in. What's actually in the editor pane is represented by an instance of ICompilationUnit, so look out for that too
In future, you're far far better off going to the newsgroups at eclipse.org for this. Hardly anyone on here knows anything about SWT, Jface or Eclipse plugins in general. You could also do a lot worse than pick up the following two books - loads of useful information in them
Building commercial quality plugins
Eclipse Rich Client Platform

Which Company is Best on Ruby on Rails Developement in India?

Hi, I looking on Best ColdFusion Development Company in India, Hyderabad. Could you please give me suggestion which company is best on it.

Panzer Technologies has much to offer in the ColdFusion Developer in USA and India, as it has experienced and expert ColdFusion developers helps you to reduce ColdFusion Developer price and time.
Source @
http://www.panzertechnologies.com/IT

Problem in installing EMF in eclipse 3.6

i have downloaded eclipse version 3.6 i am using this for java desktop application development .....means swing
i read from site that to use drag and drop controls 2 plugins are needed emf and gef i have installed .... but when i am installing EMF i was getting this error
Error
Cannot complete the install because one or more required items could not be found.
Software being installed: EMF - Eclipse Modeling Framework SDK 2.7.0.v20110128-1446 (org.eclipse.emf.sdk.feature.group 2.7.0.v20110128-1446)
Missing requirement: EMF Ecore Code Generator 2.7.0.v20110128-1446 (org.eclipse.emf.codegen.ecore 2.7.0.v20110128-1446) requires 'bundle org.eclipse.core.runtime [3.7.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: EMF - Eclipse Modeling Framework SDK 2.7.0.v20110128-1446 (org.eclipse.emf.sdk.feature.group 2.7.0.v20110128-1446)
To: org.eclipse.emf.codegen.ecore [2.7.0.v20110128-1446]
i am not understanding what i have to do

The EMF version which should be getting picked up for Eclipse 3.6 is actually 2.6.x. Based on the error, the update located the 3.7 version (2.7.0) which requires Eclipse 3.7.
You will need to check the update site which you are attempting to install from and ensure Eclipse does not find a newer version for you.
Here are some steps that will limit the update to the Helios site:
Help->Install New Software...
Unselect the "Contact all update sites during install to find required software" option
Select the Helios Update Site: Helios - http://download.eclipse.org/releases/helios
The list of available Helios (3.6) features should appear.
Choose the features you want to install. The latest EMF for Helios looks to be 2.6.1.v20100914-1218 at the moment.
Bryan

Plug a Swing-based development tool into Eclipse

This article teaches you how to integrate a stand-alone Swing-based editor into the Eclipse Platform as a plug-in. Using simple techniques, you can share resources between the Swing tool, the Eclipse Platform, and various SWT widgets -- and these resources can communicate through mutual awareness. Tool vendors who want to bring Eclipse-based development tools to market with a minimal amount of re-coding will also find this article helpful.
Learn how to integrate a Swing editor into the Eclipse Platform
http://www-106.ibm.com/developerworks/java/library/os-swing/?t=gr,JavaW03=EclipseSwing

Originally posted by: martin.brenda.martinbrenda.de
> Anybody is welcomed to share any first-hand expreience, links, opinions,
> plz!
I am working since a few months on this topic. We have a Swing Application
which we want to integrate in Eclipse. We decided to do this in little
steps. One of the first is to integrate the application as far as possible
over the Swing Bridge. And the results are really good. We integrated our
editor, some views, resources and the most actions so far. We hope to
release our Alpha version in February.
The really nice thing is, that we could take allmost all our existing Swing
Wizards and so on from the old application. Only some wizards for Project
and new Resource creation had be made new. The communication between AWT /
Swing and SWT is also runnig well. All events (Mouse, Keys..) are being
transfered from one toolkit to the other. The only problem is the
synchronization of the Swing and SWT thread. You often get "Invalid thread
access" messages. But this is solvable.
Gentleware also integrated their modelling tool Poseidon in Eclipse over the
Swing-Bridge. If you wanna see how it looks like, here the download page:
http://gentleware.com/downloadcenter.0.html
You need the Professional version. Their integration is not so nice (I think
they did it really fast). But I think they work on it in the future. But
here you can see that it works ;-)
Here are also some links:
http://eclipsewiki.editme.com/CallingSwingFromSWT
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.sni ppets/src/org/eclipse/swt/snippets/Snippet135.java?rev=HEAD& amp;content-type=text/vnd.viewcvs-markup&only_with_tag=H EAD
http://www.logemann.org/day/archives/000008.html
Bye,
Martin Brenda

Developing SIP Servlet using Eclipse

Dear all,
In the BEA documentation "developing SIP Servlet using Eclipse", it says:
WebLogic SIP Server 3.0
JDK 1.4.2
Ant (installed with WebLogic SIP Server 3.0)
Eclipse version 3.1
CVS client and server (required only for version control)
I want to kown it should be JDK 1.4.2 but not 1.5.0?
And how to set Ant which installed with Weblogic SIP Server in Eclipse? Because I checked that Eclipse use the Ant by defaut.
I really have problem with setting up Eclipse for developping SIP Servlet, Thanks for your help!
li

Dear all,
I have resolved it.
The path is not correct in the ant build file.
Thanks

WebLogic Event Server Eclipse Development Environment now AVAILABLE

The new Eclipse-based development environment for the WebLogic Event Server is now available.
These new developer capabilities will simplify and accelerate the creation, deployment and debugging of EDA application for the new Java container.
[url http://commerce.bea.com/showproduct.jsp?family=WLEVS&major=2.0&minor=-1]

When starting the event server from the Eclipse server view, I get the following error...
<Aug 14, 2007 3:58:55 PM EDT> <Critical> <BootBundle> <BEA-1004004> <The system could not find the default security providers due to "null". The system will exit.>
Am I possibly just missing a configuration value?
thanks!
Mike

DocFlex/Javadoc 1.5.6, a multi-format doclet development tool and more

DocFlex/Javadoc is both a multi-format Javadoc Doclet and a rapid doclet development tool, which allows easy creation of professional quality Java API documentation generated by Javadoc in various output formats.
More in this article:
Key Features
Availability
This Version
What is DocFlex?
Main Concepts
Other Applications
Links
KEY FEATURES
Template-driven doclet architecture
- Actual doclets are created in the form of special templates interpreted by the DocFlex Doclet, which is the template interpreter / output generator wrapped in the form of a Javadoc Doclet.
- The high quality graphic Template Designer allows you to visually design most of things, whose development was possible so far only by direct Java coding.
- The templates are designed independently on a particular output format. All formatting is specified in some universal way using properties of template components. During the generation, it is rendered with the suitable features available in the selected output format.
- The elaborated support of template parameters (including multivalued list parameters). The parameters are defined and accessed within templates to adjust dynamic properties of template components. Most of options previously used to control an ordinary doclet now simply become template parameters!
- The possibility to call templates from one another. This feature (along with the template parameters) makes possible re-using the same templates for different tasks as well as organizing template libraries.
Data processing
- The entire Doclet API is represented in the form of a virtual XML document (called Doclet DSM), on which the designing and processing of all templates is based.
- Sophisticated capabilities for data querying and sorting based on an extension of XPath.
- Full support of new Java 5.0 language features: Generic Types, Enums, Annotations.
- Simultaneous support of Java 1.4 and Java 5.
Creating hyperlinks
- Generation of an extensive network of hyperlinks interconnecting the whole documentation.
- The hyperlinks can be generated in all output formats that support them (this currently includes HTML and RTF).
- The universal way of defining documentation cross-links based on the link/target keys specified in templates.
- In RTF, the cross-links can be generated in the form of page number references, which effectively makes them usable even in the printed documentation.
- In HTML, the possibility of loading several frame windows from a single hyperlink at once.
Universal support of various formatting techniques
- text formatting: fonts, colors, borders
- paragraph formatting: margins, pagination control, borders, colors
- border formatting: styles (solid, double, dashed, dotted), thickness, colors
- tables: arbitrary cell layouts, borders, nested tables
- lists: bulleted, numbered, delimited
- document fields (RTF): page number, number of pages, TOC, etc.
- page formatting: size, orientation, margins, headers/footers
- formatting styles
- rendering of embedded HTML, which means interpreting in non-HTML output formats (such as RTF) the HTML tags embedded in text data (e.g. documentation comments). Almost all HTML tags practically usable in doc-comments are supported.
Inserting images
- statically specified in templates
- dynamically, obtained by <img> tags found in Java comments
- supported image formats: GIF, PNG, JPG, WMF, EMF, BMP
Output formats
- HTML (both framed multi-file and single-file output)
- RTF (version 1.6 - supported since Word 2000).
- TXT (plain text), which may be particularly useful for various utilizations of the Java code information provided by the Doclet API generate XML files by it, or SQL files to import into a database).
Standard Template Set
- The ready-to-use Standard Template Set included in all editions of DocFlex/Javadoc allows you to immediately generate:
(*) The framed HTML Java API documentation similar to that generated by the standard Javadoc.
(*) The same documentation packed in a single HTML file.
(*) The unmatched quality RTF JavaDoc.
- Special features supported by standard templates:
(*) Excluding classes/methods/fields by custom tags and annotations.
(*) Selective omitting of package qualifiers.
(*) Selective documenting of custom tags (similar to -tag option of Standard Doclet).
- By modifying the standard templates, you can quickly customize the generated documentation according to your needs.
Doclet GUI
- Besides command line options, DocFlex Doclet supports an alternative user-friendly way to control the template-based doclets interactively -- the high quality Doclet GUI.
- The Doclet GUI starts with the Generator Dialog, where you can specify all general settings (such as the main template, the output format and the output directory), start the generation, track its progress and stop at any moment you need.
- The grid-tree-based Parameter Inspector invoked from the Generator Dialog for a selected template allows you to view the descriptions of all template parameters controlling the doclet and set their values according to the parameter data types.
- The generator options specific for the selected output format can be set in the corresponding Format Option Inspector (also invoked from the Generator Dialog).
- Once the generation is finished (or cancelled), you can start it again with different settings or a new main template without restarting the whole Javadoc.
Integrations
- With any system that runs Javadoc (in particular, see below)
- Apache Ant
- Apache Maven 2
- Eclipse
For lots more information, see DocFlex/Javadoc homepage: [http://www.filigris.com/products/docflex_javadoc/]
AVAILABILITY
DocFlex/Javadoc comes in two editions:
(1) The full edition called "DocFlex/Javadoc" as it is. This is commercial software, which includes all the implemented functionality.
(2) The reduced freeware edition called "DocFlex/Doclet". It includes only the output generator and can be used as an interpretor of any custom templates. It also includes the standard template set, which allows you to instantly use it as an HTML doclet (similar to the standard one, however with some special features) plus an excellent quality RTF doclet.
Both editions are available for downloads on the page: [http://www.filigris.com/downloads/]
THIS VERSION
New features:
- The template interpretor works 15-20% faster
- Improvement of RTF output
- Multi-valued (list) template parameters
- Custom elements
- Standard Templates: Selective documenting of custom tags (similar to -tag option of standard doclet)
For more details, see product Readme | Change Log on the downloads page: [http://www.filigris.com/downloads/]
WHAT IS DOCFLEX?
DocFlex is an innovative technology for development of high quality template-driven documentation/report generators by any kind of data obtained from various software applications via the Java APIs they provide.
MAIN CONCEPTS
The whole DocFlex technology is based on four generalizations:
(1) The mapping of an entire Java API onto a virtual XML-like representation made of some elements and attributes so as to process any such a representation in a universal way using techniques borrowed from the field of XML, like XPath (or more precisely, a conceptual analogue of XPath with some extensions not present in it).
(2) The abstract formatting concept based on four layouts (flow of text, flow of paragraphs or paragraph-like objects, tables and lists), which can be rendered in most modern document formats (e.g. HTML, RTF, XSL-FO etc.)
(3) The automatic generation of hyperlinks (or their page number reference equivalents) by matching the sets of keys produced from certain natural properties of the things (entities) being documented and hyper-linked.
(4) The representation of the object controlling structure of the output generator (made on the first three principles) in the form of a plain-text template with a possibility to create and edit such templates using a graphic Template Designer, which visualizes the controlling objects (now becoming template components) in a form resembling the output they will produce.
OTHER APPLICATIONS
In fact, DocFlex/Javadoc is not the only application of DocFlex technology. The following is a summary of other DocFlex software:
DocFlex/XML
The SDK and runtime environment for rapid development and execution of template-driven automatic documentation/report generators by any data obtained from XML files.
This is currently the most complex and advanced application of DocFlex technology. Actually, this tool can be considered a powerful alternative to XSLT. At least, it is definitely able to do what XSLT apparently not (for example, see XSDDoc below). We will publish a more detailed comparison DocFlex/XML versus XSLT with the next DocFlex/XML release, which is coming very soon.
DocFlex/XML home page: [http://www.filigris.com/products/docflex_xml/]
DocFlex/XML | XSDDoc
A template set for DocFlex/XML that implements a high quality W3C XML Schema documentation generator in HTML and RTF output formats.
For more details, please see: [http://www.filigris.com/products/docflex_xml/xsddoc/]
DocFlex/XML | WSDLDoc
A similar template set for DocFlex/XML that will implement a high-end WSDL documentation generator.
This product is not released yet.
DocFlex/Together
A template-driven documentation generator for [Borland Together|http://www.borland.com/us/products/together/] (which is a UML modeling tool).
This is the earliest application of DocFlex technology and probably the most beautiful one. It works only with Together Architect 1.x, which is now obsolete. Unfortunately, since Together 2005, Borland eliminated any open APIs (for unknown reasons). Because of this, further development of DocFlex/Together was impossible.
DocFlex/Together home page: [http://www.filigris.com/products/docflex_together/]
See also examples of the UML documentation generated with it: [http://www.filigris.com/products/docflex_together/examples/]
The future DocFlex/UML is going to generate something like this as well.
DocFlex/UML
A template-driven UML documentation generator based on [Eclipse EMF|http://www.eclipse.org/emf/]. This tool is in early development stage yet. In a sense, it will continue DocFlex/Together with the focus on integration with other UML tools that use Eclipse EMF.
LINKS
This original article can be found at:
[http://www.filigris.com/ann/docflex_javadoc_v1.5.6/]
DocFlex/Javadoc home page:
[http://www.filigris.com/products/docflex_javadoc/]
DocFlex/XML home page:
[http://www.filigris.com/products/docflex_xml/]
DocFlex/XML | XSDDoc, the XML schema documentation generator:
[http://www.filigris.com/products/docflex_xml/xsddoc/]
Free downloads:
[http://www.filigris.com/downloads/]

Now, DocFlex/Javadoc v1.4 has been released specifically dedicated to Linux (Mac OS X) support:
(*) Some early bugs have been fixed, which prevented it working properly under Linux.
(*) A special RTF option was introduced to generate OpenOffice.org friendly RTF (see below)
(*) Improved support for external document viewers.
(*) Now, DocFlex/Javadoc software includes the shell script files prepared to quickly install and launch it under Linux
New RTF option
A new RTF output option "Tune output for MS Word� has been introduced. This option, actually, allows switching off that very tuning (which until now was the default mode) to produce an RTF friendly to open with other non MS Word applications, e.g. OpenOffice.org Writer under Linux.
Read full announcement (and screenshot) by this link:
http://www.filigris.com/ann/docflex_javadoc_v1.4/
Regards,
Leonid Rudy
http://www.docflex.com

Android plugin not working in Eclipse on Arch 64bit

Hi, I'm having some trouble getting the android plugin to work. I know there are a lot of similar threads about this on this forum and google but nothing seems to work. I have installed Eclipse 4.2 through pacman. I removed openJDK and installed Oracle's jdk/jre.
java -version:
java version "1.7.0_06"
Java(TM) SE Runtime Environment (build 1.7.0_06-b24)
Java HotSpot(TM) 64-Bit Server VM (build 23.2-b09, mixed mode)
I manually edited Eclipse's ini file to find the jre:
-vm
/opt/java/jre/bin/java
I did this before logging out or rebooting. And Eclipse would open ok and use the jre/jdk. I Then tried to install the ADT plugin and it would install without problem. I rebooted Eclipse but there were no signs of the plugin. No android project creation or android preferences. The plugin shows listed as installed.
I then tried downloading android-eclipse from AUR and rebooted. But Eclipse looks the same.
I have no idea what could be wrong here. Any help is appreciated. Thanks.

hi
I have same problem but not able to solve it.
I was running elcipse 3.7.x with ADT plugin without problems.
after eclipse update to 4.2.1 I am not able to use ADT. Eclipse is saying that it is installed but could not find anything from it in enviroment.
I did reinstall eclipse and eclipse-emf eclipse-gef eclipse-wtp and follow http://developer.android.com/sdk/instal … g-adt.html but not sucess. Later I did find this https://developers.google.com/eclipse/d … clipse-4.2 but it is still same. ADT is installed but cannt use it.
I am using openjdk
pacman -Qs jdk
local/jdk7-openjdk 7.u7_2.3.2-2
Free Java environment based on OpenJDK 7.0 with IcedTea7 replacing binary plugs - SDK
local/jre7-openjdk 7.u7_2.3.2-2
Free Java environment based on OpenJDK 7.0 with IcedTea7 replacing binary plugs -Full Java runtime
environment - needed for executing Java GUI and Webstart programs
local/jre7-openjdk-headless 7.u7_2.3.2-2
Free Java environment based on OpenJDK 7.0 with IcedTea7 replacing binary plugs - Minimal Java
runtime - needed for executing non GUI Java programs
Can be that problem?
thanks

ABAP GUI from HANA Developer Studio

Hi,
I am facing this issue when stating ABAP GUI / execute any abap program in HANA developer Studio. Any solution for this?
Failed to create the Parts Controls:
java.lang.IllegalStateException: Could not start SAP GUI for Windows: C:/Program Files (x86)/SAP/FrontEnd/sapgui/\SapGuiServer
at com.sap.adt.sapgui.ui.internal.win32.embedding.WinGuiServerProxy$SapGuiServerProcess.start(WinGuiServerProxy.java:593)
at com.sap.adt.sapgui.ui.internal.win32.embedding.WinGuiServerProxy.startGuiServerProcess(WinGuiServerProxy.java:156)
at com.sap.adt.sapgui.ui.internal.win32.WinGuiFragment.getGuiServerProxy(WinGuiFragment.java:86)
at com.sap.adt.sapgui.ui.internal.win32.embedding.EmbeddedWinGuiEditor.createEmbeddedGuiContent(EmbeddedWinGuiEditor.java:85)
at com.sap.adt.sapgui.ui.internal.views.AbstractSapGuiWorkbenchPart.createPartControl(AbstractSapGuiWorkbenchPart.java:121)
at com.sap.adt.sapgui.ui.internal.editors.AbstractSapGuiEditor.createPartControl(AbstractSapGuiEditor.java:149)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:142)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:323)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1147)
at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:65)
at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4688)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205)
at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)
at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80)
at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58)
at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:576)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:543)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:619)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:331)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1046)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3112)
at org.eclipse.ui.internal.WorkbenchPage.access$21(WorkbenchPage.java:3034)
at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:3016)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3012)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2976)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2959)
at com.sap.adt.sapgui.ui.SapGuiPlugin.openGuiEditor(SapGuiPlugin.java:180)
at com.sap.adt.sapgui.ui.SapGuiPlugin.openEditorAndStartTransaction(SapGuiPlugin.java:122)
at com.sap.adt.sapgui.ui.internal.handlers.OpenSapGuiHandler.openView(OpenSapGuiHandler.java:45)
at com.sap.adt.sapgui.ui.internal.handlers.OpenSapGuiHandler.execute(OpenSapGuiHandler.java:39)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: java.io.IOException: Cannot run program "C:/Program Files (x86)/SAP/FrontEnd/sapgui/\SapGuiServer": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1042)
at com.sap.adt.sapgui.ui.internal.win32.embedding.WinGuiServerProxy$SapGuiServerProcess.start(WinGuiServerProxy.java:590)
... 110 more
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:288)
at java.lang.ProcessImpl.start(ProcessImpl.java:133)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023)
... 111 more
My HANA developer studio is not at C:\ProgramFiles(x86) folder.

This problem is resolved - i updated my SAPGUI.

Eclipse/EMF developer in India

Similar Messages

Maybe you are looking for