[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Pedro Igor Silva (Jira)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Pedro Igor Silva edited comment on ELY-1525 at 7/9/19 6:44 PM:
---------------------------------------------------------------
[~dlofthouse], in Keycloak we do handle HTTP POST when the server redirects the user back to a client after a successful authentication. Usually, these requests are communicating a token that asserts the user identity after the authentication. I would say that the only requirement is that we need to be able to get HTTP POST parameters, cookies and headers, but no need to handle files.
was (Author: pcraveiro):
[~dlofthouse], in Keycloak we do handle HTTP POST when the server redirects the user back to a client after a successful authentication. Usually, these requests are communicating a token that asserts the user identity after the authentication. I would say that the only requirement is that we need to be able to get HTTP POST parameters, but no need to handle files.
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.10.0.CR3
>
> Attachments: 0001-ELY-1525-Initialize-FormParserFactory-with-FormEncod.patch, ely-1515-reproducer.zip
>
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Pedro Igor Silva (Jira)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Pedro Igor Silva commented on ELY-1525:
---------------------------------------
[~dlofthouse], in Keycloak we do handle HTTP POST when the server redirects the user back to a client after a successful authentication. Usually, these requests are communicating a token that asserts the user identity after the authentication. I would say that the only requirement is that we need to be able to get HTTP POST parameters, but no need to handle files.
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.10.0.CR3
>
> Attachments: 0001-ELY-1525-Initialize-FormParserFactory-with-FormEncod.patch, ely-1515-reproducer.zip
>
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12276) Create a sitemap for docs.wildfly.org
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12276?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12276:
---------------------------------------
Assignee: Brian Stansberry
> Create a sitemap for docs.wildfly.org
> -------------------------------------
>
> Key: WFLY-12276
> URL: https://issues.jboss.org/browse/WFLY-12276
> Project: WildFly
> Issue Type: Task
> Components: Documentation
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: sitemap.xml
>
>
> I've seen that google reports pages from various versions of our docs as the 'canonical' version of the page.[1] This is understandable, as google has no way know what's 'canonical', e.g. that the 17 folder is more relevant than the 14 folder and in many cases the pages themselves are identical. But I presume this will mean docs searches are more likely to direct people to older docs versions.
> Of the various ways to improve this, the one that seems *possibly* practical is to add a sitemap file[2]. There are way too many pages to cover them all, but perhaps covering the root page for the version plus the root page of the various documents (Admin Guide, Developer Guide, etc) will suffice to get crawlers to focus on those pages, and then the rest will be ranked appropriately based on crawling from those roots. Or not; I'm no SEO SME. ;)
> Part of the PR for adding docs for a new release would then be to update the sitemap doc, e.g. to replace '17' in URLs with '18'.
> [~jamezp] FYI.
> [1] https://support.google.com/webmasters/answer/139066
> [2] https://support.google.com/webmasters/answer/183668?hl=en&ref_topic=4581190
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-4474) Missing path validation of a log file while update path
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4474?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4474:
---------------------------------------
So what happens is that the second command resets the {{relative-to}} attribute to {{undefined}}. This is because "C:\\server.log" is determined to be a absolute path. The only way to fix this would be to remove the {{FileCorrector}}, but that would be a fairly big change in behavior IMO.
> Missing path validation of a log file while update path
> --------------------------------------------------------
>
> Key: WFCORE-4474
> URL: https://issues.jboss.org/browse/WFCORE-4474
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 9.0.0.Beta4
> Reporter: Vratislav Marek
> Assignee: James Perkins
> Priority: Major
>
> After the first successful set of a valid path, you can set an invalid path.
> It is can be relative to that while "relative-to" parameter is overridden, the validator doesn't validate it.
> Discovered on Windows.
> A code block is divided, but it is holding sequence to reproduce.
> _This works as expected._
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char <
> :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:/server.log",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char <
> :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:server.log",
> "rolled-back" => true
> }
> {code}
> _Still works as expected. But After this successful write-attribute command, it that changing._
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log})
> {"outcome" => "success"}
> {code}
> *Now there is a problem, it that not works as expected. The validator accepts invalid path.*
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log})
> {"outcome" => "success"}
> {code}
> _But not accept all invalid paths._
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:*server.log})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char <
> *> at index 2: C:*server.log",
> "rolled-back" => true
> }
> {code}
> _Verification if the unsuccessful update changes something. But not._
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log})
> {"outcome" => "success"}
> {code}
> _Verification if is really set in the property value. Yes_
> {code:bash}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file)
> {
> "outcome" => "success",
> "result" => {"path" => "C:\\server.log"}
> }
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file)
> {
> "outcome" => "success",
> "result" => {"path" => "C:server.log"}
> }
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file)
> {
> "outcome" => "success",
> "result" => {"path" => "C:/server.log"}
> }
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log})
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file)
> {
> "outcome" => "success",
> "result" => {"path" => "C:server.log"}
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12276) Create a sitemap for docs.wildfly.org
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12276?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12276:
-----------------------------------------
Thanks; that looks like it covers things.
We'd want to remove the 16 and earlier URLs. Per the docs in [1] from the description, when using a sitemap to specify canonical URLs:
"Don't include non-canonical pages in a sitemap. If using a sitemap, specify only canonical URLs in the sitemap."
> Create a sitemap for docs.wildfly.org
> -------------------------------------
>
> Key: WFLY-12276
> URL: https://issues.jboss.org/browse/WFLY-12276
> Project: WildFly
> Issue Type: Task
> Components: Documentation
> Reporter: Brian Stansberry
> Priority: Major
> Attachments: sitemap.xml
>
>
> I've seen that google reports pages from various versions of our docs as the 'canonical' version of the page.[1] This is understandable, as google has no way know what's 'canonical', e.g. that the 17 folder is more relevant than the 14 folder and in many cases the pages themselves are identical. But I presume this will mean docs searches are more likely to direct people to older docs versions.
> Of the various ways to improve this, the one that seems *possibly* practical is to add a sitemap file[2]. There are way too many pages to cover them all, but perhaps covering the root page for the version plus the root page of the various documents (Admin Guide, Developer Guide, etc) will suffice to get crawlers to focus on those pages, and then the rest will be ranked appropriately based on crawling from those roots. Or not; I'm no SEO SME. ;)
> Part of the PR for adding docs for a new release would then be to update the sitemap doc, e.g. to replace '17' in URLs with '18'.
> [~jamezp] FYI.
> [1] https://support.google.com/webmasters/answer/139066
> [2] https://support.google.com/webmasters/answer/183668?hl=en&ref_topic=4581190
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Gail Badner (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-12063:
------------------------------------
[~smarlow], thanks for doing that. Did you happen to look at diffs between 1.9.5 and 1.9.11?
[~sannegrinovero], I see that you upgraded ByteBuddy to 1.9.10 for HHH-13272. Do you have an opinion on upgrading ByteBuddy to 1.9.11 in master and 5.3 branches?
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12063:
-------------------------------------
Hi Gail, I verified that the failing tests, do pass with ByteBuddy 1.9.11.
I also ran the following tests as well via a local script with 1.9.11 and they passed:
{quote}
cd testsuite/integration/basic/
mvn install -Dtest=org.jboss.as.test.integration.jpa.packaging.PersistenceUnitPackagingTestCase > /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.packaging.EJBJarPackagingTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.packaging.PersistenceUnitWarPackagingTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.multipleinjections.MultiplePersistenceContextInjectionsTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.webnontxem.NonTransactionalEmTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.ormxml.OrmTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.jarfile.JpaJarFileTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.jarfile.JpaTestSlsb >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.webtxem.TestServlet >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.webtxem.WebJPATestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.basic.entitymanagerfactorytest.EntityManagerFactoryTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.basic.relativedatasourcetest.RelativeDataSourceNameTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.contextduel.AddEPC2TxAfterPCTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.serialization.SerializationTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.shallow.ShallowExtendedPersistenceContextInheritanceTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.requiresnew.EPCPropagationNewTransactionTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.hierarchy.EPCPropagationHierarchyTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.slsbxpc.FailBecauseOfXPCNotInSFSBTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.epcpropagation.unsync.TestForMixedSynchronizationTypes >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.transaction.TransactionTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.transaction.envers.TransactionAuditedTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.dsrestart.JpaDsRestartTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.beanvalidation.beanvalidationinheritancetest.BeanValidationJPAInheritanceTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.beanvalidation.beanvalidationtest.JPABeanValidationTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.beanvalidation.cdi.BeanValidationCdiIntegrationTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.datasourcedefinition.DataSourceDefinitionJPATestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TestPersistenceProvider >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TestEntityManager >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TestEntityManagerFactory >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.classtransformer.TestClassTransformer >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.classtransformer.TestAdapter >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.classtransformer.ClassFileTransformerTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.classtransformer.TestPersistenceProvider >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.classtransformer.TestEntityManagerFactory >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.sibling.SiblingXPCInheritanceTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.version.VersionTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.resourcelocal.ResourceLocalTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.classfiletransformertest.ClassFileTransformerTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.management.ManagementTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.jpa.hibernate.EntityTest >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.Hibernate4NativeAPIProviderTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.HibernateNativeAPITransactionTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.generator.TestSlsb >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.generator.PooledGeneratorTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.search.HibernateSearchJPATestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.naturalid.HibernateNativeAPINaturalIdTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.Hibernate2LCacheStatsTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.envers.Hibernate4NativeAPIEnversTestCase >> /tmp/orm53.txt
mvn install -Dtest=org.jboss.as.test.integration.hibernate.secondlevelcache.HibernateSecondLevelCacheTestCase >> /tmp/orm53.txt
{quote}
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Gail Badner (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-12063:
------------------------------------
[~smarlow], ORM master (and 5.4.2) use ByteBuddy 1.9.10.
ORM 5.3.11 uses ByteBuddy 1.9.5.
Have you tried running the failing tests with JDK 13 and ByteBuddy 1.9.10 or 1.9.11? If not, I can do it.
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12276) Create a sitemap for docs.wildfly.org
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12276?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-12276:
--------------------------------------
I've not yet read those links, but the attached sitemap.xml I generated using a nodejs command.
> Create a sitemap for docs.wildfly.org
> -------------------------------------
>
> Key: WFLY-12276
> URL: https://issues.jboss.org/browse/WFLY-12276
> Project: WildFly
> Issue Type: Task
> Components: Documentation
> Reporter: Brian Stansberry
> Priority: Major
> Attachments: sitemap.xml
>
>
> I've seen that google reports pages from various versions of our docs as the 'canonical' version of the page.[1] This is understandable, as google has no way know what's 'canonical', e.g. that the 17 folder is more relevant than the 14 folder and in many cases the pages themselves are identical. But I presume this will mean docs searches are more likely to direct people to older docs versions.
> Of the various ways to improve this, the one that seems *possibly* practical is to add a sitemap file[2]. There are way too many pages to cover them all, but perhaps covering the root page for the version plus the root page of the various documents (Admin Guide, Developer Guide, etc) will suffice to get crawlers to focus on those pages, and then the rest will be ranked appropriately based on crawling from those roots. Or not; I'm no SEO SME. ;)
> Part of the PR for adding docs for a new release would then be to update the sitemap doc, e.g. to replace '17' in URLs with '18'.
> [~jamezp] FYI.
> [1] https://support.google.com/webmasters/answer/139066
> [2] https://support.google.com/webmasters/answer/183668?hl=en&ref_topic=4581190
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months