EJB3 + Tomcat + Glassfish Question

Guys, I'm a new comer of this EJB 3. I just learned how to create a session ejb for the past few weeks.
My first try was to create a local session ejb deployed on the same container (glassfish), and it was run perfectly.
My second try was to create a remote session ejb and deployed on different container, and it could not work.
I already spent about 1 week to find answers for this problem, and I have not found any, and this is frustrating me.
I use these:
Eclipse Europe 3.3.1.1
Glassfish V2
Tomcat 5.5
I created 2 projects for this, the first one is the Enterprise Application Project includes the EJB Project.
The second one is the Dynamic Web Project.
Inside the EJB project, I created an interface and an implementation class.
Inside the Web Project, I added a servlet and put all the calling code inside the servlet.
I tried to running the code within the eclipse, I have already installed the server inside the eclipse.
I followed all the instructions in the EJB Glassfish FAQ and still not working.
This is my ejb interface:
package com.ejb3;
import javax.ejb.Remote;
@Remote
public interface HelloWorldRemote {
     public String sayHello(String name);
}This is my ejb bean class
package com.ejb3;
import javax.ejb.Stateless;
@Stateless
public class HelloWorldRemoteBean implements HelloWorldRemote {
     public String sayHello(String name) {
          String output = "Hello " + name;
          return output;
}This is my servlet code:
private void processRequest(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
          RequestDispatcher rd = null;
          try {
               Properties props = new Properties();
              props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
              props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
              props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
              props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
              props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
              InitialContext ic = new InitialContext(props);
              HelloWorldRemote helloWorld = (HelloWorldRemote)ic.lookup("HelloWorldRemoteEJB");
               String input = request.getParameter("myname");
               String output = helloWorld.sayHello(input);
               request.setAttribute("result", output);
               rd = getServletContext().getRequestDispatcher("/result.jsp");
          catch(NamingException e) {
               e.printStackTrace();
          if(rd != null)
               rd.forward(request, response);
     }I had this error:
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.enterprise.naming.SerialInitContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.enterprise.naming.SerialInitContextFactory]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at com.controller.HelloWorldController.processRequest(HelloWorldController.java:55)
     at com.controller.HelloWorldController.doPost(HelloWorldController.java:40)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.naming.SerialInitContextFactory
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1363)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1209)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
     ... 21 moreI have spent 1 week to find the answers for this problem, but still have not found any answer.
I also tried to search on google, but I got no answer.
Can anyone help me please?
Thanks.

I have the same problem. Remove the instructions from the EJB3 FAQ until it has you can take a plain tomcat tarball, add the jars and have it work.
Without javaee and appserv-rt jars:
java.lang.NoClassDefFoundError: javax/ejb/EJBObject
With jars in $TOMCAT_HOME/lib
May 5, 2008 2:33:52 PM org.apache.catalina.mbeans.GlobalResourcesLifecycleListener createMBeans
SEVERE: Exception processing Global JNDI Resources
javax.naming.NamingException: Cannot create resource instance
     at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:156)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
May 5, 2008 2:33:52 PM org.apache.catalina.core.StandardService start
INFO: PWC1377: Starting service Catalina
javax.naming.NamingException: Cannot create resource instance
     at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:156)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)

Similar Messages

  • Tomcat output question

    hi all
    i think this is a simple (and quite stupid) question, but i don't know ho to solve my problem
    i work on two computer (windows 2k), one where i have tomcat installed not like a service, the other with tomcat installed like a service.
    when i write some servlet or jsp page i use to debug it through System.out.println() method to get the output. when i work on the 1st machine i can read the output directly by the prompt, but the problem arrives on the other machine, when no prompt is opened running tomcat.
    is there a way (log file and so on) to get my application's output running under tomcat? the version is 4.1.18
    thanx a lot
    sandro

    Hi. the solution is quite simple.
    Go to your TomcatHome (where you installed it) and look for a folder called log. To check your System.out.println stuff on your tomcat as windows service just take a look to an archive called stdout.txt or something similar (can't remember the exact name)
    DFF

  • Example Application - EJB3/JAXB2/GlassFish - Sun Java Studio Creator 2

    Hi,
    I'm setting up an example application using EJB3/JAXB2 together with a Sun Java Studio Creator2 web client.
    The example is not in a smooth/sexy presentation state;)
    However, it works on my windows pc. Most installation steps
    are already automated. It's fun to see how easy the Creator web app
    works together with glassfish ejb3 layer.
    http://enpasos.com/finance/doc/index.html
    Have fun,
    Matthias

    Hi Matthias,
    I am interested in your example and the link is invalid. Can you send me your solution of the integration EJB3 and Creator please?
    Petr
    mailto: [email protected]

  • EJB3 customizing/extending question

    I have an EJB module with some stateless session beans in it. They all are quite obviously currently deployed.
    I started down the road on the following thought experiment, which I'm fairly convinced is invalid, but thought I'd ask.
    Suppose I "buy" that fabled EJB jar that you're supposed to be able to purchase from so-called component vendors. And suppose I want, for whatever reason, to treat that ejb-jar file as much like a black box as possible.
    Now suppose that it ships with a WombatBean in it, whose ejb-name is WombatBean, and whose ejb-class is com.foo.WombatBeanImpl. Suppose I want to add an additional couple of attributes--semantically--to it, without cracking open the ejb-jar.
    Could I:
    * Write an EJB that extends WombatBeanImpl--suppose it's com.ljn.WombatBeanExtension--and pack it up in its own ejb-jar file
    * Somehow convince the EJB container to map the ejb-name of WombatBean to "point" at com.ljn.WombatBeanExtension, such that com.foo.WombatBeanImpl is always "shadowed"?
    I understand that I could sort of accomplish this and say that for all applications I know about I could go play games with ejb-refs and the like and point them all at my bean instead of theirs, but I guess I wanted to do this "underneath" the ejb-name they're all referencing.
    Does this make any sense? Am I waaaay off base here?
    Thanks,
    Laird
    P. S. If I can do this, but it's appserver-dependent, I'd appreciate those answers too. I'm using EJB3/JavaEE5 on Glassfish b32.

    ejb-name is only guaranteed to be unique within the scope of an ejb-jar, so by definition if the other
    ejb is in a different ejb-jar the ejb-names would not clash.
    Regarding the issue of sub-classing,
    it's not that you can't use implementation inheritance, where one of the super-classes happens
    to be the bean class of an EJB component. The point is that there is no special notion of
    component inheritance for beans. In other words, just because you write a class FooBean
    whose parent is a bean class with an @Stateless annotation doesn't make FooBean an EJB.
    FooBean would need its own component-defining annotation or an entry in an ejb-jar.xml that
    declares it as a bean. In addition, some of the ejb meta-data in the super-class would not
    apply to FooBean, such as its metadata for declaring which local/remote interfaces it exposes.
    There is a lot of complexity in defining rules for processing of the ejb annotations
    to support full component inheritance so the spec decided to limit this support to keep
    things simpler.
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Tomcat / Glassfish Session Synchronization and JAAS

    Hi there!
    How does session synchronzation between Tomcat and Glassfish work?
    For example, if there are two users at the same time, each one has it's own webserver session and both are working on the same stateful java bean (e.g. a simple shop cart), how are both sessions - the webserver and application server session - synchronized? Any form of synchronization has to take place, otherwise a cart bean would be senseless, as there were unwanted interactions between both clients. Are there any hidden tokens that are send via JNDI Lookup?
    It's the same with JAAS: If there's a programmatic login on the application server, how does the application memorize the user's privileges and principal, in particular if there's a server cluster? Is there intern a simple stateful bean? And how does the mapping between websession and application server session work? Is it really reliable?
    Hope you can help me. It's quite hard to find detailed and solid documentation concerning this topic.
    Thanks!

    Hi,
    Can you provide a solution that does not include JSTL, as I can not use this technology as it is not in scope for the DEV environment defined for these projects I am working on.
    regards,
    Pravash

  • Access local EJB3 on Glassfish

    I'm using Eclipse and have a combined Java/Flex project using WTP that uses BlazeDS and is deployed to a Glassfish server (v2ur2).  I was able to configure everything correctly to access simple routines with the remote access, but now I would like to access an EJB3 using the local interface.  I have another project in Eclipse that is an EJB Module and the Java/Flex project specifies that as a dependency. I can access an EJB from that project using a remote interface, but am having trouble figuring out how to access one with a local interface.
    I saw another thread on the forum that referenced the EJB3 Factory available through the Adobe exchange so I downloaded that and added it to my project.  I defined the factory in services-config.xml and added a new destination in remoting-config.xml, but when I try to access the EJB, it gives me an "error accessing local resource..."
    Is there something else I need to do?  Any pointers as to what might be going wrong?  I'm assuming that specifying the Java EE Module dependency for the EJB module should pull it in and make the local interface accessible.  Is that right?  If not, what else do I need to do?  I'm fairly new to all of this and still don't completely understand how everything in the Java/Flex project is being deployed.
    Any help would be greatly appreciated!  Thanks!
    Renee

    Renee,
    I spend about 3 full days to figure out how to make this work. I eventually come to your solution, which is very nice. I would just like to add a detail: you do not need to publish the JNDI name of your EJB in the sun-ejb-jar.xml, neither in the EJB annotations. The only thing you have to make sure is to use the exact EJB class name in the web.xml file -- and both modules have to be deployed in the same enterprise application (ear).
    So, to make a quick summary of the specific things to do (this is not a complete procedure) :
         1. Create the Flex+BlazeDS combined app (or, if you want a cleaner project structure, make two separate apps : one Flex and one web app, and configure them correctly -- but this doesn't change anything to the following).
              - Add the EJB3 Factory library (.jar) from Adobe in the WebContent/WEB-INF/lib folder
              - Configure the services-config.xml to declare this factory (see help)
         2. Create the EJB module
              - Create your bean class and its local interface
              - In the bean class, do only use a basic "@Stateless" annotation, do not specify attribute in this annotation (e.g. the name of the bean or its JNDI address)
         3. Configure the remoting-config.xml file to map a destination to your EJB through its local interface (and not the remote one)
              - First, create a local reference from the web app to the EJB class:
                   <ejb-local-ref>
                        <!-- Exact name of the EJB class, or the name specified in @Stateless(name="xxx") - by default, the name attribute of the tag is the name of the EJB class -->
                        <ejb-ref-name>HelloServiceBean</ejb-ref-name>
                        <!-- Qualified name of the local interface of the EJB -->
                        <local>org.sandbox.IHelloServiceLocal</local>
                   </ejb-local-ref>
              - In the remotings-config.xml of the Flex/Web app, use the GlassFish local JNDI reference to this ref-name (e.g. prefix its name with "java:comp/env"):
                   <destination id="HelloService">
                        <properties>
                             <factory>ejb3</factory>
                             <source>java:comp/env/HelloServiceBean</source>
                        </properties>
                   </destination>
         4. Create the enterprise application containing both apps (flex/blazeds + ejb module)
    And that's all ! Deploy all this stuff to your server, and browse to your Flex app and call the EJB through a RemoteObject.
    Hope this helps. If interested, I may post on my (old) blog a full procedure to configure this example in Eclipse.
    Fred.

  • Tomcat 5 question

    I know this question may be better suited to a tomcat forum but there is not too much activity on http://www.jguru.com/forums/Tomcat right now. If you do have a better forum please let me know.
    My question is
    does Tomcat 5 automatically create the servletcontext for your web app when you deploy it first? I assume so since my App works fine and I havn't created one. And is this ServletContext deleted after you stop Tomcat?
    Cheers .... J

    By default, everything onder the root ("/") is mapped. So when you add a new webapp it will immediately be available.

  • Swing + JGoodies, EJB3 / Hibernate - Design question...

    Hi,
    Forgive me if I screw up the terminology here.. I'm pretty new to J2EE and Swing development. I'm developing a Swing based application to replace a paper process. It's basically a long form that gets submitted to a server where it is reviewed and in some cases sent back to the user for corrections. I'm having trouble figuring out a good implementation for the data tier.
    The prototype that I've developed makes extensive use of the JGoodies framework (Forms, Binding, Validation). The domain model is basically a bunch of POJO's. For each object there is a separate validator object which has a a validate() method that returns a ValidationResult object. On the Swing side, there is a Model object for each POJO/Validator which listens for changes to the result of validate(). The GUI class attaches to the model and updates the GUI to reflect results of the validation. Basically the result is that if you don't fill out a required field, the field's background color changes and you get a list of reasons why you aren't allowed to submit the form at the bottom of the page. What you type in the field is synchronized with the data object on key release or focus changes (not sure yet).
    Pretty much all of this functionality rests upon the domain model calling 'firePropertyChange' in the setXYZ() functions. This solution seems to work when the client uses Hibernate to persist the objects directly to the DB Server, but I'm wondering if/how it could work if we decided to use EJB3 Entity Beans for storing the data instead of Hibernate (primarily because we don't want to leave our DB server's port open on the firewall).
    From what I've gathered, under EJB3 the POJO's that I'm currently using on the client side (which call 'firePropertyChange') would end up on the server. I am assuming that the 'firePropertyChange' functionality would be broken. When the client binds to the Entity Bean, the server would cause the creation of a new object with simple getters and setters based on the interface on the server side. I assume that this code would be generated for me automatically and I wouldn't be able to get the 'firePropertyChange' functionality back. In other words, the binding between the GUI and the POJO would be lost, along with the automatic validation.
    Is this still possible? Was it ever? Was it possible with EJB2 using the Home objects? Should I just stick with Hibernate and let the clients access the DB server directly? Does anyone have any idea what I'm talking about? The only possibility I could think of was to create another layer of java objects and bind the matching properties between the EJB3 entity bean and the model beans that I already have, but this results in an additional class per form element.
    Thanks,
    Scott

    Hi,
    Forgive me if I screw up the terminology here.. I'm
    pretty new to J2EE and Swing development. I'm
    developing a Swing based application to replace a
    paper process. It's basically a long form that gets
    submitted to a server where it is reviewed and in
    some cases sent back to the user for corrections. I'm
    having trouble figuring out a good implementation for
    the data tier.I'm not familiar with JGoodies. Just browsing their Web site I think they're targeting desktop app, not client/server over a network. firePropertyChange assumes that sender and receiver are both running in the same address space, not on two different hosts on the internet.
    The prototype that I've developed makes extensive use
    of the JGoodies framework (Forms, Binding,
    Validation). The domain model is basically a bunch of
    POJO's. For each object there is a separate validator
    object which has a a validate() method that returns a
    ValidationResult object. On the Swing side, there is
    a Model object for each POJO/Validator which listens
    for changes to the result of validate(). The GUI
    class attaches to the model and updates the GUI to
    reflect results of the validation. Basically the
    result is that if you don't fill out a required
    field, the field's background color changes and you
    get a list of reasons why you aren't allowed to
    submit the form at the bottom of the page. What you
    type in the field is synchronized with the data
    object on key release or focus changes (not sure
    yet).Standard data validation stuff. So far, so good.
    Pretty much all of this functionality rests upon the
    domain model calling 'firePropertyChange' in the
    setXYZ() functions. This solution seems to work when
    the client uses Hibernate to persist the objects
    directly to the DB Server, but I'm wondering if/how
    it could work if we decided to use EJB3 Entity Beans
    for storing the data instead of Hibernate (primarily
    because we don't want to leave our DB server's port
    open on the firewall).I'd say you most certainly do not want to leave that port open on the firewall. The successful functioning of your "firePropertyChange" has nothing at all to do with the choice between Hibernate and EJB3. Neither of them knows or cares.
    From what I've gathered, under EJB3 the POJO's that
    I'm currently using on the client side (which call
    'firePropertyChange') would end up on the server. I
    am assuming that the 'firePropertyChange'
    functionality would be broken. It means that your firePropertyChange would have to have JNDI lookups to find the EJB proxy.
    When the client binds
    to the Entity Bean, the server would cause the
    creation of a new object with simple getters and
    setters based on the interface on the server side. I
    assume that this code would be generated for me
    automatically and I wouldn't be able to get the
    'firePropertyChange' functionality back. In other
    words, the binding between the GUI and the POJO would
    be lost, along with the automatic validation.No, but I'm not sure that you want to do things this way.
    Is this still possible? Was it ever? Was it possible
    with EJB2 using the Home objects? Should I just stick
    with Hibernate and let the clients access the DB
    server directly? Does anyone have any idea what I'm
    talking about? Do you know what you're talking about? 8)
    The only possibility I could think of
    was to create another layer of java objects and bind
    the matching properties between the EJB3 entity bean
    and the model beans that I already have, but this
    results in an additional class per form element.
    Thanks,
    ScottYou definitely want the app server and the database to be on the same side as the firewall. The EJB app tier will stand between the UI and the database. That way you can do validation and, perhaps more importantly, authentication and authorization.
    You don't say whether this is an intranet (clients and servers inside the firewall) or Internet application (clients outside the firewall). If it's the latter, you'll have a very hard time indeed continuing with Swing. If you go with a web-based UI (JSPs and servlets), you eliminate the problem of getting through the firewall, but you take on the added complexity of a web tier, an app tier, and a persistence tier.
    Why EJBs? You're using Hibernate and POJOs - good choice. Why not ditch EJBs altogether and go with Spring instead? You can use Spring MVC for your web tier and Bob's your uncle.
    %

  • Tomcat servlet question.

    I created a really simple servlet named Log ( "Hello World") that was created in a Packet called World.
    When I try to run this servlet using
    http://1#.3#.1#4.1#9:8080/World/servlet/Log
    Tomcat generated this error :
    Error: 500
    Location: /World/servlet/Log
    Internal Servlet Error:
    java.lang.NoClassDefFoundError: Log (wrong name: World/Log)
         at java.lang.ClassLoader.defineClass0(Native Method)
    How can I call this servlet ?
    I has been using servlets with websphere without problems.
    Thanks in advance.

    JSP's don't have to be registered but they can. Servlets that are not in packages can be put directly into WEB-INF/classes and not registered.
    As a caveat,this may not apply for all servers. I know that weblogic requires that all servlets be registered and mapped to an alias.

  • Tomcat Log Question

    Anyone have any idea what this means? Note the error messages, and the problem I'm having is that my Tomcat server just seems to randomly shut down. Maybe related to the following??
    Jan 25, 2006 12:47:02 PM org.apache.commons.modeler.Registry loadRegistry
    INFO: Loading registry information
    Jan 25, 2006 12:47:02 PM org.apache.commons.modeler.Registry getRegistry
    INFO: Creating new Registry instance
    Jan 25, 2006 12:47:03 PM org.apache.commons.modeler.Registry getServer
    INFO: Creating MBeanServer
    Jan 25, 2006 12:47:04 PM org.apache.coyote.http11.Http11Protocol init
    INFO: Initializing Coyote HTTP/1.1 on port 8080
    Starting service Tomcat-Standalone
    Apache Tomcat/4.1
    Jan 25, 2006 12:47:05 PM org.apache.commons.digester.Digester error
    SEVERE: Parse Error at line 1 column 10: Document root element "web-app", must match DOCTYPE root "null".
    org.xml.sax.SAXParseException: Document root element "web-app", must match DOCTYPE root "null".
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at org.apache.commons.digester.Digester.parse(Digester.java:1543)
         at org.apache.catalina.startup.ContextConfig.applicationConfig(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.start(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.StandardContext.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardHost.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardEngine.start(Unknown Source)
         at org.apache.catalina.core.StandardService.start(Unknown Source)
         at org.apache.catalina.core.StandardServer.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.execute(Unknown Source)
         at org.apache.catalina.startup.Catalina.process(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.startup.Bootstrap.main(Unknown Source)
    Jan 25, 2006 12:47:05 PM org.apache.commons.digester.Digester error
    SEVERE: Parse Error at line 1 column 10: Document is invalid: no grammar found.
    org.xml.sax.SAXParseException: Document is invalid: no grammar found.
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at org.apache.commons.digester.Digester.parse(Digester.java:1543)
         at org.apache.catalina.startup.ContextConfig.applicationConfig(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.start(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.StandardContext.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardHost.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardEngine.start(Unknown Source)
         at org.apache.catalina.core.StandardService.start(Unknown Source)
         at org.apache.catalina.core.StandardServer.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.execute(Unknown Source)
         at org.apache.catalina.startup.Catalina.process(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.startup.Bootstrap.main(Unknown Source)
    Jan 25, 2006 12:47:11 PM org.apache.commons.digester.Digester error
    SEVERE: Parse Error at line 1 column 10: Document root element "web-app", must match DOCTYPE root "null".
    org.xml.sax.SAXParseException: Document root element "web-app", must match DOCTYPE root "null".
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at org.apache.commons.digester.Digester.parse(Digester.java:1543)
         at org.apache.catalina.startup.ContextConfig.applicationConfig(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.start(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.StandardContext.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.addChildInternal(Unknown Source)
         at org.apache.catalina.core.ContainerBase.addChild(Unknown Source)
         at org.apache.catalina.core.StandardHost.addChild(Unknown Source)
         at org.apache.catalina.core.StandardHostDeployer.install(Unknown Source)
         at org.apache.catalina.core.StandardHost.install(Unknown Source)
         at org.apache.catalina.startup.HostConfig.deployDirectories(Unknown Source)
         at org.apache.catalina.startup.HostConfig.deployApps(Unknown Source)
         at org.apache.catalina.startup.HostConfig.start(Unknown Source)
         at org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardHost.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardEngine.start(Unknown Source)
         at org.apache.catalina.core.StandardService.start(Unknown Source)
         at org.apache.catalina.core.StandardServer.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.execute(Unknown Source)
         at org.apache.catalina.startup.Catalina.process(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.startup.Bootstrap.main(Unknown Source)
    Jan 25, 2006 12:47:11 PM org.apache.commons.digester.Digester error
    SEVERE: Parse Error at line 1 column 10: Document is invalid: no grammar found.
    org.xml.sax.SAXParseException: Document is invalid: no grammar found.
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at org.apache.commons.digester.Digester.parse(Digester.java:1543)
         at org.apache.catalina.startup.ContextConfig.applicationConfig(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.start(Unknown Source)
         at org.apache.catalina.startup.ContextConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.StandardContext.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.addChildInternal(Unknown Source)
         at org.apache.catalina.core.ContainerBase.addChild(Unknown Source)
         at org.apache.catalina.core.StandardHost.addChild(Unknown Source)
         at org.apache.catalina.core.StandardHostDeployer.install(Unknown Source)
         at org.apache.catalina.core.StandardHost.install(Unknown Source)
         at org.apache.catalina.startup.HostConfig.deployDirectories(Unknown Source)
         at org.apache.catalina.startup.HostConfig.deployApps(Unknown Source)
         at org.apache.catalina.startup.HostConfig.start(Unknown Source)
         at org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown Source)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardHost.start(Unknown Source)
         at org.apache.catalina.core.ContainerBase.start(Unknown Source)
         at org.apache.catalina.core.StandardEngine.start(Unknown Source)
         at org.apache.catalina.core.StandardService.start(Unknown Source)
         at org.apache.catalina.core.StandardServer.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.start(Unknown Source)
         at org.apache.catalina.startup.Catalina.execute(Unknown Source)
         at org.apache.catalina.startup.Catalina.process(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.startup.Bootstrap.main(Unknown Source)
    Jan 25, 2006 12:47:12 PM org.apache.coyote.http11.Http11Protocol start
    INFO: Starting Coyote HTTP/1.1 on port 8080
    Jan 25, 2006 12:47:12 PM org.apache.jk.common.ChannelSocket init
    INFO: JK2: ajp13 listening on /0.0.0.0:8009
    Jan 25, 2006 12:47:12 PM org.apache.jk.server.JkMain start
    INFO: Jk running ID=0 time=21/55  config=/var/tomcat4/conf/jk2.properties

    Do you have the standard headers in your web.xml file?
    Doctype tag/DTD declaration?
    You are dealing with Tomcat4?
    What is the web.xml file that generates this error?
    Presumably it should start something like this?
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    ...

  • (Java Base API / JNI ) in tomcat

    Hi All,
    (this is a question I asked on the 'C-API' forum but I got no answer. I hope I'll have more success here )
    I'm trying to access a database built with the C-API from a tomcat/glassfish server using the Java native API. (I need to read data produced with the C API)
    I put the Environment in the application context so all user will share the same instance of the database.
    first question: is it a good idea ? What would be the best practice ? can I safely use this application in a multithreaded environment ?
    The problem was that the 'System.loadLibrary' method is called each time my application is re-deployed: so an exception was thrown !! (library already loaded) because the server has already loaded the db library in a previous deployment. To solve the problem I put a silent 'try... catch...' around this System.loadLibrary in the source code of com/sleepycat/db/internal/db_javaJNI.java
    2nd question: is there a way to avoid this hack ?
    Thank you for any answer
    Pierre

    The JE team does not know the answer to your question, but will see if we can find redirect it to someone who might know.

  • EJB3 CORRUPTED when using more than one PersistenceUnit

    Hi,
    I am using JSF, EJB3 on Glassfish. CMP and JTA.
    This is the scenario:
    A user logs into application choosing one Persistence Unit (like in JavaSE). This is only at the beginig as I want to use Glassfish CMP and JTA.
        public EntityManagerFactory getEmf() throws Exception {
            configOverrides = new HashMap<String,Object>();
            configOverrides.put(TARGET_DATABASE,TargetDatabase.SQLServer);
            configOverrides.put(TARGET_SERVER,TargetServer.SunAS9);
            configOverrides.put(JTA_DATASOURCE,"jdbc/"+puName);
            configOverrides.put(SESSION_NAME,puName+"_session");
            emf = Persistence.createEntityManagerFactory(puName,configOverrides);
            return emf;
        }I then put the corresponding PersistenceUnit name in http Session scope to be used later on.
    I created a CommonEjbImpl to further inject via Jndi (and therefore use CMP and JTA) an EntityManger in each EJB3 as follows:
    @PersistenceContexts({
       @PersistenceContext(name="pu/SOCIETE1", unitName="SOCIETE1"),
       @PersistenceContext(name="pu/SOCIETE2", unitName="SOCIETE2"),
       @PersistenceContext(name="pu/SOCIETE3", unitName="SOCIETE3"),
       @PersistenceContext(name="pu/SOCIETE4", unitName="SOCIETE4"),
       @PersistenceContext(name="pu/SOCIETE5", unitName="SOCIETE5"),
       @PersistenceContext(name="pu/GENESYS_EXEMPLE", unitName="GENESYS_EXEMPLE")
    public class CommonEjbImpl {
        public EntityManager initEm() {
            LogUtil.log(this.getClass(),(String)FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("database"));
            return initEm((String)FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("database"));   
        public EntityManager initEm(String puName) {
            EntityManager em = null;
            try {
                em = (EntityManager) new InitialContext().lookup("java:comp/env/pu/"+puName);
            } catch (NamingException ex) {
                LogUtil.error(this.getClass(),ex);
            return em;   
        public void cleanup(EntityManager em) {
            //LogUtil.log(this.getClass(), "CLEANING EJB..with em: "+em);
            if (em != null && em.isOpen()) {
                em.close();
        } And in each EJB3, I use this CommonEjBImpl to get the Entity Manager like this:
    @Stateless
    public class TreeEJB extends CommonEjbImpl implements TreeEJBLocal {
        public TreeEJB() {
        private EntityManager em;
        @PostConstruct
        public void init() {
            em = super.initEm();
        @PreDestroy
        public void cleanup() {
            super.cleanup(em);
    }I have also a JSF backing bean (in SESSION SCOPE) "TreeBean" in which i Inject an EJB3 like this:
        <managed-bean>
            <managed-bean-name>TreeBean</managed-bean-name>
            <managed-bean-class>com.mfpsoft.bean.tree.TreeBean</managed-bean-class>
            <managed-bean-scope>session</managed-bean-scope>
        </managed-bean>and:
    public class TreeBean extends BeanLoader {
        public TreeBean() {
        @EJB
        private TreeEJBLocal treeEJB;
        @PostConstruct
        public void init() {
            treeEJB.init();
    }SO, imagine what is happening:
    USER1 logs (a persistence unit)
    USER2 logs (a different persistence unit)
    USER1 refresh tree for example
    USER2 rehresh tree also
    ==> USER2 GETS data from USER1 persitence unit
    My questions:
    EJB3 refrence seems to in application scope. Is thereonly one EJB3 refrence per appication?
    If so, how can I use same EJB with different persistence COntexts at the same time.
    Would this be a workaround ?? get entityManager at each business method of the EJB like this
        public  Object Method(Object object) throws Exception {
            EntityManager em = super.initEm();
            try {
                ...//em operations
            } catch (Exception ex) {
            } finally {
               em.close();
        }Would the data be corrupted if simultaneous access to same method by diffrent users?
    This issue is quite URGENT
    I would really appreciate a quick help on this
    Many thanks in advance
    Nicog

    Hi Zsom,
    Thanks for your answer
    Let me explain more clearly.
    My architecture is as follows: using JSF, Glassfish and ...SQL Server!! (! i know but this is mandatory requirement as our application is full web version of an existing ERP application already sold and installed by more than 1000 of our customers...
    I am using
    JSF-->JSF Managed Bean (Session for some and Request for almost all when logged )-->EJB Interface-->EJB Impl-->Entity-->Database
    Our application is ERP that our customers uses to managed several companies simultanously .
    This product ,mainly for intranets, is delivered with glassfish, the web application and SQL server containing by default 5 databases SOCIETE1,...SOCIETE5...but more can be created by our consultants for this customer....
    All databases have the same schema but not the same data.
    Sincerely, if I had done the desgin of the database, for sure I would have put all SOCIETEn in one DB but this is historical and I cant do anything against it.
    You have to see in our case, a database as a company of our customer (a joint venture for instance), each of which  with particular configuration, customers, orders, invoices, contacts....
    I have a persistence Unit (using JTA and CMP) per database , each using a connection pool managed by Glassfish.
    At the login of my application, the user (a user of our cutomer that bought this product), choose a database (a company actually lets say SOCIETE1), ...enter logging info and connect.
    The user must also be able to launch another browser window and connect lets say to SOCIETE2, and then work on SOCIETE1 AND SOCIETE2 simultanously.
    Also, I need Session Scope as there is configuration data that I need to keep over all pages. This configuration data is depending on the database connected to and the user.
    A session is therefore linked to the pair USER+DATABASE
    When selecting the database (company) for combo in logging form, the only way I found is fisrt to check if database(company) exists and can be connect to using at first begining Persistence.CreateEntityMangerFactory.. (i know that this is not J2EE and CMP but merly used in Java SE environments..).
    This step is only used for checking database.
    Then, if creation did not generate a Persistence Exception , I can use CMP and an EnityManger in EJB by JNDI lookup (as DI is not possible because you need constant in unitName);
    Doing so, the EJB (which only handles actions on Entities) manage the entities of the corresponding company SOCIETE1 or SOCIETE2, or.....
    I know that I might use antipatterns here, but actually this is the only solution I found
    Would an extra Layer between JSF bean and EJB do the trick....if yes how to inject the good persistence unit in my EJB is still in question.
    More if one Persistence unit is injected (assuming EJB being stateless) and another user working on another persistence unit is using the same EJB, then I go back in my first message on this topic
    As the number of databases for a customer is unknown, I can not create an EJB par database (lets says EJB_SOCIETE1, EJB_SOCIETE2,...). I agree that in this case they would be stateless....
    Do you have any suggestion to repect patterns in this situation.
    This would be greatly appreciated
    Thanks again
    Nicolas

  • Tomcat vs Apache with Tomcat connectors (mod/jk)

    Is there any advantage (security, performance etc.) of running a Java web application on Apache HTTP Server with Tomcat Connectors (mod/jk) rather than directly running it on Tomcat.

    This question is already answered, see here:
    http://tomcat.apache.org/faq/connectors.html
    Also for Tomcat/ Apache related questions, post them to the relevant mailing lists.

  • Apache webserver can't find tomcat - mod_jk problem?

    Hi
    I have recently upgraded HP-UX apache software
    FROM
    Apache webserver: 2.0.55
    Apache tomcat : 5.5.9
    TO
    Apache webserver: 2.0.55
    Apache tomcat : 5.5.9
    I have 2 tomcats running, one JVM for a daytime service and another for a nighttime service.
    So while 1 tomcat is down, the other is up, apache always running.
    However, since I have upgraded, I see the following error messages in jk.log:
    [Mon Nov 20 07:00:41 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common
    .c (949): ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8059), err=-232
    The tomcat in question is up - and the messages returned are 500 responses - server configuration issue.
    Get several a day.
    Basically using mod_jk to bind the tomcat installations to apache webserver.
    What is new though in mod_jk 1.2.10 is that a shared memory file is specified. I am wondering what happens to this memory that is used to load balance the workers when tomcats are bounced.
    Issues go away after a bounce of apache - but after each tomcat has been stopped once - messages start to fail intermittently after that.
    Done some googling but do not see any solutions - so here's hoping!
    Thanks.

    Noticed my deliberate mistake!
    From
    Apache 2.0.32
    Tomcat 3
    Still no joy with with this in terms of finding a solution to why the newer version of apache cannot find tomcat after it has been bounced.
    mod_jk.so version 1.2.9 introduced the shared memory for the workers, which as far as I can is the main config change in the 2 versions of apache that came from HP.
    So rolled back to the old version of apache with the new version of tomcat - and everything works fine!

  • Tomcat Issue with HPUX

    HI All
    I and running tomcat on HPUX machine. The problem is that on HP machine the maximum thread per process allowed is 65 ( default), so i configured max thread count in server.xml to 60. I used JMeter to check the behavior when there is enough load on tomcat. What i have observed is that even though i configured its maxthread count not to exceed 60 it is reaching 65 and as soon as it goes beyond 65 tomcat throws OutOfMemoryError. After this the thread are killed ( probably by the OS) and then the thread count comes back to around 27 but tomcat does not process any new request any more. What i was expecting is that once the threads are killed and thread count comes back to 27 it should again start processing new request.
    One option is that to increase the max thread per process limit of HP to high value, but administrators are not very convinced with this idea
    Any pointers on this issue.
    Thanks and Regards
    Pankaj Tiwari

    Read the documentation:
    "maxThreads This attribute specifies the maximum number of request-processing threads to be created by this connector"
    That means that there also are other threads, e.g. the gc thread, tomcat internal threads and so on. Reduce you number from 60 to something lower.
    How would tomcat be able to handle new requests if it was a tomcat internal thread that got killed?
    Kaj
    Ps. Please ask tomcat specific questions in a tomcat forum.

Maybe you are looking for

  • Even though I have downloaded flash player it says when download complete that it needs doing again.

    Cannot successfully add flash player even though I am told download was successful i get another message immediately saying it needs to be downloaded again and I cant view anything that needs flash player.I am on windows 7 and a desktop.How can I fix

  • Can't open Canon 70D RAW in PSE 11?

    I am using PSE 11 with ACR 7.4. I just bought a Canon 70D and PSE will not open the RAW files (.cr2) produced by this camera. Where can I download the ACR update that will let me open my 70D RAW files? Thanks.

  • Need driver for All-in-One F4480 for Mac OS 10.9

    Hi, My scanner on the F4480 was giving me an error that my software may not be compatible with my OS (Mac OS 10.9) and that I should uninstall.  Before doing so I checked the HP site for driver updates, which directed me to check the Apple Software u

  • VO extension errors when trying to run the page

    Using JDeveloper I have extended a view object:  oracle.apps.ics.por.wf.server.ReqLinesNotificationsVO I created a new view object, created the substitution and compiled the project.  The files created:  SDSUReqLinesNotificationsVOImpl.class         

  • CLR triggers and SQL Server CE

    I have an SQL Server 2012 database where a table should fire a trigger which populates an SQL Server CE 4.0 table. Developing the trigger was no problem. The problem I'm facing is the System.Data.SqlServerCe.dll registration in my SQL Server database