[jira] WSDL Generation for Client
Hi, As i have created the Server implementation classes with the help of wsdl2java tool. Where i can specify that the end user or client should take the WSDL generated by me. Currently CXF is generating the wsdl for me. I do not want this. I want the wsdl, that i have created to be shown to the clients. How can i do this. Is there any configuration file that i can specifiy the wsdl location. Help in this regard is greatly helpfull. Thanks, naren -- View this message in context: http://www.nabble.com/WSDL-Generation-for-Client-tp17187326p17187326.html Sent from the cxf-issues mailing list archive at Nabble.com.
Antwort: [jira] WSDL Generation for Client [Virus checked]
Hello, i don't know much about CXF atm, but when you create endpoint in following way, than it seems that WSDL is the same one on classpath. In fact it's not the same, but it's loaded by xml parser and written back .. that's why it's possible that some attributes have different order etc. And before 2.1.1 CDATA section markers were missing. http://namespace.my.org/services/test"; > regards jano heyhero <[EMAIL PROTECTED]> 05/12/2008 15:16 Bitte antworten an [EMAIL PROTECTED] An issues@cxf.apache.org Kopie Thema [jira] WSDL Generation for Client [Virus checked] Hi, As i have created the Server implementation classes with the help of wsdl2java tool. Where i can specify that the end user or client should take the WSDL generated by me. Currently CXF is generating the wsdl for me. I do not want this. I want the wsdl, that i have created to be shown to the clients. How can i do this. Is there any configuration file that i can specifiy the wsdl location. Help in this regard is greatly helpfull. Thanks, naren -- View this message in context: http://www.nabble.com/WSDL-Generation-for-Client-tp17187326p17187326.html Sent from the cxf-issues mailing list archive at Nabble.com.
[jira] Updated: (CXF-1585) Error in javadoc of org.apache.cxf.common.logging.LogUtils
[ https://issues.apache.org/jira/browse/CXF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andri Saar updated CXF-1585: Component/s: (was: Configuration) Documentation Documentation is probably a better component for this issue. > Error in javadoc of org.apache.cxf.common.logging.LogUtils > -- > > Key: CXF-1585 > URL: https://issues.apache.org/jira/browse/CXF-1585 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 2.1 >Reporter: Andri Saar >Priority: Trivial > > Pretty trivial mistake in the javadoc of > org.apache.cxf.common.logging.LogUtils: instead of looking for > "META-INF/cxf/org.apache.cxf.logger" as the javadoc specifies, CXF will > actually look for "META-INF/cxf/org.apache.cxf.Logger". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-1585) Error in javadoc of org.apache.cxf.common.logging.LogUtils
Error in javadoc of org.apache.cxf.common.logging.LogUtils -- Key: CXF-1585 URL: https://issues.apache.org/jira/browse/CXF-1585 Project: CXF Issue Type: Bug Components: Configuration Affects Versions: 2.1 Reporter: Andri Saar Priority: Trivial Pretty trivial mistake in the javadoc of org.apache.cxf.common.logging.LogUtils: instead of looking for "META-INF/cxf/org.apache.cxf.logger" as the javadoc specifies, CXF will actually look for "META-INF/cxf/org.apache.cxf.Logger". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1585) Error in javadoc of org.apache.cxf.common.logging.LogUtils
[ https://issues.apache.org/jira/browse/CXF-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved CXF-1585. --- Resolution: Fixed Fix Version/s: 2.1.1 Done. > Error in javadoc of org.apache.cxf.common.logging.LogUtils > -- > > Key: CXF-1585 > URL: https://issues.apache.org/jira/browse/CXF-1585 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 2.1 >Reporter: Andri Saar >Priority: Trivial > Fix For: 2.1.1 > > > Pretty trivial mistake in the javadoc of > org.apache.cxf.common.logging.LogUtils: instead of looking for > "META-INF/cxf/org.apache.cxf.logger" as the javadoc specifies, CXF will > actually look for "META-INF/cxf/org.apache.cxf.Logger". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] WSDL Generation for Client
Assuming you are using JAX-WS, you can put the wsdlLocation in the wsdlLocation attribute of the @WebService annotation. That's the standard JAX-WS way of doing that. Alternatively, you would need to use configuration and/or the service factories. That would completely depend on your deployment model and way you are configuring spring, etc... For example, if using jaxws:endpoint in the spring configuration has a wsdlLocation attribute on it that can be used. Dan On May 12, 2008, at 9:16 AM, heyhero wrote: Hi, As i have created the Server implementation classes with the help of wsdl2java tool. Where i can specify that the end user or client should take the WSDL generated by me. Currently CXF is generating the wsdl for me. I do not want this. I want the wsdl, that i have created to be shown to the clients. How can i do this. Is there any configuration file that i can specifiy the wsdl location. Help in this regard is greatly helpfull. Thanks, naren -- View this message in context: http://www.nabble.com/WSDL-Generation-for-Client-tp17187326p17187326.html Sent from the cxf-issues mailing list archive at Nabble.com. --- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
[jira] Resolved: (CXF-1581) ?wsdl not working if using the sun stax parser instead of woodstox
[ https://issues.apache.org/jira/browse/CXF-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1581. -- Resolution: Fixed > ?wsdl not working if using the sun stax parser instead of woodstox > -- > > Key: CXF-1581 > URL: https://issues.apache.org/jira/browse/CXF-1581 > Project: CXF > Issue Type: Bug >Affects Versions: 2.1, 2.0.6 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.1.1, 2.0.7 > > > The writeAttributes method in StaxUtils is sometimes getting a "null" > namespace which seems to be OK for woodstox, but not for Sun's parser. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1583) DynamicClientFactory.setupClasspath method cannot handle spaces in path to jar file
[
https://issues.apache.org/jira/browse/CXF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-1583:
Assignee: Daniel Kulp
> DynamicClientFactory.setupClasspath method cannot handle spaces in path to
> jar file
> ---
>
> Key: CXF-1583
> URL: https://issues.apache.org/jira/browse/CXF-1583
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.1
> Environment: Ubuntu 7.04, Windows XP, jdk 1.5_09, cxf 2.1
>Reporter: Alton Idowu
>Assignee: Daniel Kulp
>
> The setupClasspath method in the DynamicClientFactory class cannot handle
> spaces in the path to jar files. It throws the following exception:
> Caused by: java.net.URISyntaxException: Illegal character in path at index
> 16: file:/C:/Program Files/Apache/Tomcat-5.5.20/common/i18n/tomcat-i18n-en.jar
> at java.net.URI$Parser.fail(URI.java:2816)
> at java.net.URI$Parser.checkChars(URI.java:2989)
> at java.net.URI$Parser.parseHierarchical(URI.java:3073)
> at java.net.URI$Parser.parse(URI.java:3021)
> at java.net.URI.(URI.java:578)
> at java.net.URL.toURI(URL.java:916)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.setupClasspath(DynamicClientFactory.java:405)
> This is a know issue withthe URL.toURI() method.
> A possible solution would be to replace the following:
> if (url.getProtocol().startsWith("file")) {
> try {
> File file = new File(url.toURI().getPath());
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> } catch (URISyntaxException e) {
> throw new UncheckedException(e);
> }
> }
> with
> if (url.getProtocol().startsWith("file")) {
> File file;
> try {
> file = new File(url.toURI().getPath());
> } catch (catch catch(URISyntaxException urise) {
> file = new File(url.getPath());
> }
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1584) DynamicClientFactory.setupClasspath method throws Exception if jar file does not exist
[
https://issues.apache.org/jira/browse/CXF-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-1584:
Assignee: Daniel Kulp
> DynamicClientFactory.setupClasspath method throws Exception if jar file does
> not exist
> --
>
> Key: CXF-1584
> URL: https://issues.apache.org/jira/browse/CXF-1584
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.1
> Environment: Ubuntu 7.04, Windows XP, jdk 1.5_09, cxf 2.1
>Reporter: Alton Idowu
>Assignee: Daniel Kulp
>
> If a jar file reported by the classloader does not exist, the following
> exception is thrown:
> Caused by: java.util.zip.ZipException: No such file or directory
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.(ZipFile.java:203)
> at java.util.jar.JarFile.(JarFile.java:132)
> at java.util.jar.JarFile.(JarFile.java:97)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.addClasspathFromManifest(DynamicClientFactory.java:366)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.setupClasspath(DynamicClientFactory.java:422)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:214)
> ... 54 more
> As the code does not display the file in question, it is a very tedious
> process to find the issue in the classpath. It would be prefferable if the
> code would ignore any missing jar file. Another possible solution (though
> less preferrable) would be to print the jar files as they are added.
> Code in question:
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> The following code should fix the issue:
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1551) validation against XML schema - leads to invalid soap response
[
https://issues.apache.org/jira/browse/CXF-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jmi updated CXF-1551:
-
Component/s: (was: JAXB Databinding)
Description:
when XML schema validation is enabled, and mandatory element is missing
(probably the same for any other error) in CXF-generated response, then
response is invalid in some cases.
E.g. such response is generated from modified wsdl_first sample:
http://schemas.xmlsoap.org/soap/envelope/";>http://apache.org/hello_world_soap_http/types";>Executing
operation sayHi1THIS IS IMPORTANT
.. VERY LONG TEXT ..SOMETHING WILL BE flushed probably and that's why cannot be
removed later when fault should replace content
...
...
..
..
...
..
..
.
...
...
..
...
...
...
.soap:ServerMarshalli
ng Error: cvc-complex-type.2.4.a: Invalid content was found starting with
element 'responseType2'. One of
'{"http://apache.org/hello_world_soap_http/types":responseType}' is
expected.
in attachment you can find modified sample I used to show the bug in simple
enough project. Just do "ant server" and then invoke sayHi from soapUi or other
tool, You should see response listed above.
Dans comment from mailing list:
Basically, fixing this will require breaking the streaming. Most likely,
if validation is turned on
[jira] Resolved: (CXF-1584) DynamicClientFactory.setupClasspath method throws Exception if jar file does not exist
[
https://issues.apache.org/jira/browse/CXF-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1584.
--
Resolution: Fixed
Fix Version/s: 2.1.1
> DynamicClientFactory.setupClasspath method throws Exception if jar file does
> not exist
> --
>
> Key: CXF-1584
> URL: https://issues.apache.org/jira/browse/CXF-1584
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.1
> Environment: Ubuntu 7.04, Windows XP, jdk 1.5_09, cxf 2.1
>Reporter: Alton Idowu
>Assignee: Daniel Kulp
> Fix For: 2.1.1
>
>
> If a jar file reported by the classloader does not exist, the following
> exception is thrown:
> Caused by: java.util.zip.ZipException: No such file or directory
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.(ZipFile.java:203)
> at java.util.jar.JarFile.(JarFile.java:132)
> at java.util.jar.JarFile.(JarFile.java:97)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.addClasspathFromManifest(DynamicClientFactory.java:366)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.setupClasspath(DynamicClientFactory.java:422)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:214)
> ... 54 more
> As the code does not display the file in question, it is a very tedious
> process to find the issue in the classpath. It would be prefferable if the
> code would ignore any missing jar file. Another possible solution (though
> less preferrable) would be to print the jar files as they are added.
> Code in question:
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> The following code should fix the issue:
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1583) DynamicClientFactory.setupClasspath method cannot handle spaces in path to jar file
[
https://issues.apache.org/jira/browse/CXF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1583.
--
Resolution: Fixed
Fix Version/s: 2.1.1
> DynamicClientFactory.setupClasspath method cannot handle spaces in path to
> jar file
> ---
>
> Key: CXF-1583
> URL: https://issues.apache.org/jira/browse/CXF-1583
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.1
> Environment: Ubuntu 7.04, Windows XP, jdk 1.5_09, cxf 2.1
>Reporter: Alton Idowu
>Assignee: Daniel Kulp
> Fix For: 2.1.1
>
>
> The setupClasspath method in the DynamicClientFactory class cannot handle
> spaces in the path to jar files. It throws the following exception:
> Caused by: java.net.URISyntaxException: Illegal character in path at index
> 16: file:/C:/Program Files/Apache/Tomcat-5.5.20/common/i18n/tomcat-i18n-en.jar
> at java.net.URI$Parser.fail(URI.java:2816)
> at java.net.URI$Parser.checkChars(URI.java:2989)
> at java.net.URI$Parser.parseHierarchical(URI.java:3073)
> at java.net.URI$Parser.parse(URI.java:3021)
> at java.net.URI.(URI.java:578)
> at java.net.URL.toURI(URL.java:916)
> at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.setupClasspath(DynamicClientFactory.java:405)
> This is a know issue withthe URL.toURI() method.
> A possible solution would be to replace the following:
> if (url.getProtocol().startsWith("file")) {
> try {
> File file = new File(url.toURI().getPath());
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> } catch (URISyntaxException e) {
> throw new UncheckedException(e);
> }
> }
> with
> if (url.getProtocol().startsWith("file")) {
> File file;
> try {
> file = new File(url.toURI().getPath());
> } catch (catch catch(URISyntaxException urise) {
> file = new File(url.getPath());
> }
> if (file.exists()) {
> classPath.append(file.getAbsolutePath())
> .append(System
> .getProperty("path.separator"));
>
> }
>
> if (file.getName().endsWith(".jar")) {
> addClasspathFromManifest(classPath, file);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
