[
https://wso2.org/jira/browse/ESBJAVA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761#action_17761
]
Ruwan Linton commented on ESBJAVA-493:
--------------------------------------
Hi Jonathan,
Ideally you should do a svn diff and redirect the out put to a file and attach
it to the JIRA so that we can apply that to the code.
If you are on a unix based system then this can be achieved by the following
command
svn diff > test.patch
and if on Windows there is an option on your subversion software to create this
patch.
> Reference PKI enabled endpoints in the Admin console
> ----------------------------------------------------
>
> Key: ESBJAVA-493
> URL: https://wso2.org/jira/browse/ESBJAVA-493
> Project: WSO2 ESB
> Issue Type: Improvement
> Components: Administration Console
> Reporter: Jonathan Holmes
> Assignee: indika kumara
> Fix For: FUTURE
>
> Attachments: Enable ESB PKI Certificates.zip, my.example.transport.zip
>
>
> When referencing a PKI enabled published WSDL via the Source URL I get the
> same exception as http://wso2.org/forum/thread/3377. From the research I've
> done and read it appears to do this because the Admin console is using the
> default KeyStore that comes with the JRE and it does a simple URLConnection.
> This thread talks to this issue: http://wso2.org/forum/thread/3621 and has
> sample code on a resolution.
> The key requirement would be to enable different KeyStores per WSDL reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
