I am trying to do a BPEL Hello World Project, I am following this link "Hello World BPEL"
I am doing everything as stated up to step 13 (however, I do not get a blank wsdl screen as stated in the tutorial, I have to modify the existing elements rather than creating them).
In step 17, as per the tutorial, I should get the associated port, but what I am shown is blank. (The drop-down is empty).
Can anyone tell me what I am I doing wrong? How do I get the correct port here?
I am using eclipse luna and apache ode server 1
Thanks
I think you should look into this video. I am pretty sure you missed something like I did a couple of times using the same tutorial. I for sure found it helpful while getting started with BPEL on the latest Eclipse Oxygen. However, I must say you should also know about Open-ESB. It is an another IDE built on top of Netbeans and is powerful as well. It is too supported by proper documentation and has some neat examples in the Sample projects. ;)
Related
I am new to JBoss Fuse. I am trying to follow the tutorials and use Marshall and Unmarshall features using JBoss Developer Studio.
Problem, I am facing is, I am not able to see any options in Properties tab for Marshall.
This is what I am seeing on my IDE.
Seen on my IDE
But in the tutorials, this what what is shown.
Shown in tutorial
Please help me and let me know what needs to be done to see those options.
Thanks for your help.
Regards, Vishu
you unfortunately hit a known regression in 9.1.0, see https://issues.jboss.org/browse/FUSETOOLS-2314
The good part is that this issue has been already fixed and fix will be available in next release, Fuse Tooling 9.2.0 which is currently planned at end of May.
regards,
I'm working on a semantic-web project and I'm looking for real-life ontologies to test a couple of applications an algorithms. What I'm searching for are different sizes and structures, something that will allow me to benchmark the company's solutions, preferably, not home-made mocks, but something that is actually used. Unfortunately, looking at the entire ontology using OntoGraf is a little cumbersome.
I found a Protégé plugin called NavigOwl, which seems to be perfect for the task of viewing an entire ontology at once and judging its general complication and structure. The thing is, I can't get it to work.
I download the plugin from HERE and follow the instructions.
I put the jar in the plugin directory of my Protégé install.
I open protege and load an ontology
I go to Window>Tabs and select NavigOwl
A NavigOwl tab appears but it only contains the class hierarchy view, while the rest of the window is grey. It's simply blank, as shown below:
Clicking any of the classes in the hierarchy view does not change anything.
I googled for a solution and I managed to find this thread on nabble.com. The poster says he fixed the problem but he doesn't know how. Resetting the tab to default state is among the implied solutions but it doesn't work for me. Closing and reopening the tab, as well as Protégé itself changes nothing.
Have you encountered the problem? What could be the cause?
I'm using Protégé 4.1.0 Build 239 with the bundled JRE (1.5.0) on Windows 7 home premium x64.
I've tried both the JAR available here (NavigOwl plugin for Protégé 4.1) and the one mentioned in Protégé wiki at Stanford, here (version 1.1.0) but the situation persists.
I had came across the same problem but when i upgraded the JDK it started working. though i do not propose upgrading was the solution but it is working now.
I'm a beginner trying to learn my way through making my first real Android app. I actually started an app using Eclipse and have gotten pretty far with it. I'd like to be able to continue its development using B4A. Is it possible to bring my work from Eclipse into B4A?
What you can do, is to wrap your existing code as a library and then reference it from Basic4android. See this video tutorial.
B4A is a language on its own and it has its own editor.
While, in theory, you can edit project files of a B4A application with any editor, I would assume that you used JAVA as your main programming language.
As B4A uses a language that close resembles (Visual) Basic that, in turns gets converted into JAVA while compiling, you have actually 2 choices in front of you if you want to use B4A:
1) the first is to port your project to B4A but this means that you will need to rewrite the code according to the B4A language specifications;
2) the second option would be to integrate your JAVA code running it inline : see this forum post on the topic
2) if you can pack whatever you wrote as a library module to be used later on by B4A, you could opt to do that: see this forum post on the topic
I'm looking for resources to learn how to use effectively Eclipse forms within an Eclipse RCP application. I was trying to use the newest SWT Window Builder plugin on Indigo but building forms this way doesn't really work for me eg. cannot put anything inside expandable composite etc. (I have Swing background with Netbeans designer) and I'm new to SWT.
All I can find so far is this quite old tutorial from 2005.
Any help, point to good tutorial/book/source code sample will be highly appreciated.
I've found http://www.vogella.de/ to be invaluable.
Not much changed actually since the old 2005 tutorial so it's still very usable.
Check these out in addition too:
Eclipse Forms: New in 3.3
DeveloperWorks article on making forms Web-like
Cheers,
Max
I've also got the hint to start with vogella but after the first 2 topics I realized It's to hard to start with.
What helped me much more was to create each example/sample project and look for the source. Once you understood how all works you can lookup at vogella what you exactly need.
I'm evaluating the possibility of developing an Eclipse plugin to modify the source code of some Java files.
The Eclipse plugin should:
add one menu option or context menu option to launch the modification process.
add a key binding
only alter the UI in that way when an editor has been open on a Java file.
the modification process would not open a dialog, or maybe, a very simple one.
the modification process would traverse the AST of the Java file and would modify it.
Considering that we have no experience with Eclipse plugins and we need spend time in reading docs, how much time do you estimate in developing that plugin?
Thanks in advance.
It's really not that difficult at all... I had students in my design patterns class doing it for an assignment (adding/removing javabean getters and setters)
See http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
[EDIT: added the following article reference]
And a great article on it at http://www.eclipse.org/articles/article.php?file=Article-JavaCodeManipulation_AST/index.html (from 2006 -- there may be a few API changes since)
Yes, writing plugins takes a little getting used to, but so does any API.
And you can modify the AST -- see the page I reference above.
(I should note that the above link is from the eclipse help, which can also be accessed via Help->Help Contents inside Eclipse -- there's a lot of good info in there, but it's just a starting point)
You'll probably spend quite some time cursing the complexity of the eclipse plugin system. There are some example plugin development projects that can be very helpful if they cover the area you're working in.
I'd say you're looking at 2-4 days of work, spent mainly getting familiar with the platform - someone with a lot of experience writing eclipse plugins would probably take no more than an hour.
However, your step 5 could be tricky. I don't know how easy it is to access and change the Java AST; my experience is based on developing an editor plugin for an exotic file format rather than Java code.
Well, the four first points are easy to achieve, even by monkey coders that look at the eclipse PDE documentation shipped with Eclipse. These can be achieve in 1 day of work, maybe 2.
The hardest point is really the fifth one and the kind of modification you expect to do. Acting directly on the editor content is simple, accessing the editor internal AST and modifying it is really a bigger challenge and I doubt that it could be achieve in less than a week by unexperimented people (it can take longer, depending of what kind of modification you want to apply).