You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by co...@jakarta.apache.org on 2004/10/08 09:43:51 UTC
[jira] Created: (JELLY-154) invoke tag should allow to support literal parameters in nested tags
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-154
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-154
Summary: invoke tag should allow to support literal parameters in nested tags
Type: Improvement
Status: Unassigned
Priority: Major
Project: jelly
Components:
taglib.soap
Assignee:
Reporter: Michael Altenhofen
Created: Fri, 8 Oct 2004 12:42 AM
Updated: Fri, 8 Oct 2004 12:42 AM
Description:
The current version (1.6) of InvokeTag's doTag method does not allow me to write something like this:
<?xml version="1.0"?>
<j:jelly trim="false" xmlns:soap="jelly:soap" xmlns:j="jelly:core" xmlns:ju="jelly:util">
<j:catch var="ex">
1. Define variables to hold invocation parameters
<j:set var="endpoint">http://aws-beta.amazon.com/onca/soap?Service=AWSProductData</j:set>
<j:set var="namespace"/>
<j:set var="method">ItemSearch</j:set>
2. Load the parameters for the call from the file itemssearch_params.xml
<ju:loadText file="itemsearch_params.xml" var="params"/>
3. Invoke the web service using the parameters we've just read in
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">${params}</soap:invoke>
</j:catch>
<j:if test="${ex != null}">
Execption ${ex.message} occured
</j:if>
</j:jelly>
I've posted this issue into standard bugzilla (Bug #31542) but was advised to post it here again.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-154) invoke tag should allow to support literal parameters in nested tags
Posted by co...@jakarta.apache.org.
The following comment has been added to this issue:
Author: Michael Altenhofen
Created: Wed, 13 Oct 2004 4:11 AM
Body:
Ok,
maybe my example was a bit misleading. What you cannot do in the current version is something like this:
<j:set var="endpoint">http://aws-beta.amazon.com/onca/soap?Service=AWSProductData</j:set>
<j:set var="namespace"/>
<j:set var="method">ItemSearch</j:set>
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">
<SubscriptionId>xxx</SubscriptionId>
<Request>
<Keywords>Perl</Keywords>
<SearchIndex>Books</SearchIndex>
</Request>
</soap:invoke>
As I understand the code, the current version would turn that parameter set into one parameter object (essentially a String).
Using the original code I couldn't get the Amazon WS reply something useful.
To me, it looks "natural" that I can just "inline" the SOAPBody part of the call.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JELLY-154?page=comments#action_53986
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-154
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-154
Summary: invoke tag should allow to support literal parameters in nested tags
Type: Improvement
Status: Unassigned
Priority: Major
Project: jelly
Components:
taglib.soap
Assignee:
Reporter: Michael Altenhofen
Created: Fri, 8 Oct 2004 12:42 AM
Updated: Wed, 13 Oct 2004 4:11 AM
Description:
The current version (1.6) of InvokeTag's doTag method does not allow me to write something like this:
<?xml version="1.0"?>
<j:jelly trim="false" xmlns:soap="jelly:soap" xmlns:j="jelly:core" xmlns:ju="jelly:util">
<j:catch var="ex">
1. Define variables to hold invocation parameters
<j:set var="endpoint">http://aws-beta.amazon.com/onca/soap?Service=AWSProductData</j:set>
<j:set var="namespace"/>
<j:set var="method">ItemSearch</j:set>
2. Load the parameters for the call from the file itemssearch_params.xml
<ju:loadText file="itemsearch_params.xml" var="params"/>
3. Invoke the web service using the parameters we've just read in
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">${params}</soap:invoke>
</j:catch>
<j:if test="${ex != null}">
Execption ${ex.message} occured
</j:if>
</j:jelly>
I've posted this issue into standard bugzilla (Bug #31542) but was advised to post it here again.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-154) invoke tag should allow to support literal parameters in nested tags
Posted by co...@jakarta.apache.org.
The following comment has been added to this issue:
Author: Paul Libbrecht
Created: Fri, 8 Oct 2004 1:20 AM
Body:
In your example, I don't understand why using params="${params}" is not enough.
Maybe you can provide another example ?
Do you want to do something like:
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">
${paramSeries1}
${paramSeries2}
</soap:invoke>
Or maybe something more elaborate such as using j:forEach ?
thanks
paul
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JELLY-154?page=comments#action_53832
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-154
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-154
Summary: invoke tag should allow to support literal parameters in nested tags
Type: Improvement
Status: Unassigned
Priority: Major
Project: jelly
Components:
taglib.soap
Assignee:
Reporter: Michael Altenhofen
Created: Fri, 8 Oct 2004 12:42 AM
Updated: Fri, 8 Oct 2004 1:20 AM
Description:
The current version (1.6) of InvokeTag's doTag method does not allow me to write something like this:
<?xml version="1.0"?>
<j:jelly trim="false" xmlns:soap="jelly:soap" xmlns:j="jelly:core" xmlns:ju="jelly:util">
<j:catch var="ex">
1. Define variables to hold invocation parameters
<j:set var="endpoint">http://aws-beta.amazon.com/onca/soap?Service=AWSProductData</j:set>
<j:set var="namespace"/>
<j:set var="method">ItemSearch</j:set>
2. Load the parameters for the call from the file itemssearch_params.xml
<ju:loadText file="itemsearch_params.xml" var="params"/>
3. Invoke the web service using the parameters we've just read in
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">${params}</soap:invoke>
</j:catch>
<j:if test="${ex != null}">
Execption ${ex.message} occured
</j:if>
</j:jelly>
I've posted this issue into standard bugzilla (Bug #31542) but was advised to post it here again.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (JELLY-154) invoke tag should allow to support literal parameters in nested tags
Posted by co...@jakarta.apache.org.
The following issue has been updated:
Updater: Michael Altenhofen (mailto:michael.altenhofen@web.de)
Date: Fri, 8 Oct 2004 12:43 AM
Changes:
Attachment changed to jelly-tags-soap-patch.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JELLY-154?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-154
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-154
Summary: invoke tag should allow to support literal parameters in nested tags
Type: Improvement
Status: Unassigned
Priority: Major
Project: jelly
Components:
taglib.soap
Assignee:
Reporter: Michael Altenhofen
Created: Fri, 8 Oct 2004 12:42 AM
Updated: Fri, 8 Oct 2004 12:43 AM
Description:
The current version (1.6) of InvokeTag's doTag method does not allow me to write something like this:
<?xml version="1.0"?>
<j:jelly trim="false" xmlns:soap="jelly:soap" xmlns:j="jelly:core" xmlns:ju="jelly:util">
<j:catch var="ex">
1. Define variables to hold invocation parameters
<j:set var="endpoint">http://aws-beta.amazon.com/onca/soap?Service=AWSProductData</j:set>
<j:set var="namespace"/>
<j:set var="method">ItemSearch</j:set>
2. Load the parameters for the call from the file itemssearch_params.xml
<ju:loadText file="itemsearch_params.xml" var="params"/>
3. Invoke the web service using the parameters we've just read in
<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">${params}</soap:invoke>
</j:catch>
<j:if test="${ex != null}">
Execption ${ex.message} occured
</j:if>
</j:jelly>
I've posted this issue into standard bugzilla (Bug #31542) but was advised to post it here again.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org