[JBoss JIRA] Created: (JBWEB-72) html page and jsp are not display with in a Context defined in server.xml.
by Jean-Frederic Clere (JIRA)
html page and jsp are not display with in a Context defined in server.xml.
--------------------------------------------------------------------------
Key: JBWEB-72
URL: http://jira.jboss.com/jira/browse/JBWEB-72
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBoss Web Server 1.0.1 GA
Environment: any
Reporter: Jean-Frederic Clere
Assigned To: Jean-Frederic Clere
Priority: Minor
When using a Context definition in server.xml like:
<Context path="/test" docBase="/home/jfclere/TMP/MYAPP" />
The jsp and html pages of /home/jfclere/TMP/MYAPP are not displayed (404 is returned).
That is because the conf/web.xml is not used to set the defaults when the <Context/> is processed.
DefaultWebXml is set in TomcatDeployer and that is after the <Context/> needs it. The default value is used but it is set to "web.xml".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
by Dan Seaver (JIRA)
CommandFactory newStartProcess doesn't set parameters
-----------------------------------------------------
Key: JBRULES-2934
URL: https://issues.jboss.org/browse/JBRULES-2934
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Reporter: Dan Seaver
Assignee: Mark Proctor
Should be able to set parameter values when starting a process. Current code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
return getCommandFactoryProvider().newStartProcess( processId );
}
proposed code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
StartProcessCommand cmd = new StartProcessCommand(processId);
cmd.setParameters(parameters);
return cmd;
}
Also, I think this issue would go under the droolsjbpm-knowledge component if the JIRA component list were updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3067) unable to jndi-name attribute for default cache container
by Heiko Braun (Created) (JIRA)
unable to jndi-name attribute for default cache container
---------------------------------------------------------
Key: AS7-3067
URL: https://issues.jboss.org/browse/AS7-3067
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Heiko Braun
Assignee: Stan Silvert
{noformat}
[INFO] operation=
[INFO] {
[INFO] "operation" => "composite",
[INFO] "address" => [],
[INFO] "steps" => [{
[INFO] "address" => [
[INFO] ("subsystem" => "infinispan"),
[INFO] ("cache-container" => "hibernate")
[INFO] ],
[INFO] "operation" => "write-attribute",
[INFO] "name" => "jndi-name",
[INFO] "value" => "java:/hibernateCache"
[INFO] }]
[INFO] }
[ERROR] 2011-12-16 11:38:43,017 [ERROR] On Fri Dec 16 11:38:42 CET 2011, MessageCenter received {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute jndi-name"}}
{noformat}
--
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
14 years, 2 months
[JBoss JIRA] Created: (JBRULES-2533) Update Eclipse Compiler dependency
by Fabian Lange (JIRA)
Update Eclipse Compiler dependency
----------------------------------
Key: JBRULES-2533
URL: https://jira.jboss.org/browse/JBRULES-2533
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.0.M2
Reporter: Fabian Lange
Assignee: Mark Proctor
drools-compiler pom includes a reference to eclipse JDT. in 5.0.1 this was a 4 MB core_whatever.jar
Because I wanted to improve compiler performance I tried out a never eclipse compiler package. Finding it was not very easy, because eclipse seems to change group and artifact ids every day.
I found a module which only contains the compiler part from eclipse 3.5.1, which works in all my tests ok.
Another nice benefit was that the size of my war shrunk by 3 Megabytes, as this module is only 1.7 megs.
It even helped for performance of compilation process by the way. Not that this is a main bottleneck, but we have files that take seconds to compile.
My tests on my windows box with java 6 gave 5-10% improvement using the 3.5.1 jdt compiler.
Here the part for the pom:
{code}
<dependency>
<groupId>org.eclipse.jdt.core.compiler</groupId>
<artifactId>ecj</artifactId>
<version>3.5.1</version>
</dependency>
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3227) When a Stateless Session Bean is used as a REST-Resource, calling getUserPrincipal() on an injected SecurityContext sometimes returns null
by Philipp Berger (Created) (JIRA)
When a Stateless Session Bean is used as a REST-Resource, calling getUserPrincipal() on an injected SecurityContext sometimes returns null
------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3227
URL: https://issues.jboss.org/browse/AS7-3227
Project: Application Server 7
Issue Type: Bug
Components: EJB, REST
Affects Versions: 7.1.0.CR1b, 7.0.2.Final
Environment: Ubuntu Linux 11.04 64-bit, jdks 1.7.0_02 and 1.6.0_26
Reporter: Philipp Berger
Assignee: jaikiran pai
Considered the following stateless session bean which is propagated as a REST-Webservice:
{code:title=UserPrincipalRESTService.java|borderStyle=solid}
@Path("/test")
public interface UserPrincipalRESTService {
@GET
@Produces(MediaType.TEXT_PLAIN)
String helloUser();
}
{code}
{code:title=UserPrincipalRESTServiceImpl.java|borderStyle=solid}
@Stateless
@Local
public class UserPrincipalRESTServiceImpl implements UserPrincipalRESTService {
@Context
private SecurityContext securityContext;
public String helloUser() {
final String userName = securityContext.getUserPrincipal().getName();
return "Hello " + userName+"!";
}
}
{code}
After a certain (sometimes very large) amount of GET Requests on the Resource, the injected SecurityContext's user principal suddenly is null and a NPE is thrown. Once this happened, every second call to the resource will throw a NPE until the application server is restarted.
--
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
14 years, 2 months