"maeste" wrote:

6. Starting server side development (or better investigation of its feasibility) . In a nutshell I have in mind a similar approach we are using to develop WS client also to deploy WS service modifying classes and introducing annotation. This idea could be interesting if we can provide an easy way to deploy service based on classes existing only runtime (aka smooks generated) or classes wrapping scripting language. Have I gotten you the idea? Please ask and/or discuss this point.

"maeste" wrote:

8. Invocation starting from other sources than Java classes (i.e csv or EDI file) using Smooks features. It isn't just a sample, because, even if Smooks support these transformation out of the box, we need some support to support iterative invocation of Wise client. This point could be a subtask of point 9
9. Wise as Smooks Visitor.

"maeste" wrote:

2. Add other WS-* implementation to support all WS-* supported by jbossws or related JBoss projects (ie WS-RM, WS-Transaction...please don't consider WS-Eventing I had too much pain with it ;))

3. Finish JAX-RS implementation (some issues opened by Jervis) and complete JAX-RS sample
4. Project cleanup (some issues opened related to maven and docbook). In particular I think it need to be mavenized since it have too much dependencies and their maintenance could easy become full of pain.
5. More samples. It would demonstarte advanced using with complex wsdls and complex smooks transformation. It would be good to have also some samples demonstrating possible other integration, ie with seam or Jython. A bit more unit tests too.

6. Starting server side development (or better investigation of its feasibility) . In a nutshell I have in mind a similar approach we are using to develop WS client also to deploy WS service modifying classes and introducing annotation. This idea could be interesting if we can provide an easy way to deploy service based on classes existing only runtime (aka smooks generated) or classes wrapping scripting language. Have I gotten you the idea? Please ask and/or discuss this point.

7. Issue LMS related on Jira opened by Alessio
8. Invocation starting from other sources than Java classes (i.e csv or EDI file) using Smooks features. It isn't just a sample, because, even if Smooks support these transformation out of the box, we need some support to support iterative invocation of Wise client. This point could be a subtask of point 9
9. Wise as Smooks Visitor.

That's all for the moment.
Any thoughts are more than welcome

"maeste" wrote:

"mark.little@jboss.com" wrote:

"maeste" wrote:


6. Starting server side development (or better investigation of its feasibility) . In a nutshell I have in mind a similar approach we are using to develop WS client also to deploy WS service modifying classes and introducing annotation. This idea could be interesting if we can provide an easy way to deploy service based on classes existing only runtime (aka smooks generated) or classes wrapping scripting language. Have I gotten you the idea? Please ask and/or discuss this point.

How would that relate to JSR 181?

Well, JSR-181 define annotation to be used to expose a class as webservice. And of course you need to put them in your source code. What I'm purposing is to introduce these annotations runtime on compiled classes. Why? for example to expose a class you haven't source code as a webservice.
Another things doable with the same approach is to generate also exposed classes runtime for example to wrap a Ruby script or to expose a dynamic generated object model to be passed to a smooks transformation to route, split, or merge it using smooks itself.
Of course is just a brainstorming at the moment, but I'm pretty sure these things are doable.

import javax.jws.WebService;

@WebService
public class MyService {

 public String hello(final String text) {
 return text;
 }

}


import javax.xml.ws.Endpoint;

public class Main {

 private static final int PORT = 58888;

 public static void main(String[] args) {
 Endpoint endpoint = Endpoint.create(new MyService());
 endpoint.publish("http://localhost:" + PORT + "/");
 }
}

"maeste" wrote:

4. Project cleanup (some issues opened related to maven and docbook). In particular I think it need to be mavenized since it have too much dependencies and their maintenance could easy become full of pain.

5. More samples. It would demonstarte advanced using with complex wsdls and complex smooks transformation. It would be good to have also some samples demonstrating possible other integration, ie with seam or Jython. A bit more unit tests too.

"alessio.soldano@jboss.com" wrote:

Well, Stefano already knows this... I like this point 6 ;-)

Perhaps you already know, but JAXWS Endpoint API makes this even more interesting, as you're already able to programmatically deploy a webservice endpoint on the fly given an endpoint implementation instance (see https://jax-ws.dev.java.net/nonav/2.1.2m1/docs/endpoint.html):

import javax.jws.WebService;

@WebService
public class MyService {

 public String hello(final String text) {
 return text;
 }

}


import javax.xml.ws.Endpoint;

public class Main {

 private static final int PORT = 58888;

 public static void main(String[] args) {
 Endpoint endpoint = Endpoint.create(new MyService());
 endpoint.publish("http://localhost:" + PORT + "/");
 }
}

Perhaps some efforts on this point 6 could lead to something interesting...

Ah, I was looking at specific issues and forgot to cast my +1 on point 1 too, ie. the webgui, as that would restore the fuctionality that was one of the original purpose of Wise ;-)