[jira] [Updated] (COCOON-2315) WebserviceGenerator should allow to include the request headers of the caller.
[
https://issues.apache.org/jira/browse/COCOON-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel updated COCOON-2315:
-
Summary: WebserviceGenerator should allow to include the request headers of
the caller. (was: Generator and CInclude transformer do not include the
request headers of the caller.)
That looks as if you expect Cocoon to act as forward proxy. I suggest you send
a description of the actual problem to us...@cocoon.apache.org.
> WebserviceGenerator should allow to include the request headers of the caller.
> --
>
> Key: COCOON-2315
> URL: https://issues.apache.org/jira/browse/COCOON-2315
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
>Affects Versions: 2.1.9, 2.1.12-dev (Current SVN)
>Reporter: Alec Bickerton
>
> When using the file generator or any sub class. The request headers are not
> propagated to the source.
> e.g.
> {code}
>
> http://deviceMetaService.example.com/lookup.jsp"/>
>
>
> {code}
> The request received by the http://deviceMetaService.example.com/lookup.jsp
> will not contain the user-agent header of the original request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COCOON-2169) ImageOp resize effect has broken/useless default dimensions
[ https://issues.apache.org/jira/browse/COCOON-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2169. Resolution: Fixed Assuming lazy consense that issue is solved. > ImageOp resize effect has broken/useless default dimensions > --- > > Key: COCOON-2169 > URL: https://issues.apache.org/jira/browse/COCOON-2169 > Project: Cocoon > Issue Type: Bug > Components: Blocks: ImageOp >Affects Versions: 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12-dev (Current SVN), > 2.2 >Reporter: Mark Lundquist >Assignee: Alfred Nathaniel >Priority: Minor > Attachments: smime.p7s > > > Class ResizeOperation in the ImageOp block has broken/useless default values > for the "height" and "width" parameters. The only reasonable default values > are zero. Zero height or width has a special meaning. > I am passing these parameters in from the sitemap using the request parameter > input module. If the parameter doesn't exist, I need the "zero" value and > behavior from the Reader. Setting the dimension to e.g. "300" is broken. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COCOON3-77) Text and JSON serializers
[ https://issues.apache.org/jira/browse/COCOON3-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113269#comment-13113269 ] Thorsten Scherler commented on COCOON3-77: -- I had a look at the source you attached. It is hard to apply the patch if it is not a svn diff. This way I am not sure where to place the files. e.g. public class TextSerializer extends XMLSerializer but the package is org.apache.cocoon.components.serializers.util; and you do not have an import org.apache.cocoon.sax.component.XMLSerializer That will lead to compile errors. Further shouldn't that Serializer not extends AbstractSAXSerializer instead? > Text and JSON serializers > - > > Key: COCOON3-77 > URL: https://issues.apache.org/jira/browse/COCOON3-77 > Project: Cocoon 3 > Issue Type: Improvement > Components: cocoon-optional >Affects Versions: 3.0.0-alpha-3 >Reporter: Andre Juffer >Priority: Minor > Attachments: EncodingJsonSerializer.java, > EncodingTextSerializer.java, JsonSerializer.java, TextEncoder.java, > TextSerializer.java, pom.xml, tribc-cocoon-3.xml > > > Serveral classes have been created for serializing text and JSON in the > sitemap. The JsonSerializer also checks whether the JSON text actually is > valid. The organization of the classes follows the encoding serializers (such > as the EncodingHTMLSerializer). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
