[JBoss JIRA] (WFLY-7524) Add Hibernate-Spatial to WildFly Feature Pack
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7524?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-7524:
-----------------------------
Fix Version/s: (was: 10.x.x TBD)
Resetting the fix version as it is still open and 10.0.0.TBD was a long time ago. If it should be resolved, please do so (and close) against the relevant fix version
> Add Hibernate-Spatial to WildFly Feature Pack
> ---------------------------------------------
>
> Key: WFLY-7524
> URL: https://issues.jboss.org/browse/WFLY-7524
> Project: WildFly
> Issue Type: Feature Request
> Affects Versions: 10.1.0.Final
> Environment: Linux / OpenJDK 8 / WildFly 10.1.0.Final
> Reporter: Dennis Gesker
> Assignee: Jason Greene
> Labels: wildfly-feature-pack
>
> If possible kindly add jars need to make use of hibernate-spatial to WildFly-Feature-Pack
> org.hibernate:hibernate-spatial
> org.geolatte:geolatte-geom
> com.vividsolutions:jts-parent
> BTW, thank you for this package. It saves a HUGE amount of time with dependencies.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-7209:
-----------------------------
Resetting the fix version as it is still open and 10.1.0 was a long time ago. If it should be resolved, please do so (and close) against the relevant fix version
> Operation to list installed Resource Adapters
> ---------------------------------------------
>
> Key: WFLY-7209
> URL: https://issues.jboss.org/browse/WFLY-7209
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Guillermo González de Agüero
> Assignee: Stefano Maestri
> Fix For: 10.1.0.Final
>
> Attachments: 1-jdbc.png, 2-ra.png
>
>
> Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers (see attached screenshots). This would allow HAL to provide a wizard of available options when configuring them.
> The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list()
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-3801.
----------------------------
> Wrong Transaction behaviour for EJBs if JTS is enabled
> ------------------------------------------------------
>
> Key: WFLY-3801
> URL: https://issues.jboss.org/browse/WFLY-3801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Environment: standalone-full profile with JTS enabled
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Final
>
> Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log
>
>
> If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
> WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
> This is only the case if other resources are involved, i.e. a DB via JPA.
> If a simple bean is used (like ejb-remote quickstart) this warning is not shown.
> It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-3801:
----------------------------------
I am bulk closing old issues that were resolved with no fix version. From the history of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Wrong Transaction behaviour for EJBs if JTS is enabled
> ------------------------------------------------------
>
> Key: WFLY-3801
> URL: https://issues.jboss.org/browse/WFLY-3801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Environment: standalone-full profile with JTS enabled
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Final
>
> Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log
>
>
> If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
> WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
> This is only the case if other resources are involved, i.e. a DB via JPA.
> If a simple bean is used (like ejb-remote quickstart) this warning is not shown.
> It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-3801:
-----------------------------
Fix Version/s: 11.0.0.Final
> Wrong Transaction behaviour for EJBs if JTS is enabled
> ------------------------------------------------------
>
> Key: WFLY-3801
> URL: https://issues.jboss.org/browse/WFLY-3801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Environment: standalone-full profile with JTS enabled
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Final
>
> Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log
>
>
> If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
> WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
> This is only the case if other resources are involved, i.e. a DB via JPA.
> If a simple bean is used (like ejb-remote quickstart) this warning is not shown.
> It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-7317) Elytron ldap-key-store DMR XSD inconsistency
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7317?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-7317:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Elytron ldap-key-store DMR XSD inconsistency
> ---------------------------------------------
>
> Key: WFLY-7317
> URL: https://issues.jboss.org/browse/WFLY-7317
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Labels: user_experience
> Fix For: 11.0.0.Final
>
>
> * in XSD there are missing attributes {{key-attribute}} and {{key-type}}
> * in XSD {{value}} attribute of {{new-item-template}} is not a list type as in DMR
> * in DMR {{name}} in {{new-item-attributes}} is optional. In XSD it is marked as required. Should be required in DMR as well.
> * synchronize documenation of XSD and DMR. Documentation in XSD seems little bit detailed.
> * In {{certificate-type}} and {{certificate-attribute}} probably remove link to oracle java 8 documentation. I consider it usefull, but I see couple of maintaining issues. Link can change. Java 9 is comming and can have own enumaration. We also support IBM java. Just stating "For possible values see java documentation of CertificateFactory/CertPathEncodings" would be enough here
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-3809) JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3809?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-3809:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows
> --------------------------------------------------------------------
>
> Key: WFLY-3809
> URL: https://issues.jboss.org/browse/WFLY-3809
> Project: WildFly
> Issue Type: Bug
> Components: JDR
> Environment: All modes on Windows
> Reporter: Jesse Jaggars
> Assignee: Jesse Jaggars
> Fix For: 11.0.0.Final
>
>
> JDR replaces $JBOSS_HOME with the text `JBOSS_HOME` in the generated zipfile. On windows the path is improperly constructed. For example if JBOSS_HOME=/foo/bar/baz, when the file /foo/bar/baz/example.txt is copied into the JDR archive the path will be:
> JBOSS_HOMEz/example.txt
> It should be:
> JBOSS_HOME/example.txt
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-8186) CS tool, can't list --help without NPE occurence
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-8186?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-8186:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> CS tool, can't list --help without NPE occurence
> ------------------------------------------------
>
> Key: WFLY-8186
> URL: https://issues.jboss.org/browse/WFLY-8186
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Peter Skopek
> Priority: Critical
> Labels: credential-store
> Fix For: 11.0.0.Final
>
>
> {code}
> java -jar wildfly-elytron-tool.jar credential-store -h
> {code}
> or because of WFLY-8176
> {code}
> java -jar wildfly-elytron-tool.jar credential-store -h --salt 12345678 --iteration 230
> {code}
> leads to
> {code}
> usage: java -jar wildfly-elytron-tool.jar credential-store <sub-command>
> <options> -a <arg> | -e <arg> | -h | -r <arg> | -v [-c] [-f] [-i
> <arg>] [-l <arg>] [-p <arg>] [-s <arg>] [-t <arg>] [-u <arg>] [-x
> <arg>]
> Exception in thread "main" java.lang.NullPointerException
> at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
> at java.util.regex.Matcher.reset(Matcher.java:309)
> at java.util.regex.Matcher.<init>(Matcher.java:229)
> at java.util.regex.Pattern.matcher(Pattern.java:1093)
> at java.util.Formatter.parse(Formatter.java:2547)
> at java.util.Formatter.format(Formatter.java:2501)
> at java.io.PrintStream.format(PrintStream.java:970)
> at java.io.PrintStream.printf(PrintStream.java:871)
> at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:58)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-7067) show-resources operation of jaxrs subsystem is unable to read jax-rs end-point from subresources
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7067?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-7067:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> show-resources operation of jaxrs subsystem is unable to read jax-rs end-point from subresources
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-7067
> URL: https://issues.jboss.org/browse/WFLY-7067
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Lin Gao
> Assignee: Lin Gao
> Fix For: 11.0.0.Final
>
>
> Show-resources operation of jaxrs subsystem is unable to read jax-rs end-point from subresources.
> Example:
> {code:java}
> @Path("/root")
> public class Root {
> @Path("/method")
> public Sub rootMethod() {
> return new Sub();
> }
> }
> {code}
> {code:java}
> public class Sub {
> @GET
> @Path("submethod")
> public String returnValue() {
> return "555";
> }
> }
> {code}
> {noformat}
> [standalone@localhost:9990 /] /deployment=jaxrs-wf.war/subsystem=jaxrs:show-resources
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.ClassCastException: org.jboss.resteasy.core.ResourceLocatorInvoker cannot be cast to org.jboss.resteasy.core.ResourceMethodInvoker",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> 15:52:04,618 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 33) WFLYCTL0013: Operation ("show-resources") failed - address: ([
> ("deployment" => "jaxrs-wf.war"),
> ("subsystem" => "jaxrs")
> ]): java.lang.ClassCastException: org.jboss.resteasy.core.ResourceLocatorInvoker cannot be cast to org.jboss.resteasy.core.ResourceMethodInvoker
> at org.jboss.as.jaxrs.JaxrsDeploymentDefinition$ShowJaxrsResourcesHandler.handle(JaxrsDeploymentDefinition.java:107)
> at org.jboss.as.jaxrs.JaxrsDeploymentDefinition$ShowJaxrsResourcesHandler$1.execute(JaxrsDeploymentDefinition.java:163)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months