[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle
by Owen Taylor (JIRA)
Way to set JNDI properties for twiddle
--------------------------------------
Key: JBAS-3637
URL: http://jira.jboss.com/jira/browse/JBAS-3637
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Owen Taylor
Priority: Minor
It is frequently useful to be able to set JDNI properties when running twiddle - for example,
you might want to set jnp.disableDiscovery when checking the status of a particular server
that might not be running.
Right now, this is difficult to do. You can export a JBOSS_CLASSPATH
which contains a jndi.properties file before running twiddle.sh, but then you have to
include all the standard jars in it, which is quite annoying.
A pssible fixes would be one of:
A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default
construction (also useful for getting a log4j.properties that doesn't drop twiddle.log
in the cwd, perhaps)
B) A command line option for specifying a particular properties file to load and pass
to 'new InitialContext()' (slightly more convenient than A)
C) A command line option to define particular properties:
twiddle.sh -jnpProperty=jnp.disableDiscovery=true
(Or some better syntax)
The twiddle code actually does:
Properties props = new Properties(System.getProperties());
props.put(Context.PROVIDER_URL, serverURL);
ctx = new InitialContext(props);
In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true
would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take
effect, and system properties won't be looked at in the other code path either.
--
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, 2 months
[JBoss JIRA] Created: (JBPORTAL-1738) can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
by David Schlechtweg (JIRA)
can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
-------------------------------------------------------------------------------------------
Key: JBPORTAL-1738
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1738
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Portlet
Affects Versions: 2.6.2 Final
Reporter: David Schlechtweg
Assigned To: Julien Viet
Hi,
i get a IllegalAccessException when i use a jsp tag in freemarker:
<#assign portlet=JspTaglibs["http://java.sun.com/portlet"]>
<#import "/spring.ftl" as spring />
<@portlet.actionURL var="postURL">
<@portlet.param name="action" value="newQuery" />
</(a)portlet.actionURL>
I use freemarker 2.3.10 in jboss-portal-2.6.2.GA
java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public"
The problematic instruction:
----------
==> user-directive portlet.actionURL [on line 3, column 1 in template/search/simple/view.ftl]
----------
Java backtrace for programmers:
----------
freemarker.template.TemplateModelException: java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public"
at freemarker.ext.jsp.TagTransformModel.getWriter(TagTransformModel.java:177)
at freemarker.core.Environment.visit(Environment.java:220)
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:116)
at freemarker.core.Environment.visit(Environment.java:196)
at freemarker.core.MixedContent.accept(MixedContent.java:92)
at freemarker.core.Environment.visit(Environment.java:196)
at freemarker.core.Environment.process(Environment.java:176)
at freemarker.template.Template.process(Template.java:232)
at org.springframework.web.servlet.view.freemarker.FreeMarkerView.processTemplate(FreeMarkerView.java:344)
any ideas?
My hunch is that the class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag is not public, and you're trying to invoke a method on it that though itself is public, it is not declared in any public superclass of GenerateURLTag, or public interface that GenerateURLTag implements.
--
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, 2 months
[JBoss JIRA] Created: (JBMICROCONT-152) Dependency names need to be validated earlier
by Scott M Stark (JIRA)
Dependency names need to be validated earlier
---------------------------------------------
Key: JBMICROCONT-152
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-152
Project: JBoss MicroContainer
Issue Type: Bug
Components: Dependency
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossMC_2_0_0 Beta3
I'm seeing an error like the following testing profileservice attachments overrides:
Caused by: java.lang.IllegalArgumentException: Null name
at org.jboss.dependency.plugins.AbstractController.getContext(AbstractController.java:129)
at org.jboss.kernel.plugins.dependency.AbstractKernelController.getContext(AbstractKernelController.java:101)
at org.jboss.dependency.plugins.AbstractDependencyItem.resolve(AbstractDependencyItem.java:117)
at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:128)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:595)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:531)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
at org.jboss.system.ServiceController.doInstall(ServiceController.java:638)
at org.jboss.system.ServiceController.install(ServiceController.java:271)
This error regarding the invalid dependency item name not showing up until there is an attempt to resolve it makes it impossible to debug the problem as there is no context in the dependency to understand why its null.
--
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, 2 months