Overwriting WSDL on EAP and Wildfly
by Gytis Trikleris
Hello,
I am trying to make wsat-simple quickstart (
https://github.com/wildfly/quickstart/tree/master/wsat-simple) to work
on two Wildfly servers (one as a client, another as a server). For the
client I use 127.0.0.2 and for the server 127.0.0.3 IP addresses. I
changed client WSDL to call 127.0.0.3 and it works fine on EAP 6.1 and
EAP6.2.Beta1. However, it does not work on Wildfly master.
I did some debugging and the main difference I found is that EAP and
Wildfly calls different constructors on client side Service
implementation (RestaurantServiceATService class). EAP uses not
parametrised constructor so the client gets initialized with my modified
WSDL i.e. makes calls to 127.0.0.3. On the other hand, Wildfly uses
parametrised constructor and passes URL to the AS generated WSDL which
makes client to make calls to the same server as it is deployed i.e.
127.0.0.2.
Is there any way to make Wildfly use WSDL from the deployment the same
way EAP does it?
Thanks,
Gytis
10 years, 8 months
Change CLI to Default to Remoting
by Darran Lofthouse
Hello all,
I am currently working on the following issue: -
https://issues.jboss.org/browse/WFLY-1664
Recent changes to the CLI mean that it is assuming unless told otherwise
that a HTTP Upgrade is going to be used when connecting to the server,
this means that command already used in scripts to connect to servers
are going to fail unless the scheme is included in the URI.
I chatted with David to see if there were any options to auto detect
this and fall back to pure Remoting if the remote side of the connection
is pure Remoting - however of the two options available they were both
fairly hacky or unreliable.
So the alternative is to drop the CLI back to assuming a pure Remoting
connection unless told otherwise.
- Calling connect or starting with -c will still use http-remoting
against the local server as that is defined in the jboss-cli.xml
- Calling connect or --controller with a host and port will assume
connecting directly to remoting.
- Users wanting HTTP upgrade to other servers will need to specify
http-remoting or https-remoting as the scheme when specifying the remote
address.
One other idea that I have had for the CLI if end users do want the
parameter to the connect command to be as short as possible is to add
multiple host aliases to the jboss-cli.xml - that way the protocol host
and port can be specified in the config and the alias passed to the
connect command. Additionally this would allow us to place different
SSL configuration against each host but.
Regards,
Darran Lofthouse.
10 years, 8 months
Re: [wildfly-dev] Configuration of statistics gathering
by Andrig Miller
Just to add to what Brian is saying. I presented a proposal for runtime statistics at the AS 8 meeting (before the name change), and I would like to see all the subsystems have a configuration option for their runtime statistics. I would also like it to be off by default.
The reason for the later, is our benchmarking efforts. We have recently discovered two areas where the runtime statistics were causing problems with performance/scalability. This is one area, hence Paul's pull request, and the other is the JCA container's statistics.
We may discover other areas too, as we continue scaling, but this is of vital importance for our efforts.
Thanks.
Andy
Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
>I'd like to get some info from the component leads responsible for WF
>subsystems.
>
>1) What statistical data does your subsystem capture (including the
>underlying libraries it integrates).
>
>2) What configuration options do you support for enabling/disabling
>statistics gathering. What's the resource address and attribute name of
>the config option?
>
>3) Is the statistic gathering enabled by default?
>
>Paul Ferraro's pull request [1] fixing JIRA [2] prompts this question,
>although it's long overdue. WF should be consistent about how we handle
>configuration of statistics gathering, so I'd like to take the
>opportunity of Paul's PR to move in that direction.
>
>Thanks for your help.
>
>--
>Brian Stansberry
>Principal Software Engineer
>JBoss by Red Hat
>
>[1] https://github.com/wildfly/wildfly/pull/5415
>[2] https://issues.jboss.org/browse/WFLY-2415
>_______________________________________________
>wildfly-dev mailing list
>wildfly-dev(a)lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/wildfly-dev
10 years, 8 months
JAX-RS Client API maven test <dependency>
by Arun Gupta
I've written a JAX-RS unit test using JAX-RS Client API:
@BeforeClass
public static void setupClass() {
Client client = ClientBuilder.newClient();
target =
client.target("http://localhost:8080/jaxrs-endpoint/webresources/fruit");
}
But its failing with the exception:
org.javaee7.jaxrs.endpoint.MyResourceTest Time elapsed: 0.124 sec <<< ERROR!
java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.glassfish.jersey.client.JerseyClientBuilder
at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103)
at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114)
at org.javaee7.jaxrs.endpoint.MyResourceTest.setupClass(MyResourceTest.java:51)
What <dependency> should be included in the test classpath so that
appropriate ClientBuilder instance is found ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
10 years, 8 months
Embeddable EJB container not starting
by Arun Gupta
Starting an embeddable EJB container as:
try (EJBContainer container =
javax.ejb.embeddable.EJBContainer.createEJBContainer()) {
...
}
gives:
javax.ejb.EJBException: No EJBContainer provider available: no
provider names had been found.
at javax.ejb.embeddable.EJBContainer.reportError(EJBContainer.java:216)
at javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:146)
at javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:102)
at org.javaee7.ejb.embeddable.MyBeanTest.testSayHello(MyBeanTest.java:80)
Which JAR contains the embeddable EJB container ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
10 years, 9 months
