[JBoss JIRA] (AS7-4371) Allow authentication username to be specified on remote domain controller definition
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4371:
-------------------------------------
Summary: Allow authentication username to be specified on remote domain controller definition
Key: AS7-4371
URL: https://issues.jboss.org/browse/AS7-4371
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 7.1.2.Final
At the moment the slave domain controller authenticates against the master domain controller using the name in the host element in the host.xml, as this name is used to uniquely identify the host controller it needs to be unique - this means a user account needs to be created for each host controller.
This task is to additionally allow a user name to be specified on the <remote /> element defining the connection to the remote domain controller - in this case the name specified on the remote element will override the name on the host element - if this name is not specified the existing behaviour will remain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBRULES-3347) ResourceChangeScanner trying to scan rule file when instead the change set contains a package only
by Michael Schnitzler (JIRA)
Michael Schnitzler created JBRULES-3347:
-------------------------------------------
Summary: ResourceChangeScanner trying to scan rule file when instead the change set contains a package only
Key: JBRULES-3347
URL: https://issues.jboss.org/browse/JBRULES-3347
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.3.0.Final
Reporter: Michael Schnitzler
Assignee: Mark Proctor
1.) Create a KnowledgeBase using a rule file (DRL) on the classpath. The rule file has to contain a Drools function.
2.) Serialize the the KnowledgeBase to the file system.
3.) Create a changeset definition that adds the serialized package only.
4.) Create a client that creates a KnowledgeAgent and apply the changeset. The class path should not contain the original rule files.
5.) Start the ResourceChangeScanner
This will lead to a NPE in the ResourceChangeScannerImpl:
Exception in thread "Thread-0" java.lang.NullPointerException
at org.drools.io.impl.ClassPathResource.getURL(ClassPathResource.java:124)
at org.drools.io.impl.ClassPathResource.getLastModified(ClassPathResource.java:139)
at org.drools.io.impl.ResourceChangeScannerImpl.scan(ResourceChangeScannerImpl.java:166)
at org.drools.io.impl.ResourceChangeScannerImpl$ProcessChangeSet.run(ResourceChangeScannerImpl.java:311)
at java.lang.Thread.run(Unknown Source)
The reason for this seems to be:
In private method KnowledgeAgentImpl.buildResourceMapping the function's resource (the DRL file) is retrieved and added to the registered resources . But the client is not distributed with the rule file on its classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (AS7-4334) RESTeasy: Cannot configure Jackson ObjectMapper via ContextResolver nor Application.getSingletons()
by Hendy Irawan (JIRA)
Hendy Irawan created AS7-4334:
---------------------------------
Summary: RESTeasy: Cannot configure Jackson ObjectMapper via ContextResolver nor Application.getSingletons()
Key: AS7-4334
URL: https://issues.jboss.org/browse/AS7-4334
Project: Application Server 7
Issue Type: Bug
Components: REST
Affects Versions: 7.1.1.Final
Environment: JBoss AS 7.1.1
Reporter: Hendy Irawan
Assignee: Stuart Douglas
This doesn't work:
{code}
@Provider @Produces(MediaType.APPLICATION_JSON)
public class JacksonContextResolver implements ContextResolver<ObjectMapper> {
private transient Logger log = LoggerFactory.getLogger(JacksonContextResolver.class);
private ObjectMapper objectMapper;
public JacksonContextResolver() throws JsonGenerationException, JsonMappingException, IOException {
log.info("Using my own Jackson ObjectMapper");
objectMapper = new ObjectMapper();
objectMapper.configure(Feature.INDENT_OUTPUT, true);
objectMapper.configure(Feature.WRITE_DATES_AS_TIMESTAMPS, false);
objectMapper.configure(Feature.WRITE_DATE_KEYS_AS_TIMESTAMPS, false);
log.info("Test date: {}", objectMapper.writeValueAsString(new DateTime()));
log.info("Test pretty output: {}", objectMapper
.writeValueAsString(new Article("Launching AksiMata",
"AksiMata : Ada apa di sana?",
"Webapp yang keren dan oke punya.", "Hendy Irawan")));
}
@Override
public ObjectMapper getContext(Class<?> type) {
return objectMapper;
}
}
{code}
The log correctly tests the custom ObjectMapper works fine, however when returning the output, seems like it's still using the "default" ObjectMapper.
This also doesn't work:
{code}
@Override
public Set<Object> getSingletons() {
Set<Object> singletons = new HashSet<Object>(super.getSingletons());
ObjectMapper objectMapper = new ObjectMapper();
objectMapper.configure(Feature.INDENT_OUTPUT, true);
objectMapper.configure(Feature.WRITE_DATES_AS_TIMESTAMPS, false);
objectMapper.configure(Feature.WRITE_DATE_KEYS_AS_TIMESTAMPS, false);
singletons.add(objectMapper);
return singletons;
}
{code}
Sample project to reproduce the issue is at:
https://github.com/soluvas/ear-sample/tarball/resteasy-jackson-bug
Bug is almost similar to #AS7-1408.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months