Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERJaxWS examples #558

Merged
merged 15 commits into from
Apr 20, 2014
Merged

ERJaxWS examples #558

merged 15 commits into from
Apr 20, 2014

Conversation

markusstoll
Copy link
Contributor

Hi,

Ray Kiddy notified me, that my supplied examples were not compiling by default

I recreated the examples using Java 6 (rather than Java 7), using proper package names,
making them run out of the box and added them to the build.xml files to be compiled by default.

I also added the proper license files for ERJaxWS

There is just one drawback. Framework and examples won't compile and run with JDK5. I became unsure
which JDK is used for the automated builds (and I could not find a doc about that).
If JDK5 still is a must, we have to talk about how to handle this. We would have to go back to
an older JaxWS version, which hardly makes sense…

Markus

@ghost
Copy link

ghost commented Apr 16, 2014

With Java 8 out, maintaining support for JDK 5 makes little sense to me.

@pascalrobert
Copy link
Contributor

And since at WOWODC, most people said that they use their own fork, it shouldn't affect many people.

----- Mail original -----

De: "Chuck Hill" notifications@github.com
À: "wocommunity/wonder" wonder@noreply.github.com
Envoyé: Mercredi 16 Avril 2014 15:50:43
Objet: Re: [wonder] ERJaxWS examples (#558)

With Java 8 out, maintaining support for JDK 5 makes little sense to me.


Reply to this email directly or view it on GitHub .

ishimoto added a commit that referenced this pull request Apr 20, 2014
pulled because the current Version didn't compile anyway
@ishimoto ishimoto merged commit 8e901af into wocommunity:master Apr 20, 2014
@hprange
Copy link
Contributor

hprange commented Apr 24, 2014

@markusstoll Would you mind to provide the version of the libraries required by the ERJaxWS framework? I'm working in the Maven configuration and this kind of information would be very helpful.

Also, the WebService_Stateful project references a testservice.jar generated from a WSDL file. Could you provide the WSDL file? That way I can write the required Maven configuration to run the wsimport on every build to generate the required classes.

@markusstoll markusstoll deleted the ERJaxWS branch April 25, 2014 08:58
@markusstoll
Copy link
Contributor Author

Hi,

I have no idea about maven, so thanks for taking care of that.

ERJaxWS includes all libraries from Jax WS RI 2.1.10 (which is basically still JDK5 compliant)
excluding the src jar.

WebService_Stateful includes the referenced testservice.jar as well. Why would you want to
recreate it. However attached you find the two files that should work for wsimport.
I will be glad to assisst, if you run into problems.

regards, Markus

Am 25.04.2014 um 00:01 schrieb Henrique Prange notifications@github.com:

@markusstoll Would you mind to provide the version of the libraries required by the ERJaxWS framework? I'm working in the Maven configuration and this kind of information would be very helpful.

Also, the WebService_Stateful project references a testservice.jar generated from a WSDL file. Could you provide the WSDL file? That way I can write the required Maven configuration to run the wsimport on every build to generate the required classes.


Reply to this email directly or view it on GitHub.

@hprange
Copy link
Contributor

hprange commented Apr 25, 2014

Generating the code during the build is the recommended way of doing this with Maven. The good side effect is that the generated classes are going to be compiled with the correct JDK used during the build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants