Didn't have the chance I mean
El El sáb, 26 ene 2019 a las 13:30, Rafa Haro escribió:
> Glad to hear it! Sorry I just got to work on the surface of the problem,
> didn't have time to dedicate more time
>
> El El sáb, 26 ene 2019 a las 13:11, Karl Wright
> escribió:
>
>> I was able to get the
Glad to hear it! Sorry I just got to work on the surface of the problem,
didn't have time to dedicate more time
El El sáb, 26 ene 2019 a las 13:11, Karl Wright
escribió:
> I was able to get the wsdl->java compilation working without downloading a
> ton of additional dependencies, and with cxf
I was able to get the wsdl->java compilation working without downloading a
ton of additional dependencies, and with cxf version 2.6.2. Thanks, Rafa,
for your help in getting this far.
Karl
On Fri, Jan 25, 2019 at 4:11 PM Karl Wright wrote:
> That's one approach. I'm not thrilled with it; we
That's one approach. I'm not thrilled with it; we cannot guarantee no
client wsdl changes over time. But if there's nothing better we'll have to
live with it.
The real problem, of course, is that code generated with version X of cxf
requires runtime libraries from version X, and that's still a
I would try to be pragmatic. If those wsdl are not likely to change in the
future, I would build the client classes offline. Not sure if the generated
class are going to use further classes of cxf and then the problem could
end up being the same, but it is worth to try
El El vie, 25 ene 2019 a
I downloaded the cxf binary, latest version.
The dependency list is huge and very likely conflicts with existing
connectors which have dependencies on cxf 2.x. I would estimate that
including all the new jars and dependencies would easily double our
download footprint.
Surely there must be a
I'm not getting missing cxf jars. I'm getting problems with downstream
dependencies.
We don't usually ship more jars than we need to, is the short answer to
your second question.
Karl
On Fri, Jan 25, 2019 at 11:38 AM Rafa Haro wrote:
> which jars are you downloading?. Why not getting the
which jars are you downloading?. Why not getting the whole release?
On Fri, Jan 25, 2019 at 5:31 PM Rafa Haro wrote:
> Not sure, Karl I just picked up last release. I can try to find the first
> version offering it but as long as they have backwards compatibility we
> should be fine with the
Not sure, Karl I just picked up last release. I can try to find the first
version offering it but as long as they have backwards compatibility we
should be fine with the last version although we might need to update the
affected connectors
Rafa
On Fri, Jan 25, 2019 at 3:53 PM Karl Wright wrote:
I've been fighting with this pretty hard for a couple of hours now. I did
find the proper cxf tools jar eventually but I'm getting one dependency
problem after another. Currently I have:
>>
classcreate-wsdl-cxf:
[mkdir] Created dir:
When did it first appear? We're currently on 2.6.2; this is set by various
dependencies by our connectors.
Karl
On Fri, Jan 25, 2019 at 9:52 AM Karl Wright wrote:
> The tools package doesn't seem to have it either.
> Karl
>
>
> On Fri, Jan 25, 2019 at 9:43 AM Karl Wright wrote:
>
>> Do you
The tools package doesn't seem to have it either.
Karl
On Fri, Jan 25, 2019 at 9:43 AM Karl Wright wrote:
> Do you know what jar/maven package this is in? because I don't seem to
> have it in our normal cxf jars...
>
> Karl
>
>
> On Fri, Jan 25, 2019 at 9:08 AM Rafa Haro wrote:
>
>> I used a
Do you know what jar/maven package this is in? because I don't seem to
have it in our normal cxf jars...
Karl
On Fri, Jan 25, 2019 at 9:08 AM Rafa Haro wrote:
> I used a wsdl2java script that comes as an utility of the apache cxf
> release, but basically is making use
> of
I used a wsdl2java script that comes as an utility of the apache cxf
release, but basically is making use
of org.apache.cxf.tools.wsdlto.WSDLToJava class. You can find here an usage
example with ant: http://cxf.apache.org/docs/wsdl-to-java.html
On Fri, Jan 25, 2019 at 2:59 PM Karl Wright wrote:
The cxf stuff is already present, and is available in connector-common-lib
as well, so all that might be needed might be a new ant rule to invoke it:
01/17/2019 05:47 PM 1,400,339 cxf-core-3.2.6.jar
01/17/2019 05:46 PM 181,690 cxf-rt-bindings-soap-3.2.6.jar
01/17/2019 05:46
I was using ancient Axis 1.4 and none of them were working. You can
exercise this with "ant classcreate-wsdls" in the csws directory.
If you can give instructions for invoking CXF, maybe we can do that
instead. What's the main class, and what jars do we need to include?
Karl
On Fri, Jan 25,
Yes, I did. I have only tested Authentication service with Apache CXF and
it was apparently working fine. Which ones were failing for you?
On Fri, Jan 25, 2019 at 12:38 PM Karl Wright wrote:
> Were you able to look at this yesterday at all?
> Karl
>
> On Thu, Jan 24, 2019 at 6:34 AM Karl Wright
Were you able to look at this yesterday at all?
Karl
On Thu, Jan 24, 2019 at 6:34 AM Karl Wright wrote:
> They're all checked in.
>
> See
> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1566/connectors/csws/wsdls
>
> Karl
>
>
> On Thu, Jan 24, 2019 at 6:24 AM Rafa Haro wrote:
They're all checked in.
See
https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1566/connectors/csws/wsdls
Karl
On Thu, Jan 24, 2019 at 6:24 AM Rafa Haro wrote:
> Karl, can you share the WSDL, I can try to take a look later today
>
> On Thu, Jan 24, 2019 at 12:13 PM Karl Wright
Karl, can you share the WSDL, I can try to take a look later today
On Thu, Jan 24, 2019 at 12:13 PM Karl Wright wrote:
> I'm redeveloping the Livelink connector because the API code has been
> discontinued and the only API is now web services based. The WSDLs and
> XSDs have been exported and
I'm redeveloping the Livelink connector because the API code has been
discontinued and the only API is now web services based. The WSDLs and
XSDs have been exported and I'm trying to use the Axis tool WSDL2Java to
convert to Java code. Unfortunately, I haven't been able to make this work
-- even
21 matches
Mail list logo
