[JBoss JIRA] Created: (SECURITY-25) Create subprojects in security for spi, jbosssx and optional
by Anil Saldhana (JIRA)
Create subprojects in security for spi, jbosssx and optional
------------------------------------------------------------
Key: SECURITY-25
URL: http://jira.jboss.com/jira/browse/SECURITY-25
Project: JBoss Security
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX, Repository, SPI
Affects Versions: 2.0
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0
Currently the security project has the Security SPI as well as the JBossSX implementation in the same workspace. It is mavenized with no current capability to publish the archives into the maven repository.
The "Common" project has sub projects. Along those lines, there is a need to create sub projects.
This will enable us to publish artifacts to maven repository as well as make the dependencies clearer/manageable.
--
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
19 years, 3 months
[JBoss JIRA] Created: (JBREM-664) Fix misleading InvalidConfigurationException
by Scott M Stark (JIRA)
Fix misleading InvalidConfigurationException
--------------------------------------------
Key: JBREM-664
URL: http://jira.jboss.com/jira/browse/JBREM-664
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.2.0.Alpha4
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.2.0.Beta1 (Bluto)
This error thrown when an invocation handler is not found:
if (handler == null)
{
throw new InvalidConfigurationException("Can not handle invocation request because there are no " +
"ServerInvocationHandlers registered. Please add via xml configuration " +
"or via the Connector's addInvocationHandler() method.");
}
should include requested subsystem as another circumstance in which this error occurs is when the requested subsystem handler has not been added.
--
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
19 years, 3 months
[JBoss JIRA] Commented: (JBAS-3358) Work directory for the web app shouldn't be deleted on Context Destroy
by Javid Jamae (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3358?page=comments#action_12350503 ]
Javid Jamae commented on JBAS-3358:
-----------------------------------
This guy has a work around:
http://www.ethelred.org/articles/2006/10/18/persisting-http-sessions-over...
He says: "So my final workaround was to add a context.xml to each individual web app - it goes in the WEB-INF directory - to set the Manager pathname to one including that web app's name. I also used a relative path of ../../.. to make the session files be written outside of the working directories that would be deleted, but avoid using a non-portable path.
This seemed to do the trick. Phew! (As an aside, I haven't actually written a context.xml for each web app - they are dynamically created by our build script)."
> Work directory for the web app shouldn't be deleted on Context Destroy
> ----------------------------------------------------------------------
>
> Key: JBAS-3358
> URL: http://jira.jboss.com/jira/browse/JBAS-3358
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Javid Jamae
> Assigned To: Anil Saldhana
> Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta1
>
>
> I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down.
> Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted).
--
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
19 years, 3 months