[
https://issues.apache.org/jira/browse/SLING-12392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-12392:
-
Description:
A sitemap for Coveo is not fully supported by the Apache Sitemap due to
[
https://issues.apache.org/jira/browse/SLING-12392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868464#comment-17868464
]
Andreas Schaefer commented on SLING-12392:
--
Right now there is only one
Andreas Schaefer created SLING-12392:
Summary: Sitemap is not supporting other Sitemaps like Coveo
Key: SLING-12392
URL: https://issues.apache.org/jira/browse/SLING-12392
Project: Sling
Generator - we are using queries for Coveo
sitemaps
I can create a POC but I don’t want to spend my time on it if nobody is
interested.
Cheers - Andy
> On Jun 27, 2024, at 1:54 PM, Andreas Schaefer wrote:
>
> Hi
>
> I am working on an implementation of Apache Sling Sitemaps f
Hi
I am working on an implementation of Apache Sling Sitemaps for a client and ran
into two major issues:
1. As of now the Extension Prefix is added to all XML elements but in my case
this is causing an issue
2. Sitemap Storage is not available outside the package
For 1. I need to remove the p
[
https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-12053:
Assignee: Andreas Schaefer
> Upgrade Sling GraphQL Core to Graphql-Java 2
[
https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770495#comment-17770495
]
Andreas Schaefer commented on SLING-12053:
--
I suggested a version check in
[
https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770244#comment-17770244
]
Andreas Schaefer commented on SLING-12053:
--
When I took Sling GraphQL
Andreas Schaefer created SLING-12053:
Summary: Upgrade Sling GraphQL Core to Graphql-Java 21.x
Key: SLING-12053
URL: https://issues.apache.org/jira/browse/SLING-12053
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768921#comment-17768921
]
Andreas Schaefer commented on SLING-12027:
--
[~radu] Does not do the tric
Hi
This is still push is still pending. Can a PMC do it for me as I cannot.
Cheers - Andy
> On Sep 19, 2023, at 12:49 PM, Andreas Schaefer
> wrote:
>
> Can a PMC push the release to
> https://dist.apache.org/repos/dist/release/sling/. I will finish the rest
> afterwards.
[
https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767252#comment-17767252
]
Andreas Schaefer commented on SLING-12027:
--
I found the cause of the i
[
https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767199#comment-17767199
]
Andreas Schaefer commented on SLING-12027:
--
Here are some excerpts of
[
https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767174#comment-17767174
]
Andreas Schaefer commented on SLING-12027:
--
The current PR for this ticke
Hi
I was asked to review PR:
https://github.com/apache/sling-org-apache-sling-graphql-core/pull/38 and I
cannot debug the issue.
So from the output I see this:
- GraphQLServlet.doPostPersistedQuery() fails because the Query validation
returns false
- Response.setError BAD REQUEST
- Sl
Hi
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Joerg Hoh, Robert Munteanu
+1 (non binding): none
Can a PMC push the release to
https://dist.apache.org/repos/dist/release/sling/. I will finish the rest
afterwards.
Cheers - Andy
ote:
>
> Hi Andy,
>
> On Mon, 2023-09-18 at 09:53 -0700, Andreas Schaefer wrote:
>> Hi
>>
>> I need one more vote to release Sling GraphQL Core 0.0.24. This has
>> an important update to handle fields with the same simple name aka
>> name. Right now previou
Hi
I need one more vote to release Sling GraphQL Core 0.0.24. This has an
important update to handle fields with the same simple name aka name. Right now
previous fields are dropped and so I moved that to a Multi Value Map to avoid
it and to make FQNs the unique field name.
Cheers - Andy
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/browse/SLING-12014
There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING-10901
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2781
You can use this UNIX s
[
https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10901:
-
Fix Version/s: GraphQL Core 0.0.26
(was: GraphQL Core 0.0.24
[
https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-12014:
-
Fix Version/s: GraphQL Core 0.0.24
> GraphQL Core needs to support additional fie
[
https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer resolved SLING-12014.
--
Resolution: Fixed
PR was merged into master
> GraphQL Core needs to supp
[
https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer closed SLING-12014.
> GraphQL Core needs to support additional fields from GraphQL J
[
https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760638#comment-17760638
]
Andreas Schaefer commented on SLING-12014:
--
Create a PR for this enhancem
[
https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-12014:
Assignee: Andreas Schaefer
> GraphQL Core needs to Support Addition Fields f
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-11458:
Assignee: Andreas Schaefer (was: Radu Cotescu)
> Regress - "Writer has
Andreas Schaefer created SLING-12014:
Summary: GraphQL Core needs to Support Addition Fields from
GraphQL Java
Key: SLING-12014
URL: https://issues.apache.org/jira/browse/SLING-12014
Project
+1 (non-binding)
- Andy
> On Aug 15, 2023, at 6:26 AM, Radu Cotescu wrote:
>
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710&version=12353543&styleName=Text
>
> Staging repository:
> https://repository.apache.org/content
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754179#comment-17754179
]
Andreas Schaefer commented on SLING-11458:
--
The Servlet Writer should no
The Apache Sling team is pleased to announce the release of Apache Sling
GraphQL Core version 0.0.22
Apache Sling is a web framework that uses a Java Content Repository, such as
Apache Jackrabbit, to store and manage content. Sling applications use either
scripts or Java servlets, selected base
Hi
Can any PMC push the artifact to
https://dist.apache.org/repos/dist/release/sling/ ?
I need to have this release out as soon as possible - Thanks
> On Jul 26, 2023, at 12:31 AM, Andreas Schaefer
> wrote:
>
> Hi,
>
> I finishing the release of GraphQL that Radu cr
Hi,
I finishing the release of GraphQL that Radu created for me as my travel
computer cannot sign a release.
The vote has passed with the following result :
+1 (binding): Robert Munteanu, Casten Ziegler, Joerg Hoh, Daniel Klco
+1 (non binding): Andreas Schaefer
Can a PMC push this release to
I am sorry to be a little pushy here but this is an important release to
upgrade to the latest GraphQL-java because of security vulnerabilities in v15.0.
The previous release failed to address an issue with Inlined Fragments which
are dropped by graphql-java but it can be resolved with the Objec
+1 (non-binding)
Thank to Radu for cutting the release for me due to my travel.
- Andy
> On Jul 20, 2023, at 9:49 AM, Radu Cotescu wrote:
>
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12353082
>
> Staging repository:
> https://repo
Hi
After limiting the Jenkins build to JDK 11 to release a fix required for the
last release the build is still failing with a pretty weird issue:
https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-apache-sling-graphql-core/detail/PR-36/4/pipeline/
It cannot do
-mock.junit4. That said I did upgrade the used Oak version in that
module to 1.52.0 and it still did not work.
- Andy
> On Jul 19, 2023, at 10:44 AM, Robert Munteanu wrote:
>
> On Wed, 2023-07-19 at 10:40 +0200, Andreas Schaefer wrote:
>> After some back and forth I saw that the Pax
is using org.apache.sling.testing.sling-mock.junit4 and so I tried
to use a newer version of oak-jcr (1.52.0) but that did not solve the issue.
Any idea on how to fix this?
- Andy
> On Jul 18, 2023, at 4:00 PM, Andreas Schaefer
> wrote:
>
> I tried to upgrade a few depe
to fix that?
- Andy
> On Jul 18, 2023, at 10:46 AM, Andreas Schaefer
> wrote:
>
> Hi Robert
>
> My problem is not there yet but I updated the wiki page with the issue and my
> discovery so far.
>
> When I upgrade to Mockito-Inline 5.2.0 the compilation issue go
I ran into other issues so I don’t
think upgrading would work but I don’t know.
- Andy
> On Jul 18, 2023, at 9:59 AM, Robert Munteanu wrote:
>
> Hi Andy,
>
> On Tue, 2023-07-18 at 09:47 +0200, Andreas Schaefer wrote:
>> Hi
>>
>> For my latest PR for Sling
Hi
For my latest PR for Sling GraphQL Core I am running into CI build issues on
Java 17:
https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-apache-sling-graphql-core/detail/PR-36/3/pipeline
Any idea on how to resolve this?
Cheers - Andy
[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741219#comment-17741219
]
Andreas Schaefer commented on SLING-11920:
--
I created a PR
[h
[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11920:
-
Description:
Intermediary fields are not exposed as Selected Fields in Graphql-java and
[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738806#comment-17738806
]
Andreas Schaefer commented on SLING-11920:
--
This is a follow up of SLING-1
Andreas Schaefer created SLING-11920:
Summary: Expose Object Type Names in Selected Field
Key: SLING-11920
URL: https://issues.apache.org/jira/browse/SLING-11920
Project: Sling
Issue
Hi
The vote passed with the following result:
+1 (binding): Radu Cotescu, Robert Munteanu, Stefan Seifert
Can a PMC push the release to https://dist.apache.org/repos/dist/release/sling/
for me?
Cheers - Andy Schaefer
Hi
Back in 3/31/23 I wrote an email for a Vote
(https://lists.apache.org/thread/w3fc01lr5b4nmyx0ftpsk9sjvtb5dvnd) to release
Apache Sling GraphQL Core 0.0.20 that bumps the usage of graphql-java to the
latest 20.1 with a fix to be used in Sling.
The issue here is that the previous version used
Hi
I am running into some temporary issues with Sling PaxExam 3.0.0 due to
‘Authentication Support service missing’.
When I try to upgrade to Sling PaxExam 3.10 I run into this issue which I do
not understand:
[ERROR] com.madplanet.wfx.it.WfxWorkloadIT Time elapsed: 3.424 s <<< ERROR!
org.op
Hi
Last Friday I started a Vote for the release of Sling Graphql Core 0.0.20 which
contains the upgrade to graphql-java version 20.1.
I have two up votes so far and need one more to release it.
This release does not impact Sling releases as this is not part of Sling
Starter package.
Thanks -
Hi
After some back and forth I figured out:
- Maven was using a different GPG Key
- My Apache GPG Key had a sub key which might have caused issues
I verified that when I signed a maven file that the .asc file has the right
fingerprint (gpg ).
So I redid the release and verified on my laptop th
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/browse/SLING-10900
There are still 1 outstanding issue:
https://issues.apache.org/jira/browse/SLING-10901
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2734
You can use this UNIX scr
[
https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10901:
-
Fix Version/s: GraphQL Core 0.0.22
(was: GraphQL Core 0.0.20
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10900:
-
Fix Version/s: GraphQL Core 0.0.20
(was: GraphQL Core 0.0.18
I missed the part of replying to the original email to cancel it.
> On Mar 27, 2023, at 12:47 PM, Andreas Schaefer
> wrote:
>
>
> Hi,
>
> We solved N issues in this release:
>
> https://issues.apache.org/jira/browse/SLING-10900
>
> NOTE: this was tested w
> On Mar 28, 2023, at 1:44 PM, Andreas Schaefer wrote:
>
> Hi,
>
> We solved 1 issues in this release:
>
> https://issues.apache.org/jira/browse/SLING-10900
>
> There are still 1 outstanding issue:
>
> https://issues.apache.org/jira/browse/SLING-10901
on
> 0.0.18. If so, please make sure to follow the process from [1].
>
> Thanks!
>
> Robert
>
> [1]:
> https://sling.apache.org/documentation/development/release-management.html#canceling-the-release-1
>
> On Mon, 2023-03-27 at 12:47 -0700, Andreas Schaefer wrote:
Hi
I set this email out on 3/28/23 but I seems it did not make it into the mailing
list.
I created the release of GraphQL Core 0.0.16 on the wrong branch and so I
cancel this vote and redo this on 0.0.18 while fixing all the issues raised by
Stefan.
Thanks - Andy
Hi
I created a new release of GraphQL Core v 0.0.18 and put it up to a vote but so
far nobody responded.
This is an important release for AEM to fix a security issue in
graphql-java:https://nvd.nist.gov/vuln/detail/CVE-2022-37734
Thanks - Andy
>>> Yes, the steps are outlined in
>>> https://sling.apache.org/documentation/development/release-management.html#appendix-a-creating-and-registering-your-pgp-key
>>> as mentioned by Julian.
>>> You have to manually update the KEYS file in SVN!
>>>
>
l#appendix-a-creating-and-registering-your-pgp-key
> as mentioned by Julian.
> You have to manually update the KEYS file in SVN!
>
> Konrad
>
>> On 29. Mar 2023, at 16:52, Andreas Schaefer wrote:
>>
>> Thanks Julian for the response.
>>
>> If you are refer
tation/development/release-management.html#appendix-a-creating-and-registering-your-pgp-key-1
>
> Regards
> Julian
>
> On Tue, Mar 28, 2023 at 7:44 PM Andreas Schaefer
> wrote:
>>
>> I think I found the solution - waiting until
>> https://dist.apache.org/rep
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/browse/SLING-10900
There are still 1 outstanding issue:
https://issues.apache.org/jira/browse/SLING-10901
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2733
You can use this UNIX scr
Hi
I created the release of GraphQL Core 0.0.16 on the wrong branch and so I
cancel this vote and redo this on 0.0.18 while fixing all the issues raised by
Stefan.
Thanks - Andy
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10900:
-
Fix Version/s: GraphQL Core 0.0.18
(was: GraphQL Core 0.0.16
[
https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10901:
-
Fix Version/s: GraphQL Core 0.0.20
(was: GraphQL Core 0.0.18
I think I found the solution - waiting until
https://dist.apache.org/repos/dist/release/sling/KEYS updates with my new key.
> On Mar 28, 2023, at 9:33 AM, Andreas Schaefer
> wrote:
>
> Hi
>
> I moved to a new computer and did not do much work on Apache. When I prepared
&g
Hi
I moved to a new computer and did not do much work on Apache. When I prepared
for the release of GrpahQL Core 0.0.16 I realized that I did not have a PGP Key
and so I created a new PGP Key using ‘GPG Keychain’ and published that key.
On the Sling Release Key server
(https://dist.apache.org/
[
https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-10901:
-
Fix Version/s: GraphQL Core 0.0.18
(was: GraphQL Core 0.0.16
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer resolved SLING-10900.
--
Resolution: Fixed
Upgraded to graphql-java 20.1 (latest release) as there are nearly
Hi,
We solved N issues in this release:
https://issues.apache.org/jira/browse/SLING-10900
NOTE: this was tested with AEM 6.6
There are still some outstanding issues: none
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2730
https://repository.apache.o
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705660#comment-17705660
]
Andreas Schaefer commented on SLING-10900:
--
After graphql-java released
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695824#comment-17695824
]
Andreas Schaefer edited comment on SLING-10900 at 3/2/23 5:0
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695824#comment-17695824
]
Andreas Schaefer commented on SLING-10900:
--
After some help from the gra
Hi
While dealing with upgrading graphql-java I encountered a rather bizarre issue
with bundles. The class ‘AbstractBundleRequestMojo` has a check on line 159
where it uses a JarFile.getManifest() but that only returns the MANIFEST.MF
when it is the first entry in the JAR file.
That eventually
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694235#comment-17694235
]
Andreas Schaefer commented on SLING-10900:
--
After testing with AEM this is
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691777#comment-17691777
]
Andreas Schaefer commented on SLING-10900:
--
All graphql-java version n
Hi
I ran into a build issue with Sling Graphql Core when I use graphql-java 20.0
(the current released version). Even though that release will not be usable in
an OSGi container the latest code will have the same issue.
The problem is that Pax together with Graphql-java cannot find the
Generic
not a big issue.
There are a few issues that I am working out with the graphql-java team:
- sun.misc is imported in the bundle (resolved)
- MANIFEST.MF is not 1st entry in the JAR file (work in progresss)
Cheers - Andy
> On Feb 3, 2023, at 10:25 AM, Andreas Schaefer
> wrote:
>
>
Core work similar to graphql-java.
I will start without changing Sling and then see if it works out.
- Andy
> On Feb 3, 2023, at 9:03 AM, Radu Cotescu wrote:
>
> Hi Andy,
>
>> On 3 Feb 2023, at 16:40, Andreas Schaefer wrote:
>>
>> Hi
>>
>> I am task
Hi
I am tasked with upgrading grqaphql-java for AEM to at least 17.4 because of a
vulnerability https://nvd.nist.gov/vuln/detail/CVE-2022-37734
I saw that Radu created a ticket for upgrading to graphql-java 17:
https://github.com/graphql-java/graphql-java/releases/tag/v17.0
I assigned that tic
[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-10900:
Assignee: Andreas Schaefer (was: Radu Cotescu)
> Update graphl-java to vers
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637398#comment-17637398
]
Andreas Schaefer commented on SLING-11458:
--
[~radu] I don't mind f
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634573#comment-17634573
]
Andreas Schaefer edited comment on SLING-11458 at 11/16/22 10:0
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634573#comment-17634573
]
Andreas Schaefer commented on SLING-11458:
--
The problem here is that
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634524#comment-17634524
]
Andreas Schaefer commented on SLING-11458:
--
[~radu] Do you know if anyt
Hi
When I use XSSAPI.encodeForHTMLAttr() with this value:
/content/dam/test-folder/">.html
The resulting html tag will be closed on the tag is injected.
I would assume that a method like this will not allow the HTML Attribute to be
closed let alone to close the tag altogether.
Is there a way
[
https://issues.apache.org/jira/browse/SLING-11486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569618#comment-17569618
]
Andreas Schaefer commented on SLING-11486:
--
PR for this ticket can be f
Andreas Schaefer created SLING-11486:
Summary: Allow to use a Writer that check for close as used in
Response Context Support
Key: SLING-11486
URL: https://issues.apache.org/jira/browse/SLING-11486
Hi
I wanted to add a test to the GraphQLServlet to make sure that the closure of
the Writer is causing a test failure but the Response Content Support does not
support that.
So I wanted to suggest a flag on the Mock Sling Http Servlet Response that
would allow to use the same Delete Print Wr
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567402#comment-17567402
]
Andreas Schaefer commented on SLING-11458:
--
I encountered that issue in
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11458:
-
Description:
The GraphQLServlet shouldn't call {{response.getWriter().flush()}} a
[
https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-11458:
Assignee: Andreas Schaefer (was: Bertrand Delacretaz)
> Regress - "Wr
Andreas Schaefer created SLING-11458:
Summary: Regress - "Writer has already been closed" exception in
GraphQLServlet
Key: SLING-11458
URL: https://issues.apache.org/jira/browse/S
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer resolved SLING-11427.
--
Resolution: Fixed
A fix was created in PR #24, approved and merged into master
che-sling-repoinit-parser/pull/24>
- Andy
> On Jun 29, 2022, at 10:26 AM, Andreas Schaefer
> wrote:
>
> I created a ticket for it: https://issues.apache.org/jira/browse/SLING-11427
> <https://issues.apache.org/jira/browse/SLING-11427>
>
> - Andy
>
>>
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560684#comment-17560684
]
Andreas Schaefer commented on SLING-11427:
--
I created a simple 'fix&
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560672#comment-17560672
]
Andreas Schaefer commented on SLING-11427:
--
Adding this line to the en
ks something
> like this:
>
> register nodetypes
> <<===
>http://ns.adobe.com/xap/1.0/sType/Dimensions#'>
> ===>>
>
>
> Regards,
> -Eric
>
>
> On Mon, Jun 27, 2022 at 4:43 PM Andreas Schaefer
> wrote:
>
>> Hi
>
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11427:
-
Description:
Registering a Namespace in the repoinit fails when the URI contains a
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11427:
-
Description:
Registering a Namespace in the repoinit fails when the URI contains a
[
https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11427:
-
Description:
Registering a Namespace in the repoinit fails when the URI contains a
1 - 100 of 877 matches
Mail list logo
