Issues with Attachments: week of 2011-01-24
CXF - Monday, January 24, 2011 6 Issues with Attachments (sorted oldest to newest) [CXF-1940] WS-Trust support in CXF - Created: 2008-12-11 - Updated: 2011-01-20 - Type: Task - Fix Versions: [] - Reporter: Mayank Mishra - Assigned: Unassigned - Attachments: [BinarySecret.java, Entropy.java, model.zip, RequestSecurityToken.java, RequestSecurityTokenResponse.java, SecurityConstants.java, STS.java, STSClient27Jan.patch, STSImpl.java] - https://issues.apache.org:443/jira/browse/CXF-1940 [CXF-3055] Adding appropriate switches to all command line tools - Created: 2010-10-08 - Updated: 2011-01-13 - Type: Improvement - Fix Versions: [] - Reporter: Robert Liguori - Assigned: Unassigned - Attachments: [usages_of_cxf_commands.doc] - https://issues.apache.org:443/jira/browse/CXF-3055 [CXF-3219] WS-RMs' DestinationSequence does not update the ack range in the RMStore - Created: 2010-12-25 - Updated: 2011-01-17 - Type: Bug - Fix Versions: [] - Reporter: Aki Yoshida - Assigned: Unassigned - Attachments: [rt-ws-rm-2.3.x-fixes-diff.txt] - https://issues.apache.org:443/jira/browse/CXF-3219 [CXF-3245] Adding command line options where appropriate - Created: 2011-01-13 - Updated: 2011-01-13 - Type: Improvement - Fix Versions: [] - Reporter: Robert Liguori - Assigned: Unassigned - Attachments: [command+line+options+for+tooling.doc] - https://issues.apache.org:443/jira/browse/CXF-3245 [CXF-3262] JAX-RS: Performance Improvement: Don't use IllegalArgumentException to determine if a URI chunk is a variable or literal - Created: 2011-01-21 - Updated: 2011-01-22 - Type: Improvement - Fix Versions: [2.3.3] - Reporter: Ka-Lok Fung - Assigned: Unassigned - Attachments: [patch.diff] - https://issues.apache.org:443/jira/browse/CXF-3262 [CXF-3271] WS-RM code does not support InOrder assurances - Created: 2011-01-22 - Updated: 2011-01-23 - Type: Bug - Fix Versions: [] - Reporter: Dennis Sosnoski - Assigned: Unassigned - Attachments: [CXF-3271-patch.txt, inorder.zip] - https://issues.apache.org:443/jira/browse/CXF-3271
[jira] Created: (CXF-3277) soap headers can't be carried back when exception happen
soap headers can't be carried back when exception happen
Key: CXF-3277
URL: https://issues.apache.org/jira/browse/CXF-3277
Project: CXF
Issue Type: Bug
Reporter: Freeman Fang
Assignee: Freeman Fang
Fix For: 2.4, 2.3.3
for example we have a methoh like
{code}
public BareDocumentResponse testDocLitFault(String in) throws BadRecordLitFault
{
System.out.println("Executing testDocLitFault sayHi\n");
List headers = new ArrayList();
Header header = null;
try {
header = new Header(new QName("http://test";, "test"),
new String("test"), new
JAXBDataBinding(String.class));
} catch (JAXBException e) {
e.printStackTrace();
}
headers.add(header);
context.getMessageContext().put(Header.HEADER_LIST, headers);
throw new BadRecordLitFault("int fault", 5);
}
{code}
we explicitly put some headers for response message, it works in normal
response, but doesn't work when throw Fault/Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3277) soap headers can't be carried back when exception happen
[
https://issues.apache.org/jira/browse/CXF-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CXF-3277:
--
Attachment: CXF-3277-test.patch
testcase to expose this problem
> soap headers can't be carried back when exception happen
>
>
> Key: CXF-3277
> URL: https://issues.apache.org/jira/browse/CXF-3277
> Project: CXF
> Issue Type: Bug
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4, 2.3.3
>
> Attachments: CXF-3277-test.patch
>
>
> for example we have a methoh like
> {code}
> public BareDocumentResponse testDocLitFault(String in) throws
> BadRecordLitFault {
> System.out.println("Executing testDocLitFault sayHi\n");
> List headers = new ArrayList();
> Header header = null;
> try {
> header = new Header(new QName("http://test";, "test"),
> new String("test"), new
> JAXBDataBinding(String.class));
> } catch (JAXBException e) {
> e.printStackTrace();
> }
> headers.add(header);
> context.getMessageContext().put(Header.HEADER_LIST, headers);
> throw new BadRecordLitFault("int fault", 5);
> }
> {code}
> we explicitly put some headers for response message, it works in normal
> response, but doesn't work when throw Fault/Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3278) Invalid Enum passed in WebMethod results to a null object
Invalid Enum passed in WebMethod results to a null object
-
Key: CXF-3278
URL: https://issues.apache.org/jira/browse/CXF-3278
Project: CXF
Issue Type: Bug
Affects Versions: 2.3.2
Reporter: Ioannis Mavroukakis
Given the following method
{code}
@WebMethod
public BaseResponse removeDepositLimits(
@WebParam( name = SERVICE_AUTH ) @XmlElement( required = true )
final Authorisation auth ,
@WebParam( name = TOKEN ) @XmlElement( required = true ) final
String token ,
@WebParam( name = "timeFrame" ) @XmlElement( required = true )
final DepositLimit.TimeFrame timeFrame )
{code}
when timeFrame is a value that's not in the TimeFrame enum, timeFrame is set to
null, this should return an error to the invoker instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3279) Marking the imports of the CORABA package to be optional
Marking the imports of the CORABA package to be optional Key: CXF-3279 URL: https://issues.apache.org/jira/browse/CXF-3279 Project: CXF Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.2.13, 2.4, 2.3.3 As the corba binding is used rarely, I think we can set the CORBA packages imports to optional. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3279) Marking the imports of the CORABA package to be optional
[ https://issues.apache.org/jira/browse/CXF-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3279. --- Resolution: Fixed > Marking the imports of the CORABA package to be optional > > > Key: CXF-3279 > URL: https://issues.apache.org/jira/browse/CXF-3279 > Project: CXF > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.2.13, 2.4, 2.3.3 > > > As the corba binding is used rarely, I think we can set the CORBA packages > imports to optional. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke updated CXF-3280:
Attachment: CXF-3280.patch
Suggesting patch based on 2.3.x branch.
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
idl2wsdl does not process multiple include directories -I correctly.
--
Key: CXF-3280
URL: https://issues.apache.org/jira/browse/CXF-3280
Project: CXF
Issue Type: Bug
Components: Tooling
Affects Versions: 2.3.2
Reporter: Torsten Mielke
Attachments: CXF-3280.patch
If you run
{code}
idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
{code}
with multiple -I options specified, idl2wsdl will only process the first
occurrence of -I and skip all others. As a result included IDL files that
reside in different subdirectories are not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
"<" converted to "<" for generated comments using wsdl2java. --- Key: CXF-3281 URL: https://issues.apache.org/jira/browse/CXF-3281 Project: CXF Issue Type: Bug Affects Versions: 2.3.2 Environment: Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.6.0_22 Runtime = Java HotSpot(TM) Client VM 17.1-b03 Reporter: Robert Liguori Priority: Trivial Attachments: less_than.TIF "<" converted to "<" for generated comments using wsdl2java. Use case: wsdl2java http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Liguori updated CXF-3281: Attachment: less_than.TIF > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke updated CXF-3280:
Attachment: (was: CXF-3280.patch)
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke updated CXF-3280:
Attachment: CXF-3280.patch
Attaching another patch that includes a JUnit test as well.
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985753#action_12985753 ] Glen Mazza commented on CXF-3281: - Isn't that correct because it's in a block -- the text in the Java file eventually goes into an HTML Javadoc, you know. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3282) How do we implement castor mapping during marshalling of request and unmarshalling of response xml using CXF framework.
How do we implement castor mapping during marshalling of request and
unmarshalling of response xml using CXF framework.
Key: CXF-3282
URL: https://issues.apache.org/jira/browse/CXF-3282
Project: CXF
Issue Type: Bug
Components: Integration
Affects Versions: 2.2.9
Environment: JDK 1.6,
Reporter: Asif Ali Mohammed
Hi,
I have an existing web service developed using Axis 1.2 where I use Castor
Mapping API and perform custom mapping for the request xml received and
outgoing response xml.
Example:
Request: abcrta
Mapping: Person - > Employee; name -> fullName; id - > employeeId
Objects inside my service :
public class Employee{
private String fullName;
private String employeeId
}
Is there any similar and flexible way of doing a custom mapping in CXF. Please
suggest.
Thanks,
Asif Ali Mohammed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985787#action_12985787 ] Robert Liguori edited comment on CXF-3281 at 1/24/11 11:27 AM: --- You are absolutely right Glen, my bad. I generated the Javadoc with a "<" versus "& lt;" and the element was not displayed... so it must be "<" as you said. was (Author: gliesian): You are absolutely right Glen, my bad. I generated the Javadoc with a "<" versus "<" and the element was not displayed... so it must be "<" as you said. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985787#action_12985787 ] Robert Liguori commented on CXF-3281: - You are absolutely right Glen, my bad. I generated the Javadoc with a "<" versus "<" and the element was not displayed... so it must be "<" as you said. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985787#action_12985787 ] Robert Liguori edited comment on CXF-3281 at 1/24/11 11:29 AM: --- You are absolutely right Glen, my bad. As such this is an INVALID issue Note: I generated the Javadoc with a "<" versus "& lt;" and the element was not displayed... so it must be "<" as you said. was (Author: gliesian): You are absolutely right Glen, my bad. I generated the Javadoc with a "<" versus "& lt;" and the element was not displayed... so it must be "<" as you said. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Liguori closed CXF-3281. --- Resolution: Invalid Closing as invalid. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke updated CXF-3280:
Description:
If you run
{code}
idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
{code}
with multiple -I options specified, idl2wsdl will only process the first
occurrence of -I and skip all others. As a result included IDL files that
reside in different subdirectories are not found.
That can result in errors like this one, where it only tries to load included
IDL files from the first -I location rather than also trying from -I subdir2.
{code}
idl2wsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
idltowsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
idltowsdl - Progress FUSE Services Framework 2.2.10-fuse-00-00
Error : java.io.FileNotFoundException:
C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
(The system cannot find the file specified)
org.apache.cxf.tools.common.ToolException: java.io.FileNotFoundException:
C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
(The system cannot find the file specified)
at
org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:72)
at
org.apache.cxf.tools.corba.processors.idl.IDLToWSDLProcessor.process(IDLToWSDLProcessor.java:78)
at org.apache.cxf.tools.corba.IDLToWSDL.execute(IDLToWSDL.java:73)
at
org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
at
org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:58)
at
org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:40)
at org.apache.cxf.tools.corba.IDLToWSDL.run(IDLToWSDL.java:162)
at org.apache.cxf.tools.corba.IDLToWSDL.main(IDLToWSDL.java:170)
Caused by: java.io.FileNotFoundException:
C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
(The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileInputStream.(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
at java.net.URL.openStream(URL.java:1009)
at
org.apache.cxf.tools.corba.idlpreprocessor.IncludeStackEntry.(IncludeStackEntry.java:40)
at
org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.pushInclude(IdlPreprocessorReader.java:108)
at
org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.handleInclude(IdlPreprocessorReader.java:297)
at
org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.fillBuffer(IdlPreprocessorReader.java:174)
at
org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.(IdlPreprocessorReader.java:100)
at
org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:57)
... 7 more
Error : java.io.FileNotFoundException:
C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
(The system cannot find the file specified)
{code}
was:
If you run
{code}
idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
{code}
with multiple -I options specified, idl2wsdl will only process the first
occurrence of -I and skip all others. As a result included IDL files that
reside in different subdirectories are not found.
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
> That can result in errors like this one, where it only tries to load included
> IDL files from the first -I location rather than also trying from -I subdir2.
> {code}
> idl2wsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl - Progress FUSE Services Framework 2.2.10-fuse-00-00
> Error : java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\res
[jira] Created: (CXF-3283) Generated do not have end tags.
Generated do not have end tags. --- Key: CXF-3283 URL: https://issues.apache.org/jira/browse/CXF-3283 Project: CXF Issue Type: Improvement Affects Versions: 2.3.2 Reporter: Robert Liguori Priority: Trivial Generated do not have end tags. Use case: wsdl2java http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl Example for ArrayOfMovies.java: /** * Java class for ArrayOfMovie complex type. * * The following schema fragment specifies the expected content contained within this class. * * ** * * * */ Recommendation is to add end tags where appropriate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.* ** ** **
[jira] Commented: (CXF-3283) Generated do not have end tags.
[ https://issues.apache.org/jira/browse/CXF-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985943#action_12985943 ] Andreas Veithen commented on CXF-3283: -- By definition, Javadoc is HTML 4, so having tags without corresponding end tags is perfectly valid. By the way, if you look at the Javadoc of the JRE, you can see that omitting is the rule. > Generated do not have end tags. > --- > > Key: CXF-3283 > URL: https://issues.apache.org/jira/browse/CXF-3283 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.2 >Reporter: Robert Liguori >Priority: Trivial > > Generated do not have end tags. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > Example for ArrayOfMovies.java: > /** > * Java class for ArrayOfMovie complex type. > * > * The following schema fragment specifies the expected content contained > within this class. > * > * > *> * > * > * > * > */ > Recommendation is to add end tags where appropriate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.> * > *> * > *> * > *type="{http://www.ignyte.com/whatsshowing}Movie"; maxOccurs="unbounded" > minOccurs="0"/> > *
[jira] Created: (CXF-3284) WS-Addressing documentation is incomplete
WS-Addressing documentation is incomplete - Key: CXF-3284 URL: https://issues.apache.org/jira/browse/CXF-3284 Project: CXF Issue Type: Bug Components: Documentation Affects Versions: 2.3.2 Environment: N/A Reporter: Dan Peterson Fix For: 2.2.13 In the User's Guide, there is missing documentation for WS-Addressing support (http://cxf.apache.org/docs/ws-addressing.html). Specifically, there are two empty sections marked "TODO": 1) Enabling WS-Addressing with WS-Policy, and 2) Configuring your actions and setting up decoupled endpoints. I am new to CXF, and I'm using it on a project to communicate with a .NET WCF web service that users a wsHttpBinding and is secured with SPNEGO and SSL. To complicate the problem further, there will not be any WSDL available from the endpoint when my CXF client is deployed. The CXF client will not be able to rely on the presence of the EndpointReference in the port definition to determine how to properly configure WS-Addressing. I was wondering if an example could be given. I know how to replace the endpoint address using the binding provider: BindingProvider provider = (BindingProvider)iHelloPort; provider.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, url); How do I configure the rest of the information needed by WS-Addressing? Specifically, the Identity of the endpoint. See below: The WSDL (just includes the port definition) I am working from is similar to: http://tempuri.org/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsa10="http://www.w3.org/2005/08/addressing"; xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"; xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:tns="http://tempuri.org/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:i0="http://example.com/my/service"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> http://schemas.microsoft.com/ws/06/2004/policy/http"/> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> http://example.com/my/service"; location="hello-0.wsdl"/> http://schemas.xmlsoap.org/soap/http"/> http://example.com/my/service/IHello/GetMessage"; style="document"/> https://example.com/MyService/service.svc/Hello"/> https://example.com/MyService/service.svc/Hello http://schemas.xmlsoap.org/ws/2006/02/addressingidentity";> host/SERVER.example.com -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3283) Generated do not have end tags.
[ https://issues.apache.org/jira/browse/CXF-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985957#action_12985957 ] Robert Liguori commented on CXF-3283: - Looks like I should run this stuff by the forum before opening up the issues. I was actually thinking best practices in closing tags, as is done with XHTML. But if HTML 4 doesn't require it, I guess this isn't an issue, and can be marked as invalid. > Generated do not have end tags. > --- > > Key: CXF-3283 > URL: https://issues.apache.org/jira/browse/CXF-3283 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.2 >Reporter: Robert Liguori >Priority: Trivial > > Generated do not have end tags. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > Example for ArrayOfMovies.java: > /** > * Java class for ArrayOfMovie complex type. > * > * The following schema fragment specifies the expected content contained > within this class. > * > * > *> * > * > * > * > */ > Recommendation is to add end tags where appropriate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.> * > *> * > *> * > *type="{http://www.ignyte.com/whatsshowing}Movie"; maxOccurs="unbounded" > minOccurs="0"/> > *
[jira] Issue Comment Edited: (CXF-3281) "<" converted to "<" for generated comments using wsdl2java.
[ https://issues.apache.org/jira/browse/CXF-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985787#action_12985787 ] Robert Liguori edited comment on CXF-3281 at 1/24/11 3:23 PM: -- You are absolutely right Glen, my bad. As such this is an INVALID issue Note: I generated the Javadoc with a "<" versus "< ;" and the element was not displayed... so it must be "< ;" as you said. was (Author: gliesian): You are absolutely right Glen, my bad. As such this is an INVALID issue Note: I generated the Javadoc with a "<" versus "& lt;" and the element was not displayed... so it must be "<" as you said. > "<" converted to "<" for generated comments using wsdl2java. > --- > > Key: CXF-3281 > URL: https://issues.apache.org/jira/browse/CXF-3281 > Project: CXF > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Operating System = Windows XP version 5.1 running on x86 > Java; VM; Vendor = 1.6.0_22 > Runtime = Java HotSpot(TM) Client VM 17.1-b03 >Reporter: Robert Liguori >Priority: Trivial > Attachments: less_than.TIF > > > "<" converted to "<" for generated comments using wsdl2java. > Use case: > wsdl2java > http://www.ignyte.com/webservices/ignyte.whatsshowing.webservice/moviefunctions.asmx?wsdl > See attached image. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3262) JAX-RS: Performance Improvement: Don't use IllegalArgumentException to determine if a URI chunk is a variable or literal
[ https://issues.apache.org/jira/browse/CXF-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986050#action_12986050 ] Sergey Beryozkin commented on CXF-3262: --- The patch looks perfect to me, thanks > JAX-RS: Performance Improvement: Don't use IllegalArgumentException to > determine if a URI chunk is a variable or literal > > > Key: CXF-3262 > URL: https://issues.apache.org/jira/browse/CXF-3262 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Affects Versions: 2.3.1 > Environment: JDK 1.6 >Reporter: Ka-Lok Fung >Priority: Minor > Fix For: 2.3.3 > > Attachments: patch.diff > > Original Estimate: 3h > Remaining Estimate: 3h > > Profiling the Apache CXF JAX-RS code shows that more time than necessary is > being spent in UriChunk.createUriChunk because it uses an > IllegalArgumentException to determine whether a URI chunk should be a literal > or a variable. Creating exceptions is expensive :( > Instead of using IllegalArgumentException, perhaps you can have a method that > is like the following: > public static Variable.create(String uriChunk) > where null will be returned if uriChunk is not a variable. This way you can > avoid the overhead of creating the unnecessary stack trace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3274) JAX RS @FormParam error
[ https://issues.apache.org/jira/browse/CXF-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3274. --- Resolution: Fixed Fix Version/s: 2.3.3 2.4 > JAX RS @FormParam error > --- > > Key: CXF-3274 > URL: https://issues.apache.org/jira/browse/CXF-3274 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.2.7, 2.3.2, 2.4 > Environment: testing within Apache OODT cas-curator component >Reporter: Chris A. Mattmann >Assignee: Sergey Beryozkin >Priority: Blocker > Fix For: 2.4, 2.3.3 > > > Hi Guys: > I'm noticing a bug when trying to read the value of a @FormParam variable > within a Resource Service. I've reported what I'm seeing on the mailing list: > http://s.apache.org/jc > I've also confirmed that this isn't related to CXF-3147. > I've filed OODT-118 to track this on the OODT end. > Any help would be appreciated. > Cheers, > Chris -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-3274) JAX RS @FormParam error
[ https://issues.apache.org/jira/browse/CXF-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-3274: - Assignee: Sergey Beryozkin > JAX RS @FormParam error > --- > > Key: CXF-3274 > URL: https://issues.apache.org/jira/browse/CXF-3274 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.2.7, 2.3.2, 2.4 > Environment: testing within Apache OODT cas-curator component >Reporter: Chris A. Mattmann >Assignee: Sergey Beryozkin >Priority: Blocker > Fix For: 2.4, 2.3.3 > > > Hi Guys: > I'm noticing a bug when trying to read the value of a @FormParam variable > within a Resource Service. I've reported what I'm seeing on the mailing list: > http://s.apache.org/jc > I've also confirmed that this isn't related to CXF-3147. > I've filed OODT-118 to track this on the OODT end. > Any help would be appreciated. > Cheers, > Chris -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1254) WS-A Interop with .Net WCF - CXF fails to interop with .Net WS-A due to use of old namespace.
[ https://issues.apache.org/jira/browse/CXF-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986082#action_12986082 ] Dennis Sosnoski commented on CXF-1254: -- Metro also uses the official WS-A 2005/08 with WS-RM 1.0. I agree that this contradicts the WS-RM 1.0 spec, but it looks like everyone else has standardized on this variation. I'd suggest either changing the default for the client to WS-A 2005/08 with an option to override for the older namespace, or keep the default the same and give an option to use 2005/08. I think the server should adapt to whatever namespace is used by the client, as with other parts of CXF. > WS-A Interop with .Net WCF - CXF fails to interop with .Net WS-A due to use > of old namespace. > - > > Key: CXF-1254 > URL: https://issues.apache.org/jira/browse/CXF-1254 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Affects Versions: 2.0.3 > Environment: CXF 2.0.3 > JBoss > Spring > .Net WCF client > WSDL first development >Reporter: Paul Freeman > > CXF is not compatible with .net's WCF implementation. I have successfully > configured reliable messaging in both CXF and .net. The client is .net and > the service is CXF. .net makes the initial request to create a sequence and > expects the response to contain a header tag. The namespace for > this header tag is an addressing namespace. > It turns out that CXF returns the addressing namespace > http://schemas.xmlsoap.org/ws/2004/08/addressing > But WCF sent the request with the this namespace: > http://www.w3.org/2005/08/addressing > So the result is that WCF cannot find the header tag. > I wrote the wsdl with this namespace, which is all together different as well: > http://www.w3.org/2006/05/addressing/wsdl > Here is the entire message exchange captured by wireshark: > == > POST /saas-identity-2.0-CXF-WSDLFirst/services/IdentityService HTTP/1.1 > Content-Type: text/xml; charset=utf-8 > SOAPAction: "http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"; > Host: ad1vm-saasdev > Content-Length: 695 > Expect: 100-continue > Connection: Keep-Alive > HTTP/1.1 100 Continue > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:a="http://www.w3.org/2005/08/addressing";> s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceurn:uuid:c211d39e-e26b-4345-8c4a-a5c931ec210d > s:mustUnderstand="1">http://ad1vm-saasdev/saas-identity-2.0-CXF-WSDLFirst/services/IdentityService > xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm";>http://www.w3.org/2005/08/addressing/anonymousurn:uuid:a7418b78-869a-4dcf-a99e-3ebdbc5e6862HTTP/1.1 > 200 OK > Date: Fri, 30 Nov 2007 16:42:27 GMT > Server: Microsoft-IIS/6.0 > X-Powered-By: ASP.NET > X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA > date=200705111440)/Tomcat-5.5 > SOAPAction: "http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"; > Content-Type: text/xml;charset=utf-8 > Content-Length: 538 > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>urn:uuid:297a0df9-d5d6-4ff9-850d-7ff7a9740178 xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"; > RelationshipType="reply">urn:uuid:c211d39e-e26b-4345-8c4a-a5c931ec210d > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse /> > == > A "patch" for this issue already exists in JIRA - but it doesn't seem to > work. Looking at the code around the patch, there are explicit calls to > classes in the org.apache.cxf.ws.addressing.v200408 package. > https://issues.apache.org/jira/browse/CXF-1216 > The class in question is org/apache/cxf/ws/addressing/VersionTransformer.java > It is located in \rt\ws\addr\src\main\java > It uses many classes in the org.apache.cxf.ws.addressing.v200408 package to > construct the returned objects. This should really be upgraded to a newer > namespace. > In order to be compatible with WCF, the new namespace for addressing should > be at a minimum: http://www.w3.org/2005/08/addressing > I am sure the fix will entail upgrading the package of classes found in: > org.apache.cxf.ws.addressing.v200408 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3285) JAX-RS: Avoid implicit use of regular expression in JAXRSUtils.intersectMimeTypes
JAX-RS: Avoid implicit use of regular expression in JAXRSUtils.intersectMimeTypes - Key: CXF-3285 URL: https://issues.apache.org/jira/browse/CXF-3285 Project: CXF Issue Type: Improvement Components: JAX-RS Affects Versions: 2.3.1 Environment: JDK 1.6 Reporter: Ka-Lok Fung Priority: Minor Fix For: 2.3.3 While profiling CXF 2.3.1, we found that a small hotspot in JAXRSUtils.intersectMimeTypes. Splitting on + triggers the Pattern to be compiled twice and caused unnecessary code to be run because you're only interested in strings that only have one +. When we replaced that code with equivalent code using String.indexOf and String.substring, the code was ~3% faster. In terms of absolute time in milliseconds here are the values (the test involved 1 million requests), Index of and substring: 2635933-361906=2274027 No intersect improvement: 2724713-367039=2357674 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-3280:
-
Assignee: Freeman Fang
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
>Assignee: Freeman Fang
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
> That can result in errors like this one, where it only tries to load included
> IDL files from the first -I location rather than also trying from -I subdir2.
> {code}
> idl2wsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl - Progress FUSE Services Framework 2.2.10-fuse-00-00
> Error : java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> org.apache.cxf.tools.common.ToolException: java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:72)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLToWSDLProcessor.process(IDLToWSDLProcessor.java:78)
> at org.apache.cxf.tools.corba.IDLToWSDL.execute(IDLToWSDL.java:73)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:58)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:40)
> at org.apache.cxf.tools.corba.IDLToWSDL.run(IDLToWSDL.java:162)
> at org.apache.cxf.tools.corba.IDLToWSDL.main(IDLToWSDL.java:170)
> Caused by: java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:106)
> at java.io.FileInputStream.(FileInputStream.java:66)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
> at java.net.URL.openStream(URL.java:1009)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IncludeStackEntry.(IncludeStackEntry.java:40)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.pushInclude(IdlPreprocessorReader.java:108)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.handleInclude(IdlPreprocessorReader.java:297)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.fillBuffer(IdlPreprocessorReader.java:174)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.(IdlPreprocessorReader.java:100)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:57)
> ... 7 more
> Error : java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3274) JAX RS @FormParam error
[ https://issues.apache.org/jira/browse/CXF-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986208#action_12986208 ] Chris A. Mattmann commented on CXF-3274: Thanks Sergey! So 2.3.3 should fix this? > JAX RS @FormParam error > --- > > Key: CXF-3274 > URL: https://issues.apache.org/jira/browse/CXF-3274 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.2.7, 2.3.2, 2.4 > Environment: testing within Apache OODT cas-curator component >Reporter: Chris A. Mattmann >Assignee: Sergey Beryozkin >Priority: Blocker > Fix For: 2.4, 2.3.3 > > > Hi Guys: > I'm noticing a bug when trying to read the value of a @FormParam variable > within a Resource Service. I've reported what I'm seeing on the mailing list: > http://s.apache.org/jc > I've also confirmed that this isn't related to CXF-3147. > I've filed OODT-118 to track this on the OODT end. > Any help would be appreciated. > Cheers, > Chris -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3280) idl2wsdl does not process multiple include directories -I correctly.
[
https://issues.apache.org/jira/browse/CXF-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986265#action_12986265
]
Freeman Fang commented on CXF-3280:
---
Hi Torsten,
Thanks for the patch.
And your patch left some new added files/folder like Parent.wsdl,
expected_Parent.wsdl, subdir1, subdir2.
You can use
svn add new_add_file_or_folder
before you run
svn diff
to generate the patch which should contain new added files/folders.
Thanks
Freeman
> idl2wsdl does not process multiple include directories -I correctly.
> --
>
> Key: CXF-3280
> URL: https://issues.apache.org/jira/browse/CXF-3280
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.3.2
>Reporter: Torsten Mielke
>Assignee: Freeman Fang
> Attachments: CXF-3280.patch
>
>
> If you run
> {code}
> idl2wsdl -verbose -o ../../../wsdl/ -I . -I ../../tmf/ -I . -I ../ emsMgr.idl
> {code}
> with multiple -I options specified, idl2wsdl will only process the
> first occurrence of -I and skip all others. As a result included IDL
> files that reside in different subdirectories are not found.
> That can result in errors like this one, where it only tries to load included
> IDL files from the first -I location rather than also trying from -I subdir2.
> {code}
> idl2wsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl -verbose -o C:/Temp/ -I subdir1 -I subdir2 Parent.idl
> idltowsdl - Progress FUSE Services Framework 2.2.10-fuse-00-00
> Error : java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> org.apache.cxf.tools.common.ToolException: java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:72)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLToWSDLProcessor.process(IDLToWSDLProcessor.java:78)
> at org.apache.cxf.tools.corba.IDLToWSDL.execute(IDLToWSDL.java:73)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:58)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:40)
> at org.apache.cxf.tools.corba.IDLToWSDL.run(IDLToWSDL.java:162)
> at org.apache.cxf.tools.corba.IDLToWSDL.main(IDLToWSDL.java:170)
> Caused by: java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:106)
> at java.io.FileInputStream.(FileInputStream.java:66)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
> at java.net.URL.openStream(URL.java:1009)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IncludeStackEntry.(IncludeStackEntry.java:40)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.pushInclude(IdlPreprocessorReader.java:108)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.handleInclude(IdlPreprocessorReader.java:297)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.fillBuffer(IdlPreprocessorReader.java:174)
> at
> org.apache.cxf.tools.corba.idlpreprocessor.IdlPreprocessorReader.(IdlPreprocessorReader.java:100)
> at
> org.apache.cxf.tools.corba.processors.idl.IDLProcessor.process(IDLProcessor.java:57)
> ... 7 more
> Error : java.io.FileNotFoundException:
> C:\FUSE\src\CXF\cxf-2.3.x-fuse-branch\tools\corba\src\test\resources\idl\subdir1\Included2.idl
> (The system cannot find the file specified)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
