[JBoss JIRA] (WFLY-7453) Resource description should not contain javadoc style links
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7453?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-7453:
--------------------------------------
Component/s: Domain Management
(was: Server)
Assignee: Ken Wills (was: Jason Greene)
Please use component "Domain Management" for management model issues not specific to a subsystem. Yes, it's a very intuitive component name. :)
> Resource description should not contain javadoc style links
> -----------------------------------------------------------
>
> Key: WFLY-7453
> URL: https://issues.jboss.org/browse/WFLY-7453
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Švehla
> Assignee: Ken Wills
> Priority: Minor
> Labels: user_experience
>
> Description of the attribute {{date-format}} in
> {code}
> /core-service=management/access=audit/json-formatter=json-formatter
> {code}
> has following description:
> {panel}
> The date format to use as understood by \{@link java.text.SimpleDateFormat}. Will be ignored if include-date=\"false\".
> {panel}
> The description string shouldn't contain javadoc style @link
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7523) Add hibernate-spatial to hibernate module
by Dennis Gesker (JIRA)
Dennis Gesker created WFLY-7523:
-----------------------------------
Summary: Add hibernate-spatial to hibernate module
Key: WFLY-7523
URL: https://issues.jboss.org/browse/WFLY-7523
Project: WildFly
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 10.1.0.Final
Environment: Linux / OpenJDK 8 / Wildfly 10.1.0.Final
Reporter: Dennis Gesker
Assignee: Scott Marlow
Fix For: 10.2.0.Final
The use of GIS extensions is becoming more prevalent. It would be very helpful if org.hibernate:hibernate-spatial was added to the the hibernate module.
hibernate-spatial SEEMS to also require the following jars/packages :
org.hibernate:hibernate-spatial
org.geolatte:geolatte-geom
com.vividsolutions:jts-parent
So, jars would need to be added to modules/system/layers/base/org/hibernate/main and associated <resource-root> tags in module.xml
I believe <dependencies> would also require <module name="org.slf4j"/> entry
Note: The "Create Issue" page defaulted this item to "Major" but it is labeled as (FOR USE BY COMMITTERS ONLY) so I did not change it. I would have chosen "Minor" as this would be really useful but of course doesn't break or stop anything.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-497) Lazy scope creation
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-497?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse resolved ELY-497.
----------------------------------
Fix Version/s: 1.1.0.Beta14
(was: 1.1.0.CR1)
Assignee: Darran Lofthouse
Resolution: Out of Date
Scopes have been updated to support lazy creation.
> Lazy scope creation
> -------------------
>
> Key: ELY-497
> URL: https://issues.jboss.org/browse/ELY-497
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.1.0.Beta14
>
>
> It is not confirmed that we will do this but if we want to support lazy creation of scoped e.g. session scoped then we need to do it now or adding later may become a compatibility problem.
> We could add methods to check if one exists and a method to create it - or we could wait until the firs attachment is added - or other options.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-344) Review how clients use ModifiableRealmIdentity / ModifiableRealm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-344?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-344:
---------------------------------
Fix Version/s: 2.0.0.Alpha1
(was: 1.1.0.Beta15)
> Review how clients use ModifiableRealmIdentity / ModifiableRealm
> ----------------------------------------------------------------
>
> Key: ELY-344
> URL: https://issues.jboss.org/browse/ELY-344
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Realms
> Reporter: Darran Lofthouse
> Fix For: 2.0.0.Alpha1
>
>
> This may be something we address in the subsystem but just raising here so we don't forget.
> Once we have a working set up with a realm which can be modified it seems unreasonable to expect the administrator to know exactly which credential types and names to use.
> This may need to be a few milestones away once we have the bulk integrated so the relationships are clear.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months