JOpera for Eclipse - JOpera Bugs

Please fix hello world adapter for 2.6.0

mahmoudrabie — Fri, 09 Nov 2012 18:18:27 +0000

Dear JOpera Team,

How are you? I hope you are fine.

I am trying to run the demo
http://www.jopera.org/download/demos/adapter

I have fixed the new extensions to match what mentioned about (Breaking API changes) in
http://www.jopera.org/version/2.6.0

However, when start the testing example OML, it doesn't give any response. The process in gray color. (UNDEFINED State)

What is the problem?

Please, fix the attached adapter to be runnable on version 2.6.0 or give me instructions to come with it running.

Bug in the mapstream example

mahmoudrabie — Thu, 11 Aug 2011 12:07:38 +0000

Dear JOpera Team,

Thank you for providing this nice open research platform. I tried to add the example of (mapstream) to my JOpera project. but I received the following error

Adapter "database" has an invalid Component-Type reference: system.telegraphcq.CT_TELEGRAPHIN

How can I fix this error

Thank you in advance

Type Task SOAP_X has an invalid Condition: String index out of range: 109

nabil — Thu, 22 Apr 2010 10:48:06 +0000

Hello,

When i make a condition like this (PROC.m<>(T.a) AND (T.b)) so i receive as problem the following "Task SOAP_X has an invalid Condition: String index out of range: 109".

Could you help me please
Best Regards
Nabil
Master student
Tunisia

XML transformation

jpullmann — Fri, 05 Mar 2010 09:38:54 +0000

Dear JOpera team,

I plan to apply JOpera in a project, because of its
outstanding agile composition approach and light-weight
interfaces. Though the data processed is mainly XML and
it relies at least on XML transformations. Currently
XSLTAdapter does not seem to work, its System output is
empty although the task finishes successfully. Is there
a any workaround ?
Thank you
Jaro

issue with Condor adapter

vad-montreal — Sat, 27 Feb 2010 14:39:29 +0000

Hi,
Firstly, Thank you for JOpera, it is an excellent tool! I'm learning its functionality and trying to evaluate it.

This message is to report a Condor adapter issue:
*.sub files lose the line with "queue" command during staging from local host (Eclipse with JOpera) to condor submission host. And Condor adapter programs (in eclipse 3.5, eclipse 3.5.1, on Windows XP) exit with error message:
-----------------------------------------------
Submission failed
ch.ethz.jopera.subsystems.condor.api.CondorException: JOB SUBMISSION FAILED
Submitting job(s)

Human Adapter Worklist

ms — Sat, 27 Feb 2010 12:15:23 +0000

Hey there,

for all of you using Safari on a Mac. Unfortunately the Login-Page does not work on my Mac using Safari 4?
It works fine using Firefox though.

The JavaScript Errormessage is:
SyntaxError: Parse error --> :8080/worklist/ajax/scripts/scripts.js:11SyntaxError: Parse error
ReferenceError: Can't find variable: onLoad --> ajax:10

Regards
Malte

Problem using a WSDL file

moissinac — Fri, 06 Nov 2009 13:30:27 +0000

I'm a trying to define a process which use a WSDL
I've copied a sample one in an accessible place
http://paam-itengine.appspot.com/Text.wsdl

This WSDL is well used by a BPEL process in ODE and seems to be correct in the XMethods analyser.

Following the Web Service Tutorial, I'm in the 4.6 step. But when I try to drag a 'program' -here 'SOAP_translate'- in my process, nothing happens.

Any idea?

INVOKE and WSIF have an invalid component-type reference... in 2.4.1 on Ganymede

shayanlinux — Mon, 24 Nov 2008 22:08:18 +0000

I installed all components of JOpera 2.4.1 on Eclipse Ganymede, but unfortunately I don't have components like INVOKE, REPLY, RECIEVE, WSIF... in component browser.

When creating a project and importing one of the Web Service examples, I get following errors:

Adapter "INVOKE" has an invalid Component-Type reference: system.router.CT_INVOKE ws_quiz.oml joperatest1 getCorrectAnswerForQuestionById.INVOKE JOpera Problem

Two small bugs (automated code generation) and one remark (Help section)

lmir — Thu, 13 Mar 2008 07:43:47 +0000

Bug No. 1

For the imported web service a special class is generated that starts with the definition of a package.
Note a dot (.) in the end of the following line (before the colon):
package ws.localhost.helloWorldTest_HelloWorld1.;

Bug No. 2
The fact that java code is generated in one loooong line without breaks ("\n") makes the reading difficult.

//JOpera Program Template Plugin
//OML2Java Compiler Version 1.10 $Revision: 2525 $