commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-154) invoke tag should allow to support literal parameters in nested tags
Date Wed, 13 Oct 2004 11:12:51 GMT
The following comment has been added to this issue:

     Author: Michael Altenhofen
    Created: Wed, 13 Oct 2004 4:11 AM
maybe my example was a bit misleading. What you cannot do in the current version is something
like this:

<j:set var="endpoint"></j:set>
   <j:set var="namespace"/>
   <j:set var="method">ItemSearch</j:set>

<soap:invoke endpoint="${endpoint}" namespace="${namespace}" method="${method}">

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:

View the issue:

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

   Reporter: Michael Altenhofen

    Created: Fri, 8 Oct 2004 12:42 AM
    Updated: Wed, 13 Oct 2004 4:11 AM

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"></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:if test="${ex != null}">
   Execption ${ex.message} occured


I've posted this issue into standard bugzilla (Bug #31542) but was advised to post it here

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message