[JBoss JIRA] Created: (JBPORTAL-1076) User registration with email verification does not work
by Jean-Franois El Fouly (JIRA)
User registration with email verification does not work
-------------------------------------------------------
Key: JBPORTAL-1076
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1076
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.4 Final
Environment: Development PC / Windows XP
Reporter: Jean-Franois El Fouly
Assigned To: Julien Viet
In portal-core.war/WEB-INF/portlet.xml I changed the subscriptionMode parameter from automatic to emailVerification (I have the feeling it worked in JBoss Portal 2.0 but I may be wrong).
I tested the functionality and got an error 500 page with a stack trace:
2006-10-08 20:19:42,656 ERROR [org.jboss.portal.core.portlet.user.UserPortlet] The portlet threw an
exception
java.lang.NullPointerException
at org.jboss.portal.core.portlet.user.UserPortlet.generateValidationEmail(UserPortlet.java:936)
at org.jboss.portal.core.portlet.user.UserPortlet.userRegister(UserPortlet.java:624)
I had a look at the code at this place. There is a TODO that makes me think it is not meant to work in this version. Can someone confirm ?
I'll revert to automatic subscription but... I don't like that too much.
--
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
19 years, 6 months
[JBoss JIRA] Created: (JGRP-299) NotificationBusDemo problem with 2.4CR2
by Christian Pekeler (JIRA)
NotificationBusDemo problem with 2.4CR2
---------------------------------------
Key: JGRP-299
URL: http://jira.jboss.com/jira/browse/JGRP-299
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4
Environment: MacOSX, Java 1.5
Reporter: Christian Pekeler
Assigned To: Bela Ban
[/Users/christian/Projects/JGroups-2.4CR2.src]> java -cp dist/jgroups-all.jar:lib/commons-logging.jar:lib/concurrent.jar:lib/xalan.jar org.jgroups.demos.NotificationBusDemo
Starting NotificationBus with name BusDemo
Sep 5, 2006 4:56:53 PM org.jgroups.JChannel init
INFO: JGroups version: 2.4CR2
Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets
INFO: sockets will use interface 192.168.5.142
Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets
WARNING: traffic class of 8 could not be set, will be ignored
java.net.SocketException: Invalid argument
at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)
at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:299)
at java.net.DatagramSocket.setTrafficClass(DatagramSocket.java:1052)
at org.jgroups.protocols.UDP.createSockets(UDP.java:456)
at org.jgroups.protocols.UDP.start(UDP.java:383)
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:589)
at org.jgroups.stack.DownHandler.run(Protocol.java:118)
Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets
WARNING: traffic class of 8 could not be set, will be ignored
java.net.SocketException: Invalid argument
at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)
at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:299)
at java.net.DatagramSocket.setTrafficClass(DatagramSocket.java:1052)
at org.jgroups.protocols.UDP.createSockets(UDP.java:527)
at org.jgroups.protocols.UDP.start(UDP.java:383)
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:589)
at org.jgroups.stack.DownHandler.run(Protocol.java:118)
Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets
--
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
19 years, 6 months
[JBoss JIRA] Created: (JBRULES-481) LeftInputAdater.updateNewNode does incorrect propagation
by Mark Proctor (JIRA)
LeftInputAdater.updateNewNode does incorrect propagation
--------------------------------------------------------
Key: JBRULES-481
URL: http://jira.jboss.com/jira/browse/JBRULES-481
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 3.0.4
Reporter: Mark Proctor
Assigned To: Edson Tirelli
Fix For: 3.0.5, 3.1-m1
// Get the newly attached TupleSink
final TupleSink sink = (TupleSink) getTupleSinks().get( getTupleSinks().size() - 1 );
// Iterate the memory and assert all tuples into the newly attached TupleSink
final Map memory = (Map) workingMemory.getNodeMemory( this );
for ( final Iterator it = memory.values().iterator(); it.hasNext(); ) {
final LinkedList list = (LinkedList) it.next();
for ( LinkedListNode node = list.getFirst(); node != null; node = node.getNext() ) {
sink.assertTuple( (ReteTuple) ((LinkedListObjectWrapper) node).getObject(),
context,
workingMemory );
}
}
We get the last Sink but then we send through ALL tuples in the list to that single sink. yet we know that each tuple is for a specific sink. we instead should grab the handle and create a new tuple which we add to the list.
--
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
19 years, 6 months
[JBoss JIRA] Created: (JBAS-3759) MalformedURLException for "jndi" protocol
by PickATrail (JIRA)
MalformedURLException for "jndi" protocol
-----------------------------------------
Key: JBAS-3759
URL: http://jira.jboss.com/jira/browse/JBAS-3759
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Environment: Liinux (SuSE 10)
JVM: Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)
Reporter: PickATrail
Assigned To: Remy Maucherat
I am getting a MalformedURLException when I instantiate a URL with the "jndi" protocol. Here's some example JSP code:
final ServletContext ctx = session.getServletContext();
final String resourcePath = "/WEB-INF/web.xml";
final URL url = ctx.getResource(resourcePath);
final String externalForm = url.toExternalForm();
// The value of externalForm is something like
// "jndi:/localhost/problem/WEB-INF/web.xml".
// The following line fails under some specifi situation
// -- read on :)
new URL(externalForm);
This code usually works as expected. However, if I deploy and access the BIRT WebViewerExample application (BIRT
is an Eclipse.org project), the 'new URL("jndi:....")' line fails with the following stack trace:
java.net.MalformedURLException: unknown protocol: jndi
at java.net.URL.(URL.java:544)
at java.net.URL.(URL.java:434)
at java.net.URL.(URL.java:383)
at org.apache.jsp.index_jsp._jspService(...)
...
This is really puzzling because the URL class remembers theprotocol handlers, and I have already instantiated a URL for
"jndi" successfully.
I have tried to reproduce the problem on Tomcat 5.5.20 and 5.0.28, without success. So it seems to be a JBoss specific
problem. I'm using JBoss 4.0.4 GA on Linux; JVM build is 1.4.2_11-b06. The version of BIRT I use is 2.1.1.
-- Patrick Lai
--
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
19 years, 6 months
[JBoss JIRA] Created: (EJBTHREE-708) Bundled jboss-ejb3-all.jar is invalid in embeddable container
by Adrian Pillinger (JIRA)
Bundled jboss-ejb3-all.jar is invalid in embeddable container
-------------------------------------------------------------
Key: EJBTHREE-708
URL: http://jira.jboss.com/jira/browse/EJBTHREE-708
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Environment: Linux, Maven, Java 5.
Reporter: Adrian Pillinger
Priority: Blocker
The classes that were bundled together to form the jboss-ejb3-all.jar of the embeddable container are not compatible.
I am calling the following code...
{code}
EJB3StandaloneBootstrap.boot(null);
Collection<URL> deployDirs = getDeployDirURLs();
Collection<URL> persistenceArchives = getPersistenceArchiveURLs();
deployer = EJB3StandaloneBootstrap.createDeployer();
.... get deploy dirs ..
deployer.getDeployDirs().addAll(deployDirs);
deployer.create();
deployer.start();
{code}
When the code gets to deployer.create(); it fails with the following stack trace
{noformat}
java.lang.NoSuchMethodError: org/jboss/ejb3/Ejb3Deployment.<init>(Lorg/jboss/ejb3/DeploymentUnit;Lorg/jboss/ejb3/EAR;)V
at org.jboss.ejb3.embedded.EJB3StandaloneDeployment.<init>(EJB3StandaloneDeployment.java:49)
at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.create(EJB3StandaloneDeployer.java:438)
at com.dolby.pics.test.AbstractEJBTestCase.startupEmbeddedJboss(AbstractEJBTestCase.java:84)
at com.dolby.pics.test.TestSetupWrapper.setUp(TestSetupWrapper.java:32)
at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
{noformat}
The error as you can see is an incompatability between
{noformat}
org.jboss.ejb3.embedded.EJB3StandaloneDeployment
{noformat}
and
{noformat}
org.jboss.ejb3.Ejb3Deployment
{noformat}
I'm guessing that these are from different jars and have been bundled into the same jar without a compile any tests to check that they are compatible.
My code worked absolutely fine with alpha 8 of the embeddable container.
--
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
19 years, 6 months