Hello, I try to implement a Java WebServiceClient which uses OTRS WebServices. Have anybody experience in implementing a Java WebServiceClient for OTRS or an example? Greetings Christoph
Hi Christoph, On Apr 18, 2008, at 12:47 , Christoph Nagel wrote:
I try to implement a Java WebServiceClient which uses OTRS WebServices.
Have anybody experience in implementing a Java WebServiceClient for OTRS or an example?
Me not. Only by using perl or .net. Greetings, -Martin -- ((otrs)) :: OTRS AG :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success! Address of record: Bad Homburg Local Court: Bad Homburg, HRB 10751 Tax number: 003/240/97505 Chairman: Burchard Steinbild Chief Executive Officer: André Mindermann
Hi Martin, can you send me a sample of a .net Client? Greetings, Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von Martin Edenhofer Gesendet: Samstag, 19. April 2008 13:39 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS Hi Christoph, On Apr 18, 2008, at 12:47 , Christoph Nagel wrote:
I try to implement a Java WebServiceClient which uses OTRS WebServices.
Have anybody experience in implementing a Java WebServiceClient for OTRS or an example?
Me not. Only by using perl or .net. Greetings, -Martin -- ((otrs)) :: OTRS AG :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success! Address of record: Bad Homburg Local Court: Bad Homburg, HRB 10751 Tax number: 003/240/97505 Chairman: Burchard Steinbild Chief Executive Officer: André Mindermann _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Christoph Nagel (christoph.nagel@xenovation.com) wrote:
I try to implement a Java WebServiceClient which uses OTRS WebServices.
Have anybody experience in implementing a Java WebServiceClient for OTRS or an example?
Hi, yes, I did that - more or less. I implemented my own SOAP interface to OTRS using SOAP::Lite and Pod::WSDL. That way I thought it would be easy to give different systems access to OTRS, regardless whether they're written in PHP, Java, perl or some .Net dialect. But SOAP::Lite and Pod::WSDL don't play together very well, and they don't support the document/literal wrapped style. On the Java'ish client side I used Jax-WS. It comes with a generator that creates stubs from a (remote) WSDL file. That all works if one uses simple types like strings or integers and avoids complex stuff like structs/classes or even arrays of these types. Felix
Hi Felix, were do I get the WSDL File? Have you write one? Greetings, Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von Felix J. Ogris Gesendet: Samstag, 19. April 2008 18:29 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS Christoph Nagel (christoph.nagel@xenovation.com) wrote:
I try to implement a Java WebServiceClient which uses OTRS WebServices.
Have anybody experience in implementing a Java WebServiceClient for OTRS or an example?
Hi, yes, I did that - more or less. I implemented my own SOAP interface to OTRS using SOAP::Lite and Pod::WSDL. That way I thought it would be easy to give different systems access to OTRS, regardless whether they're written in PHP, Java, perl or some .Net dialect. But SOAP::Lite and Pod::WSDL don't play together very well, and they don't support the document/literal wrapped style. On the Java'ish client side I used Jax-WS. It comes with a generator that creates stubs from a (remote) WSDL file. That all works if one uses simple types like strings or integers and avoids complex stuff like structs/classes or even arrays of these types. Felix _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Christoph Nagel (christoph.nagel@xenovation.com) wrote:
were do I get the WSDL File? Have you write one?
Nope, Pod::WSDL creates them on the fly from embedded perl documentation. So you have to write 2 modules at least. The one which does all the SOAP <-> OTRS stuff, and the one which creates WSDL from the former module. Of course you can provide a static WSDL or even write it manually. Felix
On 21 Apr 2008, at 15:04, Felix J. Ogris wrote:
Christoph Nagel (christoph.nagel@xenovation.com) wrote:
were do I get the WSDL File? Have you write one?
Nope, Pod::WSDL creates them on the fly from embedded perl documentation. So you have to write 2 modules at least. The one which does all the SOAP <-> OTRS stuff, and the one which creates WSDL from the former module. Of course you can provide a static WSDL or even write it manually.
I'd echo everyone else's comments on this. See the thread I started around 10th this month. This also explains why I couldn't use the SOAP::Lite autodispatch mechanism in rpc.pl. My approach so far has been to wrap the otrs objects I want with some code to properly format the output of a few methods as SOAP messages. I coded the WSDL by hand. Apache AXIS it seems to swallow the complex types and arrays that I have created thus far. My attempt is not really ready to share yet. But I will do as soon as it is. Cheers ... Jonathan.
Have anybody a WSDL for the rpc.example? Best wishes Christoph
On 22 Apr 2008, at 18:12, Christoph Nagel wrote:
Have anybody a WSDL for the rpc.example?
Hi Christoph, did you see my earlier mail in this thread? The interface provided by rpc.pl allow yous to call any otrs method, however it only works simply with a Perl SOAP::Lite client. If you want to use one of the many (Java, .net, whatever) SOAP libraries that will generate client classes for you, you need, as you say WSDL (which isn't available). Equally importantly, you need the returned messages to be formatted according to a defined schema to match that WSDL. Here's a fragment of output from a TicketGet request using rpc.pl and a SOAP::Lite client (though it doesn't really matter, the client could be anything). soap:Body <DispatchResponse xmlns="/Core"> <s-gensym87 xsi:type="xsd:string">TicketID</s-gensym87> <s-gensym89 xsi:type="xsd:int">33</s-gensym89> <s-gensym247 xsi:type="xsd:string">TicketNumber <s-gensym249 xsi:type="xsd:long">2008042210000212 . . . etc... </DispatchResponse> What you really want is something like: soap:Body <TicketGetByIDResponse xmlns="http://otrs.org/Kernel/ Modules/TicketService"> <Ticket xsi:type="tns:Ticket" xmlns:tns="http://otrs.org/ otrs/Kernel/Modules/TicketService"> <TicketID xsi:type="xsd:int">33</TicketID> <TicketNumber xsi:type="xsd:long">2008042210000212 . . . etc... </Ticket> </TicketGetByIDResponse> See the difference? The first example returns an array of results from the called method. The second has a defined schema. So, as far as I understand, if you are to have WSDL and autogenerated client classes to access OTRS, you need to encapsulate the OTRS classes you require in some additional code and generate your WSDL to match the returned messages from your new classes. This does not yet exist. Of course, if you have a perl client, you can use SOAP::Lite and get back a blessed hash to do pretty much anything you like. Does that help? .... J
Hey Jonathan,
I have implemented an axis Client which sends the following SOAP message!
It's like the same such as the rpc example SOAP message for
TicketCreateNumber.
I can send the message but I get this failure "Transport error: 411 Error:
Length Required"
Have you any idea what can be wrong?
<?xml version="1.0" encoding="http://schemas.xmlsoap.org/soap/envelope/"
standalone="no"?>
On 22 Apr 2008, at 18:12, Christoph Nagel wrote:
Have anybody a WSDL for the rpc.example?
Hi Christoph, did you see my earlier mail in this thread? The interface provided by rpc.pl allow yous to call any otrs method, however it only works simply with a Perl SOAP::Lite client. If you want to use one of the many (Java, .net, whatever) SOAP libraries that will generate client classes for you, you need, as you say WSDL (which isn't available). Equally importantly, you need the returned messages to be formatted according to a defined schema to match that WSDL. Here's a fragment of output from a TicketGet request using rpc.pl and a SOAP::Lite client (though it doesn't really matter, the client could be anything). soap:Body <DispatchResponse xmlns="/Core"> <s-gensym87 xsi:type="xsd:string">TicketID</s-gensym87> <s-gensym89 xsi:type="xsd:int">33</s-gensym89> <s-gensym247 xsi:type="xsd:string">TicketNumber <s-gensym249 xsi:type="xsd:long">2008042210000212 . . . etc... </DispatchResponse> What you really want is something like: soap:Body <TicketGetByIDResponse xmlns="http://otrs.org/Kernel/ Modules/TicketService"> <Ticket xsi:type="tns:Ticket" xmlns:tns="http://otrs.org/ otrs/Kernel/Modules/TicketService"> <TicketID xsi:type="xsd:int">33</TicketID> <TicketNumber xsi:type="xsd:long">2008042210000212 . . . etc... </Ticket> </TicketGetByIDResponse> See the difference? The first example returns an array of results from the called method. The second has a defined schema. So, as far as I understand, if you are to have WSDL and autogenerated client classes to access OTRS, you need to encapsulate the OTRS classes you require in some additional code and generate your WSDL to match the returned messages from your new classes. This does not yet exist. Of course, if you have a perl client, you can use SOAP::Lite and get back a blessed hash to do pretty much anything you like. Does that help? .... J _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On 23 Apr 2008, at 19:25, Christoph Nagel wrote: <snip/>
Have you any idea what can be wrong?
Not immediately, have you tried altering the endpoint in the perl example to pass it through axis utils tcpmon and comparing the difference in request/response from your client's request/response? .... J
Hello all, I am also watching the SOAP discussions. It is funny to see, that many people have same troubles with OTRS via SOAP. Wouldn't it be easier for everyone in the OTRS ML, if WSDLs for at least the rpc-example.pl would be available? I cannot imagine, that it is so complex under perl, to generate the standard WSDL, which could be uses for many other systems (.net, Java, C++, ...) Sorry for my really odd reaction, but this topic pop ups very often on this list and in my opinion without any solution. Wouldn't a WSDL corresponding to the rpc-example.pl be easy from perl to define? Every side would profit from this! Regards, Hans
-----Original Message----- From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] On Behalf Of jonathan sartin Sent: Saturday, April 26, 2008 12:37 AM To: Development community of OTRS.org Subject: Re: [dev] Java WebServiceClient for OTRS
On 23 Apr 2008, at 19:25, Christoph Nagel wrote:
<snip/>
Have you any idea what can be wrong?
Not immediately, have you tried altering the endpoint in the perl example to pass it through axis utils tcpmon and comparing the difference in request/response from your client's request/response?
.... J _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On 29 Apr 2008, at 07:23, Kaiser, Hans wrote:
Hello all,
I am also watching the SOAP discussions. It is funny to see, that many people have same troubles with OTRS via SOAP.
Wouldn't it be easier for everyone in the OTRS ML, if WSDLs for at least the rpc-example.pl would be available? I cannot imagine, that it is so complex under perl, to generate the standard WSDL, which could be uses for many other systems (.net, Java, C+ +, ...)
Sorry for my really odd reaction, but this topic pop ups very often on this list and in my opinion without any solution. Wouldn't a WSDL corresponding to the rpc-example.pl be easy from perl to define? Every side would profit from this!
Absolutely Hans, I've been following this too. You probably need to read my previous posts as to why it's not entirely trivial though. If it was, you'd have already done it, right ;-) The example in the distribution creates a ticket number. I suspect you're going to want to do something a little more than that (like create a ticket or an article). Cheers ... Jonathan.
I am also watching the SOAP discussions. It is funny to see, that many people have same troubles with OTRS via SOAP.
Wouldn't it be easier for everyone in the OTRS ML, if WSDLs for at least the rpc-example.pl would be available? I cannot imagine, that it is so complex under perl, to generate the standard WSDL, which could be uses for many other systems (.net, Java, C+ +, ...)
Sorry for my really odd reaction, but this topic pop ups very often on this list and in my opinion without any solution. Wouldn't a WSDL corresponding to the rpc-example.pl be easy from perl to define? Every side would profit from this!
I've been following this too. You probably need to read my previous posts as to why it's not entirely trivial though. If it was, you'd have already done it, right ;-)
The example in the distribution creates a ticket number. I suspect you're going to want to do something a little more than that (like create a ticket or an article).
It would be easier for everyone if the existing code, in this case the rpc-example.pl, wouldn't be so magic. To be more precise, if someone could see the working rpc-example.pl and the corresponding WSDLs, the bootstrapping in the OTRS_SOAP-MyApp-project would be much much easier. Therefore I suggest, to generate (e.g. manually) WSDLs for the rpc-example.pl. All other WSDLs would be a nice to have and could be done later. Best regards, Hans
Hi Hans..
It would be easier for everyone if the existing code, in this case the rpc-example.pl, wouldn't be so magic.
It's magic because SOAP::Lite clients can deserialise the messages into a blessed hash that you can treat as an object on the client side. So with SOAP::Lite on each end you have no need for wsdl so long as you know your object's interface. Also in the absence of interface or type information from Perl, there isn't a simple way of automatically generating reasonable WSDL (or accurately setting the types for the returned elements, come to that - SOAP::Lite will guess, but it's often wrong). Anyway....
To be more precise, if someone could see the working rpc-example.pl and the corresponding WSDLs, the bootstrapping in the OTRS_SOAP-MyApp- project would be much much easier.
I agree. And if you hold on for a few days, I'll tidy up the work that I have done on Tickets and Articles and let it loose for your scrutiny ;-)
Therefore I suggest, to generate (e.g. manually) WSDLs for the rpc-example.pl. All other WSDLs would be a nice to have and could be done later.
Hopefully this will help you in that respect too. But really, properly formatting SOAP messages and WSDL for consumption by other clients using SOAP::Lite is not trivial. Did you see this one: http://www.pfconrey.com/programming/soap/interop.shtml It's in the nature of Open Source projects to only gain capabilities when someone needs them badly enough. I'm just traveling the same path as you ;-) Cheers ... J
On 29 Apr 2008, at 22:10, jonathan sartin wrote:
Hi Hans..
<snip/>
To be more precise, if someone could see the working rpc- example.pl and the corresponding WSDLs, the bootstrapping in the OTRS_SOAP-MyApp- project would be much much easier.
I agree. And if you hold on for a few days, I'll tidy up the work that I have done on Tickets and Articles and let it loose for your scrutiny ;-)
Therefore I suggest, to generate (e.g. manually) WSDLs for the rpc-example.pl. All other WSDLs would be a nice to have and could be done later.
As promised. It's not wsdl for the rpc-example.pl, but I have tested it with AXIS 1.4 (my requirement). You can use this module and wsdl for creating and retrieving simple tickets/articles. Hope this helps with your project: http://sartin.woaf.net/OpenNMS-OTRSIntegration/ Comments, corrections and suggestions are very welcome. Consider this alpha quality code. I take zero responsibility for any impact this module might have on a running OTRS installation. It meets my requirement for creating and retrieving basic ticket and article data using java/axis and is not intended to meet any other use case that you might have. Cheers ... J
jonathan sartin (jonathan@opennms.org) wrote:
It's not wsdl for the rpc-example.pl, but I have tested it with AXIS 1.4 (my requirement). You can use this module and wsdl for creating and retrieving simple tickets/articles.
Hi, rpc/encoded works with Axis? I'd prefer document/literal (wrapped) as rpc/encoded is not WS-I compliant. I also have problems importing it into MS VisualStudio (stubs aren't generated). BTW: You have to change the port address from "http://localhost/otrs/opennms.pl" to whatever your local hostname is. Regards, Felix
Hi Felix, have you solved the problem importing the web service to MS Visual Studio? I also have problems importing the webservice into eclipse. Regards, Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von Felix J. Ogris Gesendet: Freitag, 9. Mai 2008 09:41 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS jonathan sartin (jonathan@opennms.org) wrote:
It's not wsdl for the rpc-example.pl, but I have tested it with AXIS 1.4 (my requirement). You can use this module and wsdl for creating and retrieving simple tickets/articles.
Hi, rpc/encoded works with Axis? I'd prefer document/literal (wrapped) as rpc/encoded is not WS-I compliant. I also have problems importing it into MS VisualStudio (stubs aren't generated). BTW: You have to change the port address from "http://localhost/otrs/opennms.pl" to whatever your local hostname is. Regards, Felix _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Hi Jonathan, have you tested the WSDL with Axis2 1.4 or Axis 1.4? Regards Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von jonathan sartin Gesendet: Freitag, 9. Mai 2008 00:10 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS On 29 Apr 2008, at 22:10, jonathan sartin wrote:
Hi Hans..
<snip/>
To be more precise, if someone could see the working rpc- example.pl and the corresponding WSDLs, the bootstrapping in the OTRS_SOAP-MyApp- project would be much much easier.
I agree. And if you hold on for a few days, I'll tidy up the work that I have done on Tickets and Articles and let it loose for your scrutiny ;-)
Therefore I suggest, to generate (e.g. manually) WSDLs for the rpc-example.pl. All other WSDLs would be a nice to have and could be done later.
As promised. It's not wsdl for the rpc-example.pl, but I have tested it with AXIS 1.4 (my requirement). You can use this module and wsdl for creating and retrieving simple tickets/articles. Hope this helps with your project: http://sartin.woaf.net/OpenNMS-OTRSIntegration/ Comments, corrections and suggestions are very welcome. Consider this alpha quality code. I take zero responsibility for any impact this module might have on a running OTRS installation. It meets my requirement for creating and retrieving basic ticket and article data using java/axis and is not intended to meet any other use case that you might have. Cheers ... J _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On 30 May 2008, at 10:51, Christoph Nagel wrote:
Hi Jonathan,
have you tested the WSDL with Axis2 1.4 or Axis 1.4?
Works for me with AXIS 1.4 (I have other dependencies on 1.4). I'm using the wsdl2java ant target and which generates stubs just fine. Sorry to be a bit terse, but I'm kind of busy with the day job right now ;-). Sometime I'll package all this up more neatly, but for now I'm rather out of time. BTW, code has moved to http://opennms.svn.sourceforge.net/viewvc/ opennms/otrs-opennms/ Cheers ... J
On 30 May 2008, at 12:08, jonathan sartin wrote:
On 30 May 2008, at 10:51, Christoph Nagel wrote:
Hi Jonathan,
have you tested the WSDL with Axis2 1.4 or Axis 1.4?
Works for me with AXIS 1.4 (I have other dependencies on 1.4). I'm using the wsdl2java ant target and which generates stubs just fine. Sorry to be a bit terse, but I'm kind of busy with the day job right now ;-). Sometime I'll package all this up more neatly, but for now I'm rather out of time.
BTW, code has moved to http://opennms.svn.sourceforge.net/viewvc/ opennms/otrs-opennms/
Ah, read the AXIS 2 docs. You don't really want rpc/encoded, do you ;-) (fair point felix). So, here's your choice. 1. Use Axis 1.4 and put up with the rpc/encoded nastiness for now. 2. Wait for me to fix it (could be a few weeks - I'm out of time on this for now). 3. Fix it yourself. Cheers ... J
Hi, Has anybody a proposal how I can search for tickets? SOAP only provides search by TicketID. For example, I want to search by Title. Regards Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von jonathan sartin Gesendet: Freitag, 30. Mai 2008 14:11 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS On 30 May 2008, at 12:08, jonathan sartin wrote:
On 30 May 2008, at 10:51, Christoph Nagel wrote:
Hi Jonathan,
have you tested the WSDL with Axis2 1.4 or Axis 1.4?
Works for me with AXIS 1.4 (I have other dependencies on 1.4). I'm using the wsdl2java ant target and which generates stubs just fine. Sorry to be a bit terse, but I'm kind of busy with the day job right now ;-). Sometime I'll package all this up more neatly, but for now I'm rather out of time.
BTW, code has moved to http://opennms.svn.sourceforge.net/viewvc/ opennms/otrs-opennms/
Ah, read the AXIS 2 docs. You don't really want rpc/encoded, do you ;-) (fair point felix). So, here's your choice. 1. Use Axis 1.4 and put up with the rpc/encoded nastiness for now. 2. Wait for me to fix it (could be a few weeks - I'm out of time on this for now). 3. Fix it yourself. Cheers ... J _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Hey, I get the following Error when I try to get articles by ticketID. org.xml.sax.SAXParseException: Premature end of file. Have anybody an idea what can be wrong? Thanks Christoph -----Ursprüngliche Nachricht----- Von: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] Im Auftrag von jonathan sartin Gesendet: Freitag, 30. Mai 2008 14:11 An: Development community of OTRS.org Betreff: Re: [dev] Java WebServiceClient for OTRS On 30 May 2008, at 12:08, jonathan sartin wrote:
On 30 May 2008, at 10:51, Christoph Nagel wrote:
Hi Jonathan,
have you tested the WSDL with Axis2 1.4 or Axis 1.4?
Works for me with AXIS 1.4 (I have other dependencies on 1.4). I'm using the wsdl2java ant target and which generates stubs just fine. Sorry to be a bit terse, but I'm kind of busy with the day job right now ;-). Sometime I'll package all this up more neatly, but for now I'm rather out of time.
BTW, code has moved to http://opennms.svn.sourceforge.net/viewvc/ opennms/otrs-opennms/
Ah, read the AXIS 2 docs. You don't really want rpc/encoded, do you ;-) (fair point felix). So, here's your choice. 1. Use Axis 1.4 and put up with the rpc/encoded nastiness for now. 2. Wait for me to fix it (could be a few weeks - I'm out of time on this for now). 3. Fix it yourself. Cheers ... J _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On 16 Jun 2008, at 12:02, Christoph Nagel wrote:
Hey,
I get the following Error when I try to get articles by ticketID.
org.xml.sax.SAXParseException: Premature end of file.
Have anybody an idea what can be wrong?
Check out the apache error_log. Do you have use SOAP::DateTime installed? TicketService uses it. .... J
Hello List, Kaiser, Hans schrieb:
Hello all,
I am also watching the SOAP discussions. It is funny to see, that many people have same troubles with OTRS via SOAP.
Wouldn't it be easier for everyone in the OTRS ML, if WSDLs for at least the rpc-example.pl would be available?
That would be absolutly great! I ran into that problem a while ago, too (and gave up). Just some working proof of concept with the example perl script would be very nice. I guess quite a few people were looking, are looking and will look for this. Just my 2 cent. ;)
participants (7)
-
Christoph Nagel -
Christoph Nagel -
Felix J. Ogris -
jonathan sartin -
Kaiser, Hans -
Martin Edenhofer -
ml＠bortal.de