[JBoss JIRA] Created: (EJBTHREE-760) @WebServiceRef not bound to java:comp/env
by Thomas Diesler (JIRA)
@WebServiceRef not bound to java:comp/env
-----------------------------------------
Key: EJBTHREE-760
URL: http://jira.jboss.com/jira/browse/EJBTHREE-760
Project: EJB 3.0
Issue Type: Bug
Reporter: Thomas Diesler
Assigned To: Carlo de Wolf
package org.jboss.test.ws.jaxws.webserviceref;
@WebServiceRef(name = "service1", value = TestEndpointService.class, wsdlLocation = "META-INF/wsdl/TestEndpoint.wsdl")
@WebServiceRefs( {
@WebServiceRef(name = "service2", value = TestEndpointService.class, wsdlLocation = "META-INF/wsdl/TestEndpoint.wsdl"),
@WebServiceRef(name = "port1", value = TestEndpointService.class, type = TestEndpoint.class, wsdlLocation = "META-INF/wsdl/TestEndpoint.wsdl") })
public class ApplicationClient
When the client is deployed, I see the first reference beeing bound to jbossws-client/env/service1
However,
ports.add(((TestEndpointService)encCtx.lookup("java:comp/env/service1")).getTestEndpointPort());
fails with javax.naming.NameNotFoundException: service1 not bound
To reproduce run this against jbossas/branches/JEE5_TCK
/home/tdiesler/svn/jbossws/trunk/src/test
[tdiesler@tddell test]$ ant -Dtest=jaxws/webserviceref test
--
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, 11 months
[JBoss JIRA] Created: (JBAS-5041) MDB transaction timeout from method-attributes
by Adrian Brock (JIRA)
MDB transaction timeout from method-attributes
----------------------------------------------
Key: JBAS-5041
URL: http://jira.jboss.com/jira/browse/JBAS-5041
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: EJB2, EJB3
Affects Versions: JBossAS-4.2.2.GA
Reporter: Adrian Brock
The parent task was not implemented correctly. Instead a new activation-config-property was introduced on
our jms rar.
What is really required is that there should be a JBossMessageEndpoint interface that we implement
that allows a getTransactionTimeout(Method) for use by the inbound rars.
I'd guess the activation-config-property should override the jboss.xml or EJB3 annotation.
Additionally when the MessageEndpoint starts the transaction (rather than the rar in our JMS rar)
it should also look at this configuration.
--
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, 11 months
[JBoss JIRA] Created: (JBAS-5299) Jboss 4.2.2 ignores attributes to tag files when pages are pre-compiled
by Stephen Cresswell (JIRA)
Jboss 4.2.2 ignores attributes to tag files when pages are pre-compiled
-----------------------------------------------------------------------
Key: JBAS-5299
URL: http://jira.jboss.com/jira/browse/JBAS-5299
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.2.2.GA
Environment: Ubuntu 7.10, java 6.03, JBoss 4.2.2.GA
Reporter: Stephen Cresswell
Assigned To: Remy Maucherat
The following will not work on JBoss 4.2.2.GA when JSPs are precompiled.
<!-- standardHead tag file-->
<%@ taglib prefix="spring" uri="http://www.springframework.org/tags" %>
<%@ attribute name="code" required="true" %>
<head>
<title><spring:message code="site.title"/> - <spring:message code="${code}"/></title>
</head>
<!-- JSP using standard head tag file -->
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags/" %>
<html>
<tags:standardHead code="contactUs.title" />
<body>
<div class="pod">
<h2><spring:message code="contactUs.label"/></h2>
<spring:message code="contactUs.address"/>
</div>
</body>
</html>
Even though the standardHead tag is passed a valid message key 'contactUs.title', when precompiled this value is translated to the empty string, causing the following error.
javax.servlet.ServletException: javax.servlet.jsp.JspTagException: No message found under code '' for locale 'en_GB'.
The page works fine if not precompiled.
It also works fine when deployed to tomcat 5.5.26 precompiled or otherwise.
The same war that fails on JBoss 4.2.2.GA works if deployed to 4.2.1.GA
I have created a demonstration app if required.
--
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, 11 months
[JBoss JIRA] Created: (JBAS-4813) EAR with WAR classloading isolation & commons-httpclient
by C←dric Chantepie (JIRA)
EAR with WAR classloading isolation & commons-httpclient
--------------------------------------------------------
Key: JBAS-4813
URL: http://jira.jboss.com/jira/browse/JBAS-4813
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading, Web (Tomcat) service
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1
Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
jrockit-R26.4.0-jdk1.5.0_06
Reporter: C←dric Chantepie
Assigned To: Scott M Stark
Priority: Blocker
We have an EAR including 4 modules :
- an ejb .jar,
- persistence .har
- 2 webapps.
3 modules -- the ejb .jar and the 2 webapps, depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.
== META-INF/jboss-app.xml ==
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
"http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
<jboss-app>
<loader-repository>my.package:loader=My.ear
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
<jmx-name>my.package:module=My.ear</jmx-name>
<module>
<har>MyPersistence.har</har>
</module>
</jboss-app>
Then I've added Class-Path attribute in ejb .jar manifest.
== ejb.jar | META-INF/MANIFEST.MF ==
Manifest-Version: 1.0
Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
ucene-analyzers-2.0.0.jar
(Line breaks there are as in MANIFEST.MF when I extract it from the jar.)
I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.
== webapp1.war | META-INF/MANIFEST.MF ==
Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
.jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
ailer.jar lib/commons-httpclient-3.1.jar
== webapp2.war | META-INF/MANIFEST.MF ==
Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
APSHOT.jar lib/commons-httpclient-3.1.jar
And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".
== webapp1.war | WEB-INF/MANIFEST.MF ==
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
<jboss-web>
<context-root>/BO</context-root>
<virtual-host>www.my-vhost.com</virtual-host>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>my.package:loader=My.ear
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
== webapp2.war | WEB-INF/MANIFEST.MF ==
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
<jboss-web>
<context-root>/</context-root>
<virtual-host>www.my-vhost.com</virtual-host>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>my.package:loader=My.ear
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.
The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one.
If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.
I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.
2 of these test server have the same linux version (kernel), excepted SMP support.
Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.
So please if you can give some useful information.
--
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, 11 months
[JBoss JIRA] Created: (JBAS-4249) isUserInRole returns always false when jacc is enabled and the principal roles are empty
by Roland Räz (JIRA)
isUserInRole returns always false when jacc is enabled and the principal roles are empty
----------------------------------------------------------------------------------------
Key: JBAS-4249
URL: http://jira.jboss.com/jira/browse/JBAS-4249
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.0.5.GA
Reporter: Roland Räz
Assigned To: Remy Maucherat
We are using our won jacc policy and login modules that don't add (cache) the roles in the principal. In this situation, the org.jboss.web.tomcat.security.JaccAuthorizationRealm hasRole method always returns false. The reason behind that is that the method hasRole setups a Principal array that does not contain the principal itself (only the roles are contained) when getPrincipalRoles return a not null Set. The getPrincipalRoles retuns for the above described setup not null.
The following code fixes the issue:
public boolean hasRole(Principal principal, String name)
{
...
Principal[] principals = {principal};
Set roles = getPrincipalRoles(principal);
if( roles != null )
{
principals = new Principal[roles.size() + 1];
principals[0]= principal;
Iterator it = roles.iterator();
for (int i=1;it.hasNext();i++) {
principals[i] =(Principal) it.next();
}
}
...
In my opinion it would be even cleaner to use only the Principal and do not using the principal roles as own identity when querying a jacc provider. JBoss could then still extract in it's own jacc provider the principal roles from the principal. In the current design there is a clash between the role and principal names. The better solution is used in the EJB 2.x code (org.jboss.ejb.enterpriseContext.isCallerInRoleCheckForJacc();
It looks like this for servlets:
...
Principal[] principals = {principal};
...
--
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, 11 months
[JBoss JIRA] Created: (JBAS-5981) ActiveSessions should have consistent meaning in both clustered and non-clustered session manager
by Paul Ferraro (JIRA)
ActiveSessions should have consistent meaning in both clustered and non-clustered session manager
-------------------------------------------------------------------------------------------------
Key: JBAS-5981
URL: https://jira.jboss.org/jira/browse/JBAS-5981
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Paul Ferraro
Assignee: Remy Maucherat
Priority: Minor
Fix For: JBossAS-5.0.0.GA
The "ActiveSessions" attribute of the non-clustered session manager returns the number of active sessions on the server. In the clustered case, this attribute takes on a different meaning and returns the number of active sessions on all servers in the partition. A separate "LocalActiveSessions" attribute returns just the active sessions on the local node.
"ActiveSessions" should return the same value for both the clustered and non-clustered session manager. The clustered session manager should replace "LocalActiveSessions" with an "ActiveReplicatedSessions" attribute that returns the total number of active sessions in the partition.
Mod-cluster has an ActiveSessionsLoadMetric that determines the number of active sessions on the node using this attribute on the session manager. Requiring the user to override the attribute name depending on whether or not they use session replication is rather sloppy. Instead, this attribute should have a consistent meaning regardless of session manager implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months