Summary

• Page properties (3 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Discontinued Projects

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.msp
	1	+XWiki.uru

Content

...	...	@@ -1,16 +1,12 @@
1		-{{panel title="Project Overview" borderStyle="dashed"}}
2		-Responsible:
3		-
4		-* {{mention reference="XWiki.uru" style="FULL_NAME" anchor="XWiki-uru-JLVfO"/}}
5		-
	1	+{{panel borderStyle="dashed" title="Project Overview"}}
6	6	Related Theses:
7	7
8	8	* Stephan Wersig, //Ein Web Service für das automatische Layout von Graphen//, October 2011 ([[pdf>>url:http://rtsys.informatik.uni-kiel.de/%7Ebiblio/downloads/theses/swe-dt.pdf||shape="rect"]])
9	9	{{/panel}}
10	10
11		-
	7	+\\
12	12
13		-The KWebS project aims at delivering the automatic layout of the KIELER project to users on a platform independent basis. The main component of the project is the //server//. It is based on an Eclipse Rich Client Application (RCA) and encapsulates the KIELER Infrastructure for Meta Layout ([[KIML>>doc:Infrastructure for Meta Layout (KIML)]]) in order to expose the layout over a network. To make the layout accessible for other platforms, the server hides the java nature of the layout behind a web service and supports a variety of //formats// for the representation of user models. The server provides access to the layout based on two architectures:
	9	+The KWebS project aims at delivering the automatic layout of the KIELER project to users on a platform independent basis. The main component of the project is the //server//. It is based on an Eclipse Rich Client Application (RCA) and encapsulates the KIELER Infrastructure for Meta Layout ([[KIML>>doc:KIELER.Home.Discontinued Projects.Infrastructure for Meta Layout (KIML).WebHome]]) in order to expose the layout over a network. To make the layout accessible for other platforms, the server hides the java nature of the layout behind a web service and supports a variety of //formats// for the representation of user models. The server provides access to the layout based on two architectures:
14	14
15	15	* the HTTP-based service which uses simple POST requests to retrieve the layout. We provide several language bindings to connect from any language.
16	16	* the SOAP web service uses the reference implementation of the //Java API for XML - Web Services (JAX-WS)//, which is being maintained by the Metro project ([[jax-ws.java.net>>url:http://jax-ws.java.net/||shape="rect"]]), and provides the layout on a sessionless basis
...	...	@@ -18,7 +18,7 @@
18	18
19	19	The following subpages first show how we can download and set up a layout server on our own, e.g. to provide layout inside a companies network. Further pages discuss the specific properties of either the SOAP- or HTTP-based solution. There is also a page on the supported graph formats.
20	20
21		-
	17	+\\
22	22
23	23	Then we get to know the API provided by KWebS, after which the integration of the service-based layout with KWebS into our own projects is discussed. The last section gives us a list of configuration options supported by the server of KWebS.
24	24

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-40075290
	1	+328093

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/40075290/Web Services (KWebS)
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/328093/Web Services (KWebS)