[JBoss JIRA] Created: (SECURITY-114) Move resources into standard maven location
by Paul Gier (JIRA)
Move resources into standard maven location
-------------------------------------------
Key: SECURITY-114
URL: http://jira.jboss.com/jira/browse/SECURITY-114
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX
Reporter: Paul Gier
Assigned To: Anil Saldhana
The current resources configuration has the files spread across a few directories.
{code}
<resources>
<resource>
<directory>src/main</directory>
<includes>
<include>**/*.xml</include>
</includes>
</resource>
<resource>
<directory>${basedir}</directory>
<includes>
<include>JBossORG-EULA.txt</include>
</includes>
</resource>
<resource>
<directory>src/resources</directory>
<includes>
<include>**/*.dtd</include>
<include>**/*.xsd</include>
</includes>
</resource>
<resource>
<directory>target/generated-sources/javacc</directory>
<includes>
<include>**/*.class</include>
</includes>
</resource>
</resources>
<testResources>
<testResource>
<directory>src/tests/resources/</directory>
</testResource>
<testResource>
<directory>src/main</directory>
</testResource>
</testResources>
{code}
All the resource files could be moved to the standard maven locations of src/main/resources, and src/test/resources. This way, the only configuration needed would be the appropriate includes.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBWEB-97) Cross-context request dispatching is not working for PHP files
by Thomas Heute (JIRA)
Cross-context request dispatching is not working for PHP files
--------------------------------------------------------------
Key: JBWEB-97
URL: http://jira.jboss.com/jira/browse/JBWEB-97
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss AS 4.2.2.GA
Reporter: Thomas Heute
Assigned To: Mladen Turk
I installed the php-examples.war from the documentation.
Now i'm trying to do a cross-context request dispatching from a servlet in context /foo to the resource /index.php of the context /php-examples.war
The PHP handler Servlet is lost and it ends up with: ERROR [ScriptEnvironment] Invalid script names
It looks like the Servlet is looking in the wrong context.
I'm attaching my test webapp which tried to include /php-examples/index.php
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBPORTAL-1466) customizable error page in the portlet that threw the exception
by William DeCoste (JIRA)
customizable error page in the portlet that threw the exception
---------------------------------------------------------------
Key: JBPORTAL-1466
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1466
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.CR2
Reporter: William DeCoste
Assigned To: Julien Viet
Feature request from Intuit
Feature:
For error handing, the portlet should be able to render a customizable error page in the portlet that threw the exception. This feature would be something similar to the error-page tag in web.xml.
Currently JBoss Portal provides a way to either hide the portlet that has errors or show it with the stack trace or show it with only the error message. But there is no way where the developers could customize the contents that appear in the window for the portlet that throws an exception.
We had opened case #00015844 about not being able to use web.xml error-page tag with JBoss portal applications. The provided solution about catching the specific exception in the render method does not work as it is not customizable & too tied up with the portlet class code. And as you might be aware about the WAP function - someone using the WAP application components will not be able to customize it according to their requirements.
We know that the portlet standard doesn't specify what to do, and we're just trying to have it behave as much like a regular web application in lieu of something being in the standard.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBAOP-515) Awful error report to syserr: use logger for this instead
by Carlos XXXXX (JIRA)
Awful error report to syserr: use logger for this instead
---------------------------------------------------------
Key: JBAOP-515
URL: http://jira.jboss.com/jira/browse/JBAOP-515
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR3
Reporter: Carlos XXXXX
Priority: Minor
When trying to introduce the same method twice, an error is correctly reported. But no matter which setting is having effect (verbose true/false, suppressTransformationErrors true/false), this error is printed directly to the console, ignoring the logging system. This should be in an ERROR level log entry, it's not a fatal error that aborts execution.
java.lang.RuntimeException: Mixin jbossaop.SirenMixin of pointcut file:/home/carlos/dev/java/eclipse/test-stuff/src/jbossaop/jboss-aop.xml3 is trying to apply an already existing methodsing for class jbossaop.Bean
at org.jboss.aop.instrument.Instrumentor.addMixin(Instrumentor.java:321)
at org.jboss.aop.instrument.Instrumentor.instrumentIntroductions(Instrumentor.java:386)
at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:725)
at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:120)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.instrumentClass(SuperClassesFirstWeavingStrategy.java:200)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.translate(SuperClassesFirstWeavingStrategy.java:70)
at org.jboss.aop.AspectManager.translate(AspectManager.java:934)
at org.jboss.aop.AspectManager.transform(AspectManager.java:880)
....
--
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
16 years, 11 months