[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work
by George Trudeau (JIRA)
[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ]
George Trudeau edited comment on WFLY-10616 at 6/29/18 2:34 PM:
----------------------------------------------------------------
Thank you for clearing this out.
Changing the {{ContextResolver<ObjectMapper>}} to a {{ContextResolver<Jsonb>}} works as expected.
was (Author: george.trudeau):
Thank you for clearing this out, I will look into this.
> ContextResolver doesn't work
> ----------------------------
>
> Key: WFLY-10616
> URL: https://issues.jboss.org/browse/WFLY-10616
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 13.0.0.Final
> Reporter: George Trudeau
> Assignee: R Searls
> Fix For: 14.0.0.CR1
>
> Attachments: test.war
>
>
> I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
> {code:java}
> @Provider
> public class DateResolver implements ContextResolver<ObjectMapper>
> {
> private final ObjectMapper mapper;
> public DateResolver()
> {
> mapper = new ObjectMapper();
> mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
> mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
> }
> @Override
> public ObjectMapper getContext(Class<?> type) { return mapper; }
> }
> {code}
> The {{getContext}} method isn't called on 13.0.0.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work
by George Trudeau (JIRA)
[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ]
George Trudeau commented on WFLY-10616:
---------------------------------------
Thank you for clearing this out, I will look into this.
> ContextResolver doesn't work
> ----------------------------
>
> Key: WFLY-10616
> URL: https://issues.jboss.org/browse/WFLY-10616
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 13.0.0.Final
> Reporter: George Trudeau
> Assignee: R Searls
> Fix For: 14.0.0.CR1
>
> Attachments: test.war
>
>
> I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
> {code:java}
> @Provider
> public class DateResolver implements ContextResolver<ObjectMapper>
> {
> private final ObjectMapper mapper;
> public DateResolver()
> {
> mapper = new ObjectMapper();
> mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
> mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
> }
> @Override
> public ObjectMapper getContext(Class<?> type) { return mapper; }
> }
> {code}
> The {{getContext}} method isn't called on 13.0.0.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-10616:
---------------------------------
There was a code change between wfly-12 and wfly-13 in order to be compliant
with the jax-rs 2.1 specification. *This is not a bug*. Resteasy provides
a means to designate use of Jackson in liu of JSON-P.
Here is the documentation provided in the Resteasy's doc, chapter, "JAX-RS 2.1 Additions".
{code:java}
RESTEasy supports both JSON-B and JSON-P. In accordance with the specification,
entity providers for JSON-B take precedence over those for JSON-P for all types
except JsonValue and its sub-types.
The support for JSON-B is provided by the JsonBindingProvider from resteasy-json-binding-provider module.
To satisfy JAX-RS 2.1 requirements, JsonBindingProvider takes precedence over the other providers for dealing with JSON payloads,
in particular the Jackson one. The JSON outputs (for the same input) from Jackson and JSON-B reference implementation can be slightly
different. As a consequence, in order to allow retaining backward compatibility, RESTEasy offers a resteasy.preferJacksonOverJsonB context property that can be set to true to disable JsonBindingProvider for the current deloyment.
WildFly 14 supports specifying the default value for the resteasy.preferJacksonOverJsonB context property by setting a system property with the same name. Moreover, if no value is set for the context and system properties, it scans JAX-RS deployments
for Jackson annotations and sets the property to true if any of those annotations is found.
{code}
I used the following cmd to set the flag
{code:java}
./bin/standalone.sh -Dresteasy.preferJacksonOverJsonB=true
{code}
Alternatively you can provide a web.xml file with the flag.
{code:java}
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<context-param>
<param-name>resteasy.preferJacksonOverJsonB</param-name>
<param-value>true</param-value>
</context-param>
</web-app>
{code}
> ContextResolver doesn't work
> ----------------------------
>
> Key: WFLY-10616
> URL: https://issues.jboss.org/browse/WFLY-10616
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 13.0.0.Final
> Reporter: George Trudeau
> Assignee: R Searls
> Fix For: 14.0.0.CR1
>
> Attachments: test.war
>
>
> I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
> {code:java}
> @Provider
> public class DateResolver implements ContextResolver<ObjectMapper>
> {
> private final ObjectMapper mapper;
> public DateResolver()
> {
> mapper = new ObjectMapper();
> mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
> mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
> }
> @Override
> public ObjectMapper getContext(Class<?> type) { return mapper; }
> }
> {code}
> The {{getContext}} method isn't called on 13.0.0.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work
by George Trudeau (JIRA)
[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ]
George Trudeau updated WFLY-10616:
----------------------------------
Description:
I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
{code:java}
@Provider
public class DateResolver implements ContextResolver<ObjectMapper>
{
private final ObjectMapper mapper;
public DateResolver()
{
mapper = new ObjectMapper();
mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
}
@Override
public ObjectMapper getContext(Class<?> type) { return mapper; }
}
{code}
The {{getContext}} method isn't called on 13.0.0.Final.
was:
I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
{code:java}
@Provider
public class DateResolver implements ContextResolver<ObjectMapper>
{
private final ObjectMapper mapper;
public DateResolver()
{
mapper = new ObjectMapper();
mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZ"));
mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
}
@Override
public ObjectMapper getContext(Class<?> type) { return mapper; }
}
{code}
The {{getContext}} method isn't called on 13.0.0.Final.
> ContextResolver doesn't work
> ----------------------------
>
> Key: WFLY-10616
> URL: https://issues.jboss.org/browse/WFLY-10616
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 13.0.0.Final
> Reporter: George Trudeau
> Assignee: R Searls
> Fix For: 14.0.0.CR1
>
> Attachments: test.war
>
>
> I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
> {code:java}
> @Provider
> public class DateResolver implements ContextResolver<ObjectMapper>
> {
> private final ObjectMapper mapper;
> public DateResolver()
> {
> mapper = new ObjectMapper();
> mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
> mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
> }
> @Override
> public ObjectMapper getContext(Class<?> type) { return mapper; }
> }
> {code}
> The {{getContext}} method isn't called on 13.0.0.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (DROOLS-2654) [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2654?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2654:
-------------------------------------
[~manstis] Thanks for the additional information. I asked about the cell type because I think if you present/focus on the inline text input field by default, then there should be some hint text (or etc) that helps the user to understand which type of cell they are in and what they're naming - rather than just an empty input box. Which I guess circles back to 2653.
> [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2654
> URL: https://issues.jboss.org/browse/DROOLS-2654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
> [~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
> h3. Manual Acceptance test
> For each column/row agreed in comments that should support this feature:
> - Append row/column, fill name, save reopen, check value stored
> - Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
> - Try undo/redo after appending row/column
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10652) Mdb Clustered Singleton Delivery is not working
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/WFLY-10652?page=com.atlassian.jira.plugin... ]
Flavia Rainone commented on WFLY-10652:
---------------------------------------
[~pferraro] Thanks a lot! If you need any assistance with this, let me know!
> Mdb Clustered Singleton Delivery is not working
> ------------------------------------------------
>
> Key: WFLY-10652
> URL: https://issues.jboss.org/browse/WFLY-10652
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Paul Ferraro
> Fix For: 14.0.0.CR1
>
>
> When trying to deploy an application with clustered singleton MDB delivery, we see this error:
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.ejb3.clustered.singleton"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"messaging-clustering-singleton.war\".clustered.singleton.dependency is missing [org.wildfly.ejb3.clustered.singleton]"]}}}
> The clustered singleton service is not being installed with the expected name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10652) Mdb Clustered Singleton Delivery is not working
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10652?page=com.atlassian.jira.plugin... ]
Paul Ferraro edited comment on WFLY-10652 at 6/29/18 11:47 AM:
---------------------------------------------------------------
[~flavia.rainone] I've reproduce the issue using the quickstart. I'll also take ownership of this issue, since it seems I broke it...
was (Author: pferraro):
[~flavia.rainone] I'll also take ownership of this issue, since it seems I broke it...
> Mdb Clustered Singleton Delivery is not working
> ------------------------------------------------
>
> Key: WFLY-10652
> URL: https://issues.jboss.org/browse/WFLY-10652
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Paul Ferraro
> Fix For: 14.0.0.CR1
>
>
> When trying to deploy an application with clustered singleton MDB delivery, we see this error:
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.ejb3.clustered.singleton"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"messaging-clustering-singleton.war\".clustered.singleton.dependency is missing [org.wildfly.ejb3.clustered.singleton]"]}}}
> The clustered singleton service is not being installed with the expected name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10652) Mdb Clustered Singleton Delivery is not working
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10652?page=com.atlassian.jira.plugin... ]
Paul Ferraro reassigned WFLY-10652:
-----------------------------------
Assignee: Paul Ferraro (was: Flavia Rainone)
> Mdb Clustered Singleton Delivery is not working
> ------------------------------------------------
>
> Key: WFLY-10652
> URL: https://issues.jboss.org/browse/WFLY-10652
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Paul Ferraro
> Fix For: 14.0.0.CR1
>
>
> When trying to deploy an application with clustered singleton MDB delivery, we see this error:
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.ejb3.clustered.singleton"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"messaging-clustering-singleton.war\".clustered.singleton.dependency is missing [org.wildfly.ejb3.clustered.singleton]"]}}}
> The clustered singleton service is not being installed with the expected name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (WFLY-10652) Mdb Clustered Singleton Delivery is not working
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10652?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-10652:
-------------------------------------
[~flavia.rainone] I'll also take ownership of this issue, since it seems I broke it...
> Mdb Clustered Singleton Delivery is not working
> ------------------------------------------------
>
> Key: WFLY-10652
> URL: https://issues.jboss.org/browse/WFLY-10652
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Paul Ferraro
> Fix For: 14.0.0.CR1
>
>
> When trying to deploy an application with clustered singleton MDB delivery, we see this error:
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.ejb3.clustered.singleton"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"messaging-clustering-singleton.war\".clustered.singleton.dependency is missing [org.wildfly.ejb3.clustered.singleton]"]}}}
> The clustered singleton service is not being installed with the expected name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months