[JBoss JIRA] (JBWEB-144) JSP EL ternary operator requires space before colon
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/JBWEB-144?page=com.atlassian.jira.plugin.... ]
Jean-Frederic Clere resolved JBWEB-144.
---------------------------------------
Resolution: Done
> JSP EL ternary operator requires space before colon
> ---------------------------------------------------
>
> Key: JBWEB-144
> URL: https://issues.jboss.org/browse/JBWEB-144
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Tomcat
> Affects Versions: JBossWeb-2.0.0.GA_CP09
> Reporter: Mike Millson
> Assignee: Jean-Frederic Clere
> Attachments: test.jsp
>
>
> JSP EL that worked on JBoss AS 4.0.5.GA does not work on EAP. For example, the following does not work:
> <c:set var="truevalue" value="true" />
> <c:set var="falsevalue" value="false"/>
> <c:out value="${not empty param.yes?truevalue:falsevalue}"/>
> It throws this error:
> 2009-06-11 10:40:57,487 ERROR [org.apache.catalina.core.ContainerBase] Servlet.service() for servlet jsp threw exception
> org.apache.jasper.JasperException: /jsp/case305721.jsp(27,3) "${not empty param.yes?truevalue:falsevalue}" contains invalid expression(s): javax.el.ELException: Error Parsing: ${not empty param.yes?truevalue:falsevalue}
> at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
> But this works with a space added before the colon:
> <c:out value="${not empty param.yes?truevalue :falsevalue}"/>
> This is a bug[1] that was originally fixed in Tomcat 6.0.18[2], but was subsequently found to cause a regression[3], so was re-implemented in 6.0.19.
> [1]http://issues.apache.org/bugzilla/show_bug.cgi?id=42565
> [2]http://tomcat.apache.org/tomcat-6.0-doc/changelog.html
> [3]http://issues.apache.org/bugzilla/show_bug.cgi?id=45511
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBWEB-97) Cross-context request dispatching is not working for PHP files
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/JBWEB-97?page=com.atlassian.jira.plugin.s... ]
Jean-Frederic Clere resolved JBWEB-97.
--------------------------------------
Resolution: Out of Date
> Cross-context request dispatching is not working for PHP files
> --------------------------------------------------------------
>
> Key: JBWEB-97
> URL: https://issues.jboss.org/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
> Assignee: Jean-Frederic Clere
> Attachments: foo.zip, ScriptEnvironment.java, servlets-php.jar, servlets-php.jar
>
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBWEB-99) PHP servlet and context path
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/JBWEB-99?page=com.atlassian.jira.plugin.s... ]
Jean-Frederic Clere resolved JBWEB-99.
--------------------------------------
Resolution: Out of Date
> PHP servlet and context path
> ----------------------------
>
> Key: JBWEB-99
> URL: https://issues.jboss.org/browse/JBWEB-99
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossWeb-1.0.1.GA
> Reporter: Thomas Heute
> Assignee: Jean-Frederic Clere
> Attachments: servlets-php.jar
>
>
> By testing an existing app, i realized that $_SERVER['PHP_SELF'] was not set correctly.
> By definition: http://ch2.php.net/reserved.variables
> ===================
> 'PHP_SELF'
> The filename of the currently executing script, relative to the document root. For instance, $_SERVER['PHP_SELF'] in a script at the address http://example.com/test.php/foo.bar would be /test.php/foo.bar.
> ===================
> Unfortunately in the JBossWeb environement we have the context path in between.
> So getting that variable on http://www.example.com/myContextPath/foo/test.php returns "/foo/test.php" when it should return "/myContextPath/foo/test.php"
> In order to have existing PHP application working with no modification, $_SERVER['PHP_SELF'] should start with the context path.
> In general, other SERVER properties should be checked to see their meaning in JBossWeb.
> It would also be convenient to have access to the context path from a PHP script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1425) Upgrade RESTEasy from 3.0-beta-4 (April 10) to 3.0-beta-6 (May 29)
by Juergen Zimmermann (JIRA)
Juergen Zimmermann created WFLY-1425:
----------------------------------------
Summary: Upgrade RESTEasy from 3.0-beta-4 (April 10) to 3.0-beta-6 (May 29)
Key: WFLY-1425
URL: https://issues.jboss.org/browse/WFLY-1425
Project: WildFly
Issue Type: Feature Request
Components: REST
Affects Versions: 8.0.0.Alpha1
Reporter: Juergen Zimmermann
Assignee: Stuart Douglas
Attachments: resteasy-jboss-modules-3.0-beta-6.zip
RESTEasy 3.0-beta-6 (since beta-5) provides a significant improvement:
JSON mapping can be defined via JAXB annotations instead of proprietary Jackson annotations.
I'll attach the zip file of the RESTEasy 3.0-beta-6 distribution to patch JBossAS 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1423) Provide configurable timeout for ExternalContextObjectFactory.createContext
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-1423?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda commented on WFLY-1423:
-----------------------------------------
So when external context provider does not provide the option then the user can't set anything to avoid long timeouts ... which is not optimal.
Can you give us estimation how hard would it be to implement general timeout check? Thank you.
> Provide configurable timeout for ExternalContextObjectFactory.createContext
> ---------------------------------------------------------------------------
>
> Key: WFLY-1423
> URL: https://issues.jboss.org/browse/WFLY-1423
> Project: WildFly
> Issue Type: Feature Request
> Components: Naming
> Affects Versions: 8.0.0.Alpha1
> Reporter: Jan Martiska
> Assignee: Stuart Douglas
>
> An ExternalContextObjectFactory's createContext method might take a long time to complete, because usually it will communicate over the network. It would be useful to be able to cap the waiting time, and there should be a timeout enabled by default -- it might happen that the remote server will get stuck during the context creation and the external context will never be successfully created (or it will just take too much time). If a timeout occurs, createContext can for example return null, or throw an exception, not sure which is better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JGRP-1637) Counters overflow
by Bela Ban (JIRA)
Bela Ban created JGRP-1637:
------------------------------
Summary: Counters overflow
Key: JGRP-1637
URL: https://issues.jboss.org/browse/JGRP-1637
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.4
We have some counters which might see a lot of increments. Investigate which counters are affected (and how) by a potential wraparound, e.g. longs wrap around at 2^63 and go negative.
For example, storing delivery times in nanoseconds and totalling that number could end up with an overflow as e.g. 2ms = 2000000ns, for 1 million msgs/sec would overflow in roughly 7 weeks ! That's the reason org.jgroups.util.Average was created: instead of totalling delivery time and the number of deliveries to compute avg delivery time, we only maintain a fixed array of delivery times, and its elements are randomly overwritten with new values, so we only keep the (more or less) most recent N values to compute the average.
Using a long for a message sequence number should not be an issue: even if we send 1 million messages / sec, we could send for roughly 290'000 years !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann updated WFLY-1406:
-------------------------------------
Attachment: tar.log
The attached tar.log contains the output of "tar tf shop2.war"
> Hibernate cannot process package-info.java any more
> ---------------------------------------------------
>
> Key: WFLY-1406
> URL: https://issues.jboss.org/browse/WFLY-1406
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Scott Marlow
> Attachments: server.log, tar.log
>
>
> I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError:
> "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below.
> Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1:
> @XmlAccessorType(FIELD)
> @Vetoed
> package de.shop.artikelverwaltung.domain;
> import static javax.xml.bind.annotation.XmlAccessType.FIELD;
> import javax.enterprise.inject.Vetoed;
> import javax.xml.bind.annotation.XmlAccessorType;
> The stacktrace:
> ...
> 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21]
> at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final]
> ... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1424) Remote lookup for Referenceable returns Reference and not the real object
by Natasha Biryukov (JIRA)
Natasha Biryukov created WFLY-1424:
--------------------------------------
Summary: Remote lookup for Referenceable returns Reference and not the real object
Key: WFLY-1424
URL: https://issues.jboss.org/browse/WFLY-1424
Project: WildFly
Issue Type: Feature Request
Affects Versions: 8.0.0.Alpha1
Reporter: Natasha Biryukov
In JBoss EAP6.1 Alfa and Beta during remote lookup for obejct that implements Referenceable the coresponding ObjectFactory is not called, as a result the Reference object is returned and not the real one.
Code example:
public class Fruit implements Referenceable {
String fruit;
public Fruit(String f) {
fruit = f;
}
public Reference getReference() throws NamingException {
return new Reference(
Fruit.class.getName(),
new StringRefAddr("fruit", fruit),
FruitFactory.class.getName(),
null);
}
public String toString() {
return fruit;
}
}
public class FruitFactory implements ObjectFactory {
@Override
public Object getObjectInstance(Object obj, Name name, Context nameCtx, Hashtable<?, ?> environment) throws Exception {
Reference localObject1;
if (obj instanceof Reference) {
localObject1 = (Reference) obj;
Object fruit = localObject1.get("fruit").getContent();
return new Fruit((String)fruit);
} else {
return obj;
}
}
}
Fruit f = new Fruit("apple");
context.bind("apple", f);
Fruit f1 = (Fruit)context.lookup("apple");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month