[JBoss JIRA] Created: (JBAS-4125) Move clustering test support classes to test module
by Brian Stansberry (JIRA)
Move clustering test support classes to test module
---------------------------------------------------
Key: JBAS-4125
URL: http://jira.jboss.com/jira/browse/JBAS-4125
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Brian Stansberry
The org.jboss.test.JBossClusteredTestCase, JBossClusteredTestServices and JBossClusteredTestSetup classes should be moved out of the testsuite module and into test. They are just utility classes to support deployment to more than one AS instance and exposure to test clients of more than one JNDI URL and base HTTP URL. EJB3 uses them as well, so they need to be in a binary to allow EJB3 to decouple from the AS.
This should be done on both trunk and Branch_4_2.
--
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, 10 months
[JBoss JIRA] Created: (EJBTHREE-823) Unable to call ejb remotely
by Sureshbabu Thyvalappil (JIRA)
Unable to call ejb remotely
---------------------------
Key: EJBTHREE-823
URL: http://jira.jboss.com/jira/browse/EJBTHREE-823
Project: EJB 3.0
Issue Type: Bug
Environment: JBOSS 4.0.5 with EJB 3.0
Reporter: Sureshbabu Thyvalappil
I'm using JBOSS 4.0.5GA with ejb3. I am running into weird behavior when running java client from remote machine. If I run it from the same machine where the jboss server is running, no problem. So here is the behavior I'm noticing.
FOr the jndi lookup of ejb, it is connecting the remote server and gets a reference to the ejb. But when I call a method on the ejb reference, it is trying to call a method on the local machine( I mean the same machine where the client is running).
Sounds very weird to me. Any help is appreciated from EJB3 experts.
I upgraded to EJB3 RC9 patch1, but same behavior.
Here is the client code ..
try
{
Properties p=new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
p.put(Context.PROVIDER_URL,"jnp://remote-host:1099");
InitialContext ctx = new InitialContext(p);
IReportService report = (IReportService) ctx.lookup(
"ejb3/xxx/ReportService");
System.out.println("Got the ejb remote reference = "+report);
System.out.println("report.resubmit.."+report.resubmit(null,0L));
ReportJob reportJob = new ReportJob();
System.out.println("B4 report.submitRequest..");
report.submitRequest(reportJob);
System.out.println("After report.submitRequest..");
}
catch (Exception e)
{
e.printStackTrace();
}
--
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, 10 months
[JBoss JIRA] Created: (JBPM-835) check out jeff's bug reports
by Tom Baeyens (JIRA)
check out jeff's bug reports
----------------------------
Key: JBPM-835
URL: http://jira.jboss.com/jira/browse/JBPM-835
Project: JBoss jBPM
Issue Type: Task
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
When I created a project in Eclipse with jbpm-jpdl-3.2.Beta2 as the source there was a number of compilation issues. These I could resolve as follows:
1) jms example - remove or comment out the offending code. This example uses APIs that do not exist in the product.
2) org.apache.tools.ant.BuildException in src/identity/LoadIdentitiesTask required ant.jar to be added to lib
3) my rules examples require drools-compiler-3.0.5 and drools-core-3.0.5 to be added to lib
4) org.jbpm.jcr.jackrabbit.JackrabbitJcrServiceFactory requires jackrabbit-core-1.0.1 to be added to lib
--
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, 10 months