----- Original Message -----
From: "Alessio Soldano" <asoldano(a)redhat.com>
To: wildfly-dev(a)lists.jboss.org
Sent: Thursday, September 1, 2016 3:40:52 AM
Subject: Re: [wildfly-dev] question 2 sec boot time of WISE
Il 01/09/2016 01:12, Jason T. Greene ha scritto:
> On the other hand i suspect this relies on CXF to generate the client
> side messages, so perhaps it would be a complex transition.
CXF is needed to generate the SOAP message on "client" side. But that
could still run on the server. What needs to be on the actual client
(browser) is the generation of the graphical representation of the
message. IOW, the user is not presented with a static page, but with
something that 1) depends on the previously selected service endpoint 2)
depends on how the user interacts with it (for example, say you have
arrays of complex types in the schema, the user can add and remove items
in the array and the page has to show the proper structure). The core of
the application generates a generic tree view of the request message,
which is modifiable according to the schema constraints (allowed types,
optional items, complex structures, collections, etc.); the GUI allows
the user to fill in data into that tree and modify it before eventually
pressing the invoke button and hence telling the core to convert the
tree back into actual arguments to make the ws invocation.
Not sure this fits with your concept of serving just static files, but
I'll let Rebecca comment here as she's worked on the GUI.
I'm assuming its the gwt-servlet that is taking most the bootup time.
I don't see that Wise can have a lot of static code. I'm investigating
using the restyGWT api to see if that can resolve some of these issues.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev