[JBoss JIRA] Created: (JBAS-4265) JNDIView list fails to show java:comp envs
by Scott M Stark (JIRA)
JNDIView list fails to show java:comp envs
------------------------------------------
Key: JBAS-4265
URL: http://jira.jboss.com/jira/browse/JBAS-4265
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Naming
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
The JNDIView.list op is failing to show component java:comp env currently. We really need to drop the TCL based enc and make this a proper piece of the deployment metadata.
java:comp namespace of the ObjectMessageBean bean:
Failed on lookup, javax.naming.NameNotFoundException: comp not bound
javax.naming.NameNotFoundException: comp not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:628)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:590)
at org.jboss.naming.JNDIView.list(JNDIView.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258)
at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:86)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBAS-3595) Tomcat allows http access with transport guarantie CONFIDENTIAL
by Thomas Diesler (JIRA)
Tomcat allows http access with transport guarantie CONFIDENTIAL
---------------------------------------------------------------
Key: JBAS-3595
URL: http://jira.jboss.com/jira/browse/JBAS-3595
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossAS-5.0.0.Beta
The generated web.xml contains CONFIDENTIAL. Access via http:// should be denied.
This woks in Branch_4_0
/home/tdiesler/svn/jbossws/trunk/src/test
[tdiesler@tdvaio test]$ ant -Dtest=org.jboss.test.ws.samples.secureejb.SecureEJBTestCase one-test
one-test:
[junit] Running org.jboss.test.ws.samples.secureejb.SecureEJBTestCase
[junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 5.452 sec
[junit] Test org.jboss.test.ws.samples.secureejb.SecureEJBTestCase FAILED
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBAS-3509) org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
by Jaroslaw Kijanowski (JIRA)
org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
----------------------------------------------------------------------
Key: JBAS-3509
URL: http://jira.jboss.com/jira/browse/JBAS-3509
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta
Environment: win xp
Reporter: Jaroslaw Kijanowski
org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound because of missing xml files.
Resolve:
Copy following xml files to testsuite\src\resources\cache\META-INF
************
ejb-jar.xml:
************
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>
<!-- Session Beans -->
<session >
<description><![CDATA[]]></description>
<ejb-name>CacheObjectMeanTester</ejb-name>
<home>org.jboss.test.cache.bean.CacheObjectMeanTesterHome</home>
<remote>org.jboss.test.cache.bean.CacheObjectMeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.CacheObjectMeanTesterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCache MBean.]]></description>
<ejb-name>test/TreeCacheTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
<ejb-name>test/TreeCacheAopTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheAopTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheAopTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheAopTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[EJB proxy to the TreeCache MBean service.]]></description>
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheMBeanTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheMBeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheMBeanTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheAopMBeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<!--
To add session beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called session-beans.xml that contains
the <session></session> markup for those beans.
-->
<!-- Entity Beans -->
<!--
To add entity beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called entity-beans.xml that contains
the <entity></entity> markup for those beans.
-->
<!-- Message Driven Beans -->
<!--
To add message driven beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called message-driven-beans.xml that contains
the <message-driven></message-driven> markup for those beans.
-->
</enterprise-beans>
<!-- Relationships -->
<!-- Assembly Descriptor -->
<assembly-descriptor >
<!--
To add additional assembly descriptor info here, add a file to your
XDoclet merge directory called assembly-descriptor.xml that contains
the <assembly-descriptor></assembly-descriptor> markup.
-->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- transactions -->
<container-transaction >
<method >
<ejb-name>test/TreeCacheTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheAopTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<!-- finder transactions -->
</assembly-descriptor>
</ejb-jar>
************
************
jboss.xml
************
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
<jboss>
<enterprise-beans>
<!--
To add beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called jboss-beans.xml that contains
the <session></session>, <entity></entity> and <message-driven></message-driven>
markup for those beans.
-->
<session>
<ejb-name>CacheObjectMeanTester</ejb-name>
<jndi-name>test/CacheObjectMeanTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheTester</ejb-name>
<jndi-name>ejb/test/TreeCacheTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheAopTester</ejb-name>
<jndi-name>test/TreeCacheAopTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<jndi-name>ejb/test/TreeCacheMBeanTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<jndi-name>ejb/test/TreeCacheAopMBeanTester</jndi-name>
</session>
</enterprise-beans>
<resource-managers>
</resource-managers>
</jboss>
***************
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBREM-746) need to be able to tell ServerInvokerServlet to use the platform MBean server
by John Mazzitelli (JIRA)
need to be able to tell ServerInvokerServlet to use the platform MBean server
-----------------------------------------------------------------------------
Key: JBREM-746
URL: http://jira.jboss.com/jira/browse/JBREM-746
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.SP4
Reporter: John Mazzitelli
Assigned To: Ron Sigal
Right now, ServerInvokerServlet assumes the MBeanServer where it can find the server invoker is the JBoss MBeanServer.
See the comments in ServerInvokerServlet.getMBeanServer()
It would be nice to be able to tell it to not use the MBeanServer whose default domain is "jboss", but rather we should be able to tell it (via servlet init params) either:
a) the name of the MBeanServer's default domain (in case I want to use my own, not the jboss one)
or
b) a flag to indicate it should use the Java5 platform MBeanServer (java.lang.management.ManagementFactory.getPlatformMBeanServer())
Workaround is for customers to write their own subclass of ServerInvokerServlet, override the getMBeanServer method to find the appropriate one.
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBAS-4253) ServletContext().getRealPath("/") is returning null
by Scott M Stark (JIRA)
ServletContext().getRealPath("/") is returning null
---------------------------------------------------
Key: JBAS-4253
URL: http://jira.jboss.com/jira/browse/JBAS-4253
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Scott M Stark
Assigned To: Remy Maucherat
Fix For: JBossAS-5.0.0.Beta2
The following call:
String realPath = getServletContext().getRealPath("/");
is failing due to a null path being returned. I assume this is a vfs integration issue.
<testcase classname="org.jboss.test.web.test.WebIntegrationUnitTestCase" name="testRealPath" time="0.15">
−
<error message="Expected reply code:200, actual=500" type="java.io.IOException">
java.io.IOException: Expected reply code:200, actual=500
at org.jboss.test.util.web.HttpUtils.accessURL(HttpUtils.java:137)
at org.jboss.test.util.web.HttpUtils.accessURL(HttpUtils.java:108)
at org.jboss.test.util.web.HttpUtils.accessURL(HttpUtils.java:96)
at org.jboss.test.util.web.HttpUtils.accessURL(HttpUtils.java:82)
at org.jboss.test.web.test.WebIntegrationUnitTestCase.testRealPath(WebIntegrationUnitTestCase.java:67)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
</error>
</testcase>
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBFORUMS-245) implementation for multiple forums
by Luca Stancapiano (JIRA)
implementation for multiple forums
----------------------------------
Key: JBFORUMS-245
URL: http://jira.jboss.com/jira/browse/JBFORUMS-245
Project: JBoss Forums
Issue Type: Patch
Components: Forum Model Layer, Forum Test Suite
Affects Versions: 1.0.1 GA
Environment: eclipse 3.2.2 , jboss as 4.0.5_cp_04, jboss portal taken from http://anonsvn.jboss.org/repos/portal/trunk since 9 jun 2007, jboss forums taken from http://anonsvn.labs.jboss.com/labs/jbossforums/branches/forums101P26 since 23 jun 2007
Reporter: Luca Stancapiano
Assigned To: Ryszard Kozmik
Fix For: 1.0.1 GA
hi....I have a patch to use multiple forums into the portal.... updates are many because I added an argument in several method. The principal update is to add a jbp_forums_instances table that contains
the instance for the forum and a field jbp_id that represents the instance. You can to add a new forum directly by web adding a preference from portlet instances form of portal. The new forum is represented by a foruminstanceid preference. It is a number that identify a forum. If two instances of forum has the same foruminstanceid , then they are equals, while if those preferences are different , then the forums are different and they will get different categories, forums, topics ...etc etc. I describe my update in steps:
STEP 1: DATABASE AND HIBERNATE
1 - added a table called jbp_forums_instances managed through hibernate through interface ForumInstance and class ForumInstanceImpl as for the other tables in the forums
2 - added a field into jbp_forums_categories called jbp_forum_instance_id , that it tie in a one-to-many relation to jbp_forums_instances table and updated Category interface and CategoryImplClass
3 - updated src/resources/setup/setup.sql with the updates over mentioned
4 - updated src/resources/portal-forums-sar/conf/hibernate/setup.txt with the updates over mentioned
5 - updated src/resources/portal-forums-sar/conf/hibernate/hibernate.cfg.xml adding the creation of ForumInstance object into database
STEP 2 - PREFERENCES
1 - updated src/resources/portal-forums-war/WEB-INF/portlet.xml adding foruminstanceid preference to configure through web into portlet instances of portal
STEP 3 - METHODS
1 - updated findTopics, findTopicsHot, ,findTopicsByLatestPosts , findTopicsHottest, findTopicsMostViewed, findPosts, ,findCategories , findCategoriesFetchForums, findForums, createCategory, findLastPostsOfForums, findForumWatchByUser, findForumWatchedByUser, findTopicWatchedByUser, findTopicWatches and findForumWatches methods into src/main/org/jboss/portlet/forums/ForumsModule.java and src/main/org/jboss/portlet/forums/impl/ForumsModuleImpl.java to use forumInstanceId argument
2 - created findForumInstanceById, createForumInstance, removeForumInstance into src/main/org/jboss/portlet/forums/ForumsModule.java and src/main/org/jboss/portlet/forums/impl/ForumsModuleImpl.java to manage ForumInstance objects
STEP 4 - TEST
1 - updated src/main/org/jboss/portlet/test/forums/CategoryModelTestCase.java to use new updates for methods
2 - updated src/main/org/jboss/portlet/test/forums/ForumModelTestCase.java to use new updates for methods
3 - updated src/main/org/jboss/portlet/test/forums/TopicModelTestCase.java to use new updates for methods
4 - updated src/main/org/jboss/portlet/test/forums/PostModelTestCase.java to use new updates for methods
SETP 5 - ACTIONS
1- added getPreferences method into src/main/org/jboss/portlet/forums/ui/FormUtil.java. This method is similar to getPreferences of PortalUtil class but it let to get the preferences also for an anonymous user:
public static String getPreference(String preferenceKey)
{
String preference = null;
Object o = FacesContext.getCurrentInstance().getExternalContext()
.getRequest();
if (o instanceof PortletRequest)
{
PortletRequest request = (PortletRequest) o;
PortletPreferences pp = request.getPreferences();
preference = pp.getValue(preferenceKey, "");
}
return preference;
}
2 - updated all actions and views that need to get foruminstanceid to query and insert forum objects.
Updated actions are:
addCategory, moveCategoryDown and moveCategoryUp methods of src/main/org/jboss/portlet/forums/ui/action/AdminController.java
Updated views are:
getCategories and getForums methods of src/main/org/jboss/portlet/forums/ui/view/ViewAdminPanel.java
execute method of src/main/org/jboss/portlet/forums/ui/view/ViewCategory.java
getCategories method of src/main/org/jboss/portlet/forums/ui/view/ViewJumpbox.java
getWatchedTopics and getTopicWatches methods of src/main/org/jboss/portlet/forums/ui/view/ViewMyForumsAllSubscrived.java
getForumsLastPosts, execute and getWatchedForums methods of src/main/org/jboss/portlet/forums/ui/view/ViewMyForumsEditAllForums.java
getWatchedTopics, getForumsLastPosts and getWatchedForums methods of src/main/org/jboss/portlet/forums/ui/view/ViewMyForumsMain.java
loadDefaultTopics method of src/main/org/jboss/portlet/forums/ui/view/ViewSummary.java
3 - all methods use a FORUM_INSTANCE_ID constant declared into src/main/org/jboss/portlet/forums/ui/Constants.java to call foruminstanceid preferemce
--
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
18 years, 7 months