[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jubula-dev] Jubula 2.0.0 - Remote control extension - Can'tdeploy the fragment

Hello Miguel,


thanks for your patience, we have investigated the issue and you are right with your assumption. This is a problem which is similar to Bug 169 [1]. A solution for this problem is to remove the signatures from the org.eclipse.jubula.rc.common_<version>.jar and org.eclipse.jubula.rc.swing_<version>.jar.

Removing the signatures is simply deleting the META-INF\ECLIPSREF.RSA and META-INF\ECLIPSREF.SF files in the jars.


For more Information and a more detailed description please read Bug 169 Comment 2 in the guidancer bugzilla[1].

Best regards,

Marvin

[1] http://bugzilla.bredex.de/169#c2


On 25.03.2013 12:57, Carlos Feal Miguel wrote:

All jars in plugins folder are signed. Is it possible that the error occurs because my jar is not signed?

 

blue_strip_201

 

Carlos Feal

CCSS Arquitectura

carlos.feal@xxxxxxxx
Albarracín 25,

28037 Madrid/SPAIN

www.atos.net

 

Atos_Olympic_Games_Logo_signature

 

From: jubula-dev-bounces@xxxxxxxxxxx [mailto:jubula-dev-bounces@xxxxxxxxxxx] On Behalf Of Carlos Feal Miguel
Sent: viernes, 22 de marzo de 2013 10:23
To: Jubula platform and tools development
Subject: Re: [jubula-dev] Jubula 2.0.0 - Remote control extension - Can'tdeploy the fragment

 

Thank you for your response.

 

I have remove “@start”.  Also, I have added a –clean option to autagent.ini (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404041#c1)

Now the AUT agent starts correctly, and I can connect the ITE to the AUT agent.

 

But now the problem is when I try to connect my AUT to the AUT agent. I get the following error:

 

 

Client.log provides a very poor information (no other log file has changed, or I have not find any more):

 

2013-03-22 09:45:15.932 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=1264]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!

2013-03-22 09:48:23.442 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=1268]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!

2013-03-22 09:57:37.013 [Worker-7] WARN  o.e.j.c.c.c.AutAgentConnection - connecting the AUT Agent failed

2013-03-22 10:00:06.856 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=1290]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!

 

 

But if I remove my fragment from server/plugins (and removing the fragment reference from the config.ini file) it works fine (start AUT agent, connect to AUT agent, connect AUT to AUT agent and test my AUT).  It`s very strange.

 

Note: The same happens without “–clean” option in autagent.ini

 

Do you need any more information?

Thanks a lot.

 

blue_strip_201

 

Carlos Feal

CCSS Arquitectura

carlos.feal@atos.net
Albarracín 25,

28037 Madrid/SPAIN

www.atos.net

 

Atos_Olympic_Games_Logo_signature

 

From: jubula-dev-bounces@xxxxxxxxxxx [mailto:jubula-dev-bounces@xxxxxxxxxxx] On Behalf Of Raimar Bühmann
Sent: jueves, 21 de marzo de 2013 16:42
To: Jubula platform and tools development
Subject: Re: [jubula-dev] Jubula 2.0.0 - Remote control extension - Can't deploy the fragment

 

Hi Miguel,

thank you for the very detailed problem reporting!

You've just found a small, but severe mistake in our extension manual: Simply remove the "@start" option when adding RC extensions as a fragment. Fragments do not have a lifecycle and hence they can not be "started" with this option.

I have filed this as an issue [1] in our bugzilla at Eclipse and I will resolve this documentation issue soon.

Best regards,
Raimar 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=404041


On 21.03.2013 11:01, Carlos Feal Miguel wrote:

Hi all,

 

I am following the new “Extension Manual 2.0.0” to migrate a component extension from version 1.3 to version 2.0 (ImplClass to fragment).

I get the error attached when I start AUT agent. (org.osgi.framework.BundleException: A fragment bundle cannot be started)

 

Steps:

-          Implement a fragment (ID host: org.eclipse.jubula.rc.swing).

-          Export the fragment (Export – Deployable plug-ins and fragments). I get a .jar file (com.atos.jubula.extension.calendario.rc_1.0.0.201303201838.jar)

-          Deploy the fragment. As I am using standalone AUT agent in a swing application (without OSGi), I’m following the next rule (page 14, second bullet): “ the standalone AUT agent by adding your fragment to its configuration”:

o   Copy – paste the .jar file into  server\plugins (maybe this is the wrong action?)

o   Append , com.atos.jubula.extension.calendario.rc@start at the end of the line starting with osgi.bundles

-          Start AUT agent, getting the error:

 

 

 

Thanks a lot and sorry for my poor English.

 

blue_strip_201

 

Carlos Feal

CCSS Arquitectura

carlos.feal@xxxxxxxx
Albarracín 25,

28037 Madrid/SPAIN

www.atos.net

 

Atos_Olympic_Games_Logo_signature

 

 

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------

_______________________________________________
jubula-dev mailing list
jubula-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jubula-dev



-- 
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
 
Tel.: +49-531-24330-0
Fax:  +49-531-24330-99
http: www.bredex.de
 
Geschäftsführer: Achim Lörke, Ulrich Obst, Andreas Vogel
Amtsgericht Braunschweig HRB 2450

 

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------

 
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------

_______________________________________________
jubula-dev mailing list
jubula-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jubula-dev


-- 
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig

Tel.: +49-531-24330-0
Fax:  +49-531-24330-99
http: www.bredex.de

Geschäftsführer: Achim Lörke, Ulrich Obst, Andreas Vogel
Amtsgericht Braunschweig HRB 2450

GIF image

PNG image

PNG image

PNG image

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature