[JBoss JIRA] Created: (JASSIST-44) Maven profiles for tools.jar should take account of Mac OS
by Martin Burger (JIRA)
Maven profiles for tools.jar should take account of Mac OS
----------------------------------------------------------
Key: JASSIST-44
URL: http://jira.jboss.com/jira/browse/JASSIST-44
Project: Javassist
Issue Type: Bug
Environment: Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.4.11" arch: "i386" Family: "unix"
Reporter: Martin Burger
Assigned To: Shigeru Chiba
The pom.xml uses different profiles to add the tools.jar to the dependencies. However, it is already included in the runtime for Mac OS X and some free JDKs and does not exist as a separate file 'tools.jar'. See: http://maven.apache.org/general.html#tools-jar-dependency
As soon as http://jira.codehaus.org/browse/MNG-3106 gets fixed, activation should look like the following example:
<activation>
<jdk>1.6</jdk>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
In the meantime
<profiles>
<profile>
<id>tools.jar</id>
<activation>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.6</version>
<scope>system</scope>
<optional>true</optional>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
</profile>
</profiles>
should do the job. It could be a permanent solution because the different profiles differ only in the version element.
--
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, 1 month
[JBoss JIRA] (JASSIST-151) javassist.runtime.Desc cannot load array types when using thread's context classloader
by Yanic Inghelbrecht (JIRA)
Yanic Inghelbrecht created JASSIST-151:
------------------------------------------
Summary: javassist.runtime.Desc cannot load array types when using thread's context classloader
Key: JASSIST-151
URL: https://issues.jboss.org/browse/JASSIST-151
Project: Javassist
Issue Type: Bug
Affects Versions: 3.15.0-GA
Environment: Any
Reporter: Yanic Inghelbrecht
Assignee: Shigeru Chiba
When the Desc class has to load an array type during instrumentation, it fails when its global flag useContextClassLoader is set to true.
The following testcase demonstrates this :
---
package test_descForName;
import javassist.runtime.Desc;
import org.junit.Assert;
import org.junit.Test;
public class TestDescForName {
@Test
public void test() {
// try it using classloader of TestDescForName
Desc.useContextClassLoader = false;
Assert.assertTrue(Desc.getClazz("[Ljava.lang.String;") != null);
Thread.currentThread().setContextClassLoader(TestDescForName.class.getClassLoader());
Desc.useContextClassLoader = true;
Assert.assertTrue(Desc.getClazz("[Ljava.lang.String;") != null);
}
}
---
The root cause for this defect is the use of ClassLoader#loadClass in method getClassObject (which doesn't handle array types):
private static Class getClassObject(String name) throws ClassNotFoundException {
if (useContextClassLoader)
return Thread.currentThread().getContextClassLoader().loadClass(name);
else
return Class.forName(name);
}
The fix is to use the three argument version of Class#forName (which does handle array types):
private static Class getClassObject(String name) throws ClassNotFoundException {
if (useContextClassLoader)
return Class.forName(name, true, Thread.currentThread().getContextClassLoader());
else
return Class.forName(name);
}
Hooray, my first fix for javassist :)
Best regards,
Yanic
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-4012) xts-environment.url in standalone-xts.xml cannot take an expression
by Ivo Studensky (JIRA)
Ivo Studensky created AS7-4012:
----------------------------------
Summary: xts-environment.url in standalone-xts.xml cannot take an expression
Key: AS7-4012
URL: https://issues.jboss.org/browse/AS7-4012
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Final
Reporter: Ivo Studensky
Assignee: Paul Robinson
Priority: Critical
Fix For: 7.1.1.Final
AS7 configuration should include expressions like ${jboss.bind.address:127.0.0.1} instead of hardcoded hostnames in URLs. The xts-environment.url in standalone-xts.xml is set to 'http://localhost:8080/ws-c11/ActivationService' which makes troubles when AS7 is bound to a different IP than localhost or in IPv6 environment. See the conf file snippet:
{noformat}
<subsystem xmlns="urn:jboss:domain:xts:1.0">
<xts-environment url="http://localhost:8080/ws-c11/ActivationService"/>
</subsystem>
{noformat}
But when I tried to change the URL to 'http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService', the XTS tests in AS7 testsuite failed with:
{noformat}
13:59:11,669 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-4-thread-1) Failed: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.testRollback: com.arjuna.wst.SystemException: javax.xml.ws.WebServiceException: Could not send Message.
at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.startTransaction(UserTransactionImple.java:308) [jbossxts-4.16.2.Final.jar:]
at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:80) [jbossxts-4.16.2.Final.jar:]
at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:70) [jbossxts-4.16.2.Final.jar:]
at org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.testRollback(WSATTestCase.java:113) [classes:]
...
Caused by: java.net.MalformedURLException: For input string: "127.0.0.1}:8080"
at java.net.URL.<init>(URL.java:601) [rt.jar:1.6.0_31]
at java.net.URL.<init>(URL.java:464) [rt.jar:1.6.0_31]
at java.net.URL.<init>(URL.java:413) [rt.jar:1.6.0_31]
at org.apache.cxf.transport.http.HTTPConduit.setupURL(HTTPConduit.java:689)
at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:463)
at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)
{noformat}
The cause of this failure was that the expression from the url was not resolved.
Paul, please could you take a look at it and fix the XTS configuration to be able to resolve expressions?
I tried to change line 149 in org.jboss.as.xts.XTSSubsystemAdd class to:
{noformat}
final String coordinatorURL = model.get(CommonAttributes.XTS_ENVIRONMENT).hasDefined(ModelDescriptionConstants.URL) ? context.resolveExpressions(model.get(CommonAttributes.XTS_ENVIRONMENT, ModelDescriptionConstants.URL)).asString() : null;
{noformat}
but it did not help, the model.get(CommonAttributes.XTS_ENVIRONMENT, ModelDescriptionConstants.URL) node seems to be String type instead of expression type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBAS-9475) .jsp fails to recompile after redeployment
by Lami Akagwu (JIRA)
Lami Akagwu created JBAS-9475:
---------------------------------
Summary: .jsp fails to recompile after redeployment
Key: JBAS-9475
URL: https://issues.jboss.org/browse/JBAS-9475
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.2.2.GA
Environment: all
Reporter: Lami Akagwu
Fix For: No Release
When redeploying a .ear or .war containing .jsps, there are many situations causing a .jsp that needs to be recompiled to not be recompiled, or to be recompiled continuously.
Any situation causing the timestamp of the modified .jsp to be older than the timestamp of its compiled class will cause it not to be recompiled; for example:
- reverting to a previous version of the .jsp using a version control
- timezone difference between development and production server
- .jsp never visited in production server until after change is made, which can happen for a rarely visited page, or a newly deployed server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month