[EJB3] - Re: newbie question: ejb3 tutorial examples
by Meena Rajani
Meena Rajani [http://community.jboss.org/people/MeenaRajani] created the discussion
"Re: newbie question: ejb3 tutorial examples"
To view the discussion, visit: http://community.jboss.org/message/579040#579040
--------------------------------------------------------------
Hi
I am getting the same error with the same example. How you added add jnp-client.jar . I am using I am using Elipse Helios and Jboss 6. I creted a java project with exisiting build file.
The error stack is
Exception in thread "main" javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.tutorial.stateless.client.Client.main(Client.java:34)
Can you please reply in detail as I am stucked with eclipse and Jboss for more than 3 weeks.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/579040#579040]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[jBPM] - Understanding Human Task call
by Odelya Holiday
Odelya Holiday [http://community.jboss.org/people/odelyaholiday] created the discussion
"Understanding Human Task call"
To view the discussion, visit: http://community.jboss.org/message/581276#581276
--------------------------------------------------------------
Hi!
I created the BPMN file. The first item is human task. I set on the human task actorId Phil,Joe. My process needs to start with parameters of requestData.
I started the process like this:
// 2. get the session to start a process.
ManagementBean managementBean = (OnMediaManagementBean) FacesContext.getCurrentInstance().getExternalContext().getApplicationMap().get("ManagementBean");
StatefulKnowledgeSession ksession = managementBean.getKsession();
// 3. Starting the process
Map<String, Object> parameters = new HashMap<String, Object>();
parameters.put("requestData", prgoramData);
ProcessInstance pI = ksession.startProcess("MyProcess", parameters);
Now, I expect the process to reach the human task and display my On Entry Actions.
Intead I get an exception "org.drools.WorkItemHandlerNotFoundException: Could not find work item handler for Human Task"
Do I need to start it somewhere?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581276#581276]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Tools] - JPA Project - cannot resolve tables
by Claus Dreyer
Claus Dreyer [http://community.jboss.org/people/cdreyer1] created the discussion
"JPA Project - cannot resolve tables"
To view the discussion, visit: http://community.jboss.org/message/580153#580153
--------------------------------------------------------------
Hi,
I have a simple project made with the 'JPA Project' wizard. My development setup is Eclipse 3.6 Helios, JBoss Tools 3.2.CR1 and MySQL 5.5.8. Everything is running on Windows.
The problem is that I get the error *Table "MyEntity" cannot be resolved*
The entity class MyEntity is a very simple test class. The corresponding table was created with a DDL file made by the JPA Tools -> Generate Tables from Entities... wizard.
I have tried many things to get it to work. I finally made an entity class called lowercase (all of the letters are lower case), and suddenly it worked...
It seems that the tools (I don't know if it is JBoss Tools or Dali) does a case sensitive comparison on the class name and table name. By default MySQL on Windows converts all table names to lower case. This is not the case for column names where lettercase is preserved. On Unix (and Mac I believe) lettercase is preserved by default by MySQL.
MySQL has a global system variable called +lower_case_table_names+ (see MySQL doc: http://dev.mysql.com/doc/refman/5.5/en/identifier-case-sensitivity.html Identifier Case Sensitivity). According to the MySQL documentation it can be set to 2 (instead of 1) and lettercase will be preserved on Windows. However, this has implications for your database statements which now must have the correct lettercase.
I have tried to start MySQL with lower_case_table_names=2, then drop the existing database, re-create the database, run the DDL for my two simple classes mentioned above and then the tools work.
I don't know if this issue should be classified as a bug or just filed on quirks related to MySQL.
Kind regards,
Claus
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/580153#580153]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Web Services] - Re: Attaching a WS-Security policy forces use of "Standard WSSecurity Endpoint" configuration
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] created the discussion
"Re: Attaching a WS-Security policy forces use of "Standard WSSecurity Endpoint" configuration"
To view the discussion, visit: http://community.jboss.org/message/581102#581102
--------------------------------------------------------------
Ciao Riccardo,
basing the handlers configuration for ws-security on the "Standard WSSecurity Endpoint" conf there is most likely something that should be changed (having that as a configurable option would be better)... the point is that the WS-Policy usage here should basically allow the engine to setup WS-Security without the need of user provided security handler configuration.
This said, however, the WS-Policy engine in JBossWS-Native is experimental and no real WS-*Policy implementation was ever based on that (mainly because at the time that code was written, the multiple-stack support work was being started and then we decided to go for CXF/Metro integration stacks, especially for the WS-* support). While there's indeed some initial code for WS-SecurityPolicy in native, that's not finished.
So, if you need a real support for WS-Policy (especially for WS-Security Policy), you should really evaluate moving to JBossWS-CXF stack. If you can't afford also moving to JBoss AS 6 Final and want to stay on 5.1.0, JBossWS-CXF 3.4.0 is the version for you (see http://community.jboss.org/docs/DOC-13569 http://community.jboss.org/wiki/JBossWS-SupportedTargetContainers)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581102#581102]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months