Develop Reference

Deployment Issue in Weblogic 10.3 which targets to the Managed Server

I am using Weblogic 10.3.I created a managed server along with machine.It is running well.
I try to deploy the application in weblogic I deployed which points to running managed Server but the deployment gets fails.
I am getting error has "" org/antlr/runtime/RecognitionException "".
Please help me to resolve this issue.
Thanks in advance.

I was confused, what is differences between jboss esp6.1 and jboss as7?

i am a newbie,today i am tring to use jboss and deploy my application with jboss,i did't use
jboss before ,when i try to download ,i log into the official website,click download Jboss Application Software 7,but it jump to JBOSS eap6.1.final download place,so i download the EAP6.1 instead. after sometinme of probing,i start the server with standalone mode and upload my app war file with Management Console,but i cann't access my app,my application name is MedicineManage
i try with: http://localhost:8080/medicineManage/login.jsp
here is the result
JBWEB000065: HTTP Status 404 - /medicineManage/login.jsp
what's the difference between AS7 and EAP6.1.0
somebody can explain for me ! thanks a lot

AS is the application server and it is an open source.
EAP is the enterprise application platform supported by red hat and red hat is often releasing the patches for this version.
For more detail just go through the web page it has clear difference between application server AS and Enterprise application platform.
http://planet.jboss.org/post/security_community_jboss_as_versus_jboss_eap

Boot time of Jboss as 7 is less than Jboss EAP 6.1 and also memory consumption is less in Jboss as 7.
Find more about Jboss EAP 6.1 from here and Jboss as 7 from here. Follow these links for documentation about Jboss EAP 6.1 and Jboss as 7.
How ever JBoss EAP is a product that is officially supported by Red Hat. You get patches, updates, security fixes etc. It is shipped secure.

Web Service with glassfish and tomcat

I have generated a RestFul web service using NetBeans 7.2.1, Tomcat 6+ and MySQL, but When I test this Web Service I get the following exception:
java.lang.RuntimeException: javax.naming.NameNotFoundException: Name persistence-factory is not bound in this Context
This web service when implemented in the same way using glassfish.
Need some guidance, totally lost and have been searching for some fix for 3 days now' but un able to solve it' some guidance will be gud'

JBoss 7 application, start/stop from ui?

I am running an application on a Jboss 6 server and using mbeans to start/stop my app without redeploying/restarting server. I was testing on JBoss 7 and saw that there were no mbean support.
How do I create that functionality now? I've yet to find anything on this.

There is MBean support.
In what area do you experience problems: when deploying MBeans or accessing them, ...?

In the meantime (2015), there is a portation of the AS5 jmx-console, which can be deployed to AS7 and WildFly.
See https://github.com/wildfly-extras/jmx-console

Calling web service from another ejb on startup

Using jboss-esb 5.1.0.GA
I have a web service that an EJB that I have makes calls on when it is started. This EJB may be installed in the same JBoss instance as the web service. If I start JBoss, let it come up completely, then deploy my EJB into the same instance, all is well. However, if I leave it deployed and restart JBoss, when the EJB gets to the point where it makes a call on the web service, the Application Server start-up process hangs. Now the WebService was deployed prior to the EJB according to the logs. It acts like the web server that is serving the WS calls is not yet up either. I can try to access the WSDL via a web browser and that fails until the JBoss instance is fully started. i can see if I have my dependencies wrong and it would error out on deployment, but I get no error, it just hangs indefinitely. Any ideas where to go from here. Any more information you need?
Thanks,
-Rob

You can ensure the order of deployment if you bundle your webservice war and ejb jar into one single ear file. In this case the ejb jar is always deployed first.

Appears there is a bug in the version of JBoss that we are using. We were required to register for an event to notify us when JBoss was up, then we made our WS calls and things work fine now.