[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924039#comment-16924039
]
Karl Wright commented on CONNECTORS-1566:
-----------------------------------------
Here's the current distribution area jar setup:
{code}
C:\wip\mcf\CONNECTORS-1566\dist>dir lib\jaxws-rt-*.jar
Volume in drive C is Windows
Volume Serial Number is F4D8-E4E0
Directory of C:\wip\mcf\CONNECTORS-1566\dist\lib
File Not Found
C:\wip\mcf\CONNECTORS-1566\dist>dir connector-common-lib\jaxws-rt-*.jar
Volume in drive C is Windows
Volume Serial Number is F4D8-E4E0
Directory of C:\wip\mcf\CONNECTORS-1566\dist\connector-common-lib
File Not Found
C:\wip\mcf\CONNECTORS-1566\dist>dir connector-lib\jaxws-rt-*.jar
Volume in drive C is Windows
Volume Serial Number is F4D8-E4E0
Directory of C:\wip\mcf\CONNECTORS-1566\dist\connector-lib
09/05/2019 07:28 PM 2,168,512 jaxws-rt-2.2.6.jar
1 File(s) 2,168,512 bytes
0 Dir(s) 200,186,331,136 bytes free
C:\wip\mcf\CONNECTORS-1566\dist>
{code}
The jar in question is being brought in by another connector. My question: if
we make sure it's NOT brought in, and we instead make sure the cxf version is
available, will the other connector break? Will the csws connector begin to
work? I'll check it out.
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> ------------------------------------------------------------------------------
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
> Affects Versions: ManifoldCF 2.12
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
