When you created the projects, you had to select a jboss server runtime, from which the classpath provider would get some classpath entries for compiling it.
The ejb3.0 project is not a webtools project, but was created by jboss ide, which is why it required a jboss server to create.
As a word of warning, ejb3.0 projects are under revision now to more accurately resemble webtools projects and work similarly, so they'll most likely be changing again before the next beta.
Sorry for the inconveniences. I'll try to have a good conversion wizard available for them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980491#3980491
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980491
This would be a nice feature - I want to do that too.
I have to set some system properties so I changed the run.bat of JBoss (it is also possible to start run.bat with parameters). But I don't know how JBossIDE starts the AS. So I don't know where to put the java system properties. currently i am developing with Eclipse IDE but deploying myself. Is there a fix?
best regards,
Dominik
ps: sorry for bad english ~~
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980489#3980489
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980489
I'm using JBossAS 4.0.5GA with JBossWS 1.0.3GA for webservice support. I have a JSR-181 EJB 3.0 Endpoint with document style SOAP messaging.
I've applied JAXB 2.0 annotations to the parameter objects on my service methods. The services deploy, but the WSDL generator seems to ignore the annotations completely. At this point it looks like the JBossWS 1.0.3GA is not supporting JAXB 2.0. Is this correct? (i.e. @XmlType, @XmlElement, @XmlList)
What are you using to generate the WSDL schema, and how can I customize the schema to match my object model?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980487#3980487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980487
I'm pretty sure I have found the problem. Can someone who is seeing this issue try this as a workaround?
First, don't use the MyFaces StartupServletContextListener. This listener should not be used in a portlet environment.
Second, get your system set to where you see the java.lang.NullPointerException: serialFactory. That is the error that must be fixed.
Third, subclass MyFacesGenericPortlet and put these two lines in the init() method:
super();
| getPortletContext().setAttribute("org.apache.myfaces.SERIAL_FACTORY", new org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory
| ());
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980482#3980482
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980482