I need java application to read session and cookie requests

Hi
I have a java application that can the HTML and links etc but is there a way for the application to
a. retrieve cookies when they are given and
b. know when the cookie is requested
c. present the cookie when when they are requested
d. retrieve session variables when they are given and
e. know when the cookie is requested
f. present them when they are requested
Or is there a component out there where i can look at the code if it's complex
stev

Sure, the cookie is in the HTTP headers, so you don't really need anything special to handle cookies.
A starting point for further studies is:
http://home.netscape.com/newsref/std/cookie_spec.html

Similar Messages

XSQL Session and Cookies

Hi, Steven,
I have a question about cookies parameters in include-parameters.
When set the following in my xsql file:
<xsql:set-session-param name="current_user" value="{@sessionid}"/>
<xsql:include-param name="mode"/>
<xsql:include-request-params/>
In the xml output, it looks like this.
<request>
<parameters>
</parameters>
<session/>
<cookies/>
</request>
How come the session and cookies values are not appeared in XML file? However, if I reload the xsql file, the session and cookies values are there. Any idea what might be wrong or it is what should be?
Thanks in advance.
Julie Zhu

I'd expect the cookies not to show up until the page request after the one in which they are set. This is correct since setting the cookies is something that's done on the response. Reading the cookies is reading them from the request.
Regarding the session variables, it's
always important to say what Web Servlet / Servlet Engine you're using XSQL with. Perhaps the setting of Servlet session variables behaves differently on different servers.

Connect Java Application with a Session Bean

Hi,
my Problem is following:
I have session bean (stateless) and i try to write i client for it!
I get always the same error message, when i call the java ClientApplication from the Command line:
java -jar Betting_server.jar BettingServer
StartBetting Server
Part1
Caught an unexpected exception!
javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory. Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at at.siemens.mma.iap.betting.server.CreateQRunTimer$RemindTask.run(CreateQRunTimer.java:47)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
My configuration:
jboss-3.2.1_tomcat-4.1.24
j2sdkee1.3.1
j2sdk1.4.1_02
My Client Class:
package betting.server;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import java.util.*;
import betting.ejb.*;
public class CreateQRunTimer {
     Timer timer;
     public CreateQRunTimer() {
          timer = new Timer();
          timer.schedule(new RemindTask(),
                    0, //initial delay
                    1*60*1000); //subsequent rate 30 minutes
     class RemindTask extends TimerTask {
          public void run() {
               String logicalBettingBeanName = "MyBetting";
               Betting bet;
               BettingHome bethome;
               try
                    System.out.println("Part1");
                    Properties props = new Properties();
                         props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
                         props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
                         props.put("java.naming.provider.url", "localhost:1099");
                    InitialContext ic = new InitialContext(props);
                    System.out.println("Part2");
                    Object objref = ic.lookup(logicalBettingBeanName);
                    System.out.println("Part3");
                    bethome =(BettingHome)PortableRemoteObject.narrow(objref,BettingHome.class);
                    bet = bethome.create();
                    long qRunMagicNum = bet.DB_CreateQRun();
                    if(bet.CreateConfigurationFileQuery(qRunMagicNum) == false)
                         // failed
                         System.out.print("CreateConfigFileQuery failed");
                    else
                         bet.TransferXMLFiles("tvbetqrun.conf",0);
                         System.out.print("CreateConfigFileQuery succed");
               catch (Exception ex)
                    System.err.println("Caught an unexpected exception!");
                    ex.printStackTrace();
               System.out.println("Run GG");
               //System.exit(0); //Stops the AWT thread (and everything else)

Normally, if you are executing the client from the command line, you do not specify the classpath in a XML file (unless you are using ant or something similar). You can specify the classpath by using the -classpath option.
Try something like
java -classpath <path_to_jboss>/client/jbossall-client.jar;Betting_server.jar BettingServer
You can check the classpath in your client with the statement
System.out.print(System.getProperty("java.class.path"));

Java application to read XMP.

Would it be possible then to have a Java application reading through the files with XMP embedded and displaying the information?

Hi Ana, sorry I didn't read your reply earlier, maybe it would have been usefull. There is no e-mail notification on this forum. Now I solved my problem with iView MediaPro and AppleScript. iView can read the "caption" data from the XMP of Photoshop 7 created files.
Here's my script (not very beautiful mind you, it's the first AS I ever wrote), the comments are in sweidish my native toungue if anyone wonders. Maybe someone else in my situation will benefit from this...
tell application "iView MediaPro"
set selectedID to the selection of window 1
set numItems to the number of items in selectedID
-- loopa genom de valda filerna
repeat with i from 1 to numItems
set j to item i of the selectedID
set origPath to the path of object j of window 1
tell application "iView MediaPro"
--hämta filens namn
copy the name of object j of window 1 to myFileName
-- ta bort suffixet ".jpg"
set KollaAntal to count characters of myFileName
set myFileNameB to characters 1 thru (KollaAntal - 4) of myFileName
-- här hämtar vi "caption"/bildtexten
copy the caption of object j of window 1 to extractedText
end tell
-- spara informationen som textfil
set thePath to path to startup disk as string
set theData to extractedText
set fileRef to (open for access file (thePath & myFileNameB & ".txt") with write permission)
set eof fileRef to 0
write theData to fileRef
close access fileRef
end repeat -- här slutar loopen
end tell
-- lite user feedback, ingen egentlig betydelse, men "känns bra"
tell application "Finder"
display dialog "Skriptet har utförts" buttons {"OK"} default button 1 with icon note
end tell

Sun Java Application Server 9.0 and 9.1 - High CPU PROCENTAGE 100%

Hi,
I have problem with sun java application Server running after few days during watching a logs from web admin suddenly the application server takes 100% cpu and keeps this procentage - I have to manually close the server process.
The server running on Windows Server 2003.
Anyone have any idea to sovle the problem?

Hi Kedar,
Thanks for the reply. Yes, I finally figured it out.
The custom MBeans seem to work well for the most part though I don't know for sure if I'm using them in the way they were really intended.
Basically, I want to run 'services' on my application server for the lifetime of the server. I want these 'services' to maintain things like runtime caching of information over time that is not persisted in a DB but needs to be kept around in active memory to be used at a later time, but only while the application server is up and running.
Another thing I would like to do is have them receive JMS notifications directly, but I seem to be having trouble when subscribing as a consumer within my custom MBean. The topic thread on that is here:
http://forum.java.sun.com/thread.jspa?threadID=5153124&tstart=0

Java Application Server 8.1 and HTTP TRACE

I need to disable the HTTP TRACE method on our servers with Sun Java Application Server 8.1 UR2. The following URL specifies how to disable on previous versions, but does not seem relavent to newer versions.
http://sunsolve.sun.com/search/document.do?assetkey=1-26-576 70-1
Any ideas?

Please post Application Server-specific questions to the App Server forum at:
http://swforum.sun.com/jive/forum.jspa?forumID=114
Thanks,
Chris

Reading sessions and descriptors outside of classpath

Hello all,
IHAC who wants to read the sessions.xml and descriptors xml files from a designated location outside of the classpath. TopLink usually reads the sessions and descriptors using class loaders, but that is not what customer is looking for.
How can a TopLink runtime read those files using absolute paths such as C:\descriptors\toplink\sessions.xml ?
And, also, inside the sessions.xml is the location of the project xml (deployment descriptor). Can that location also be expressed using absolute path (ex. C:\descriptors\toplink\HR\toplink-deployment-descriptor.xml) ?
Any information is welcomed

Doug,
Thanks for the info.
I tried to read the sessions.xml file using XMLLoader using the absolute path,
but I'm not sucessful with it.
What I tried is:
// acquire toplink session & deployment descriptor
SessionManager manager = new SessionManager();
XMLLoader loader = new XMLLoader("C:/descriptor/META-INF/sessions.xml");
session = (ServerSession)manager.getSession(loader, "sampleSession", Thread.currentThread().getContextClassLoader());
which yields it cannot find the sessions.xml resource.
Can you please point out any sample codes or the way to do it in your reply?
I know that you're very busy, I'd be much appreciated if you could help me and my customer.
Thank You.

My sun java application server not run and give me error

hi master
sir i use
sun java system with studio creator but when i start deployment server
that give me this error
==================
The sun java system application server 8.2 could not start.
more information about the cause is in the server log file .
possible reasons include:
-Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
-Incorrect server configuration (domain.xml to be corrected muanually)
-Corrupted Deployed Application preventing the server to start.(this can be seen in the server.log file. in the case, domain.xml needs to be modified).
==========
this is my server.log file
=======
[#|2007-10-23T09:43:55.144+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T09:58:09.886+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T10:12:34.768+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T11:10:28.081+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T12:58:46.034+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
please how i start my application server
thank's
aamir

Please see the following FAQ:
Why doesn't application server Start.
http://developers.sun.com/jscreator/reference/faqs/technical/depsrvs/index.jsp

How do I access the End User Licensing Agreement? I clicked on it and it gives me a message that I need to launch Adobe Reader, accept and close and reopen. Trouble is I can't get to an icon for file to launch. I am working on a Mac and have installed Mac

I am using a Mac and have installed Adobe Reader for Mac, latest version. I cannot access the End User Licensing Agreement. I clicked on it and it gives me a message that I must launch Adobe, check that I agree, close and reopen. The problem is I can't find any way to launch Adobe because it appears nowhere on my launch pad, nor in my document files or on the control panel. Because of this, I cannot print bank statements nor can I get into my insurance companies billing department to make a payment. HELP!

How about in your Applications folder?

Permissions needed to create a WLST session and deploy OSB

Hi,
Can anyone tell me what Weblogic permissions are needed to create a session with the OSB Configuration SessionManagementMBean?
It appears you need to have administrators privilege because in my environment I only have Deployers privileges which si enough for me to do an OSB deployment from the OSB Console (and apply a Customisation file etc)
but when I do it via WLST I get the exception below when I try to create a session:
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[30maro, IntegrationAdministrators, Monitors, Deployers], on ResourceType: com.bea.wli.sb.management.configuration.SessionManagementMBean Action: execute, Target: createSession
The Javadoc for the SessionManagementMBean and Oracle examples and indeed docuemtnation appears to be silent on this matter.
This is a pain because it suggests I need to have full Administrator privileges to perfor a deployment via a script but only Deployers privilege if I do it manually.
If anyone can shed light on this (or how to grant someone with Deployers privilege to create a session via the MBean) that would be much appreciated.

I ended up answering this myself. It turns out this is a bug (that exists in OSB at least to Version 11.1.1.5) for which Oracle can provide a version specific patch that allows someone in the Deployers group to deploy via WLST.
regards

Ports to open between Java application server inside firewall and Java CI

What ports do I need to open to allow a J2ee App server 7.0 to communicate with the Java Central Instance inside the firewall??
thank you !
Ld

Why Database ports? seems like the Central Instance would be the only one talking to the Database no?
thanks...
This is for CRM eCommerce....

Difference between session and cookie?

what for they use?

If we're talking web application context:
Each web browser transaction is a separate connection, so the web server often needs to be able to keep track of which comes from which browser, to tie the individual transactions into a conversation. The most popular underlying mechanism is cookies. The server sends the browser a cookie as part of the first transaction response and, thereafter, every time the browser sends a transaction it includes the cookie. Cookies typically contain random strings of characters which uniquely label the browser.
A Session object is used in Serlvets and JSPs as a higher level abstraction of the same thing. The session object retains data about the conversation between transactions. The web server normally implements this by automatically creating a random cookie associated with the Session object and, whenever a transaction is received, it looks for the cookie and finds the relavant session object.

Session and cookies

Why, if I delete the Jsession cookies and I reload the index.faces page, and post the login form, this error happend ?
ViewExpiredException: viewId:/login.faces - View /login.faces could not be restoredNew JSession cookie isn't created... Strange ?

I can't find a real solution for that problem !
In IE, the website seem to work, but without cookies... why ?
In Firefox, after deleting the JSESSION cookie, if I reload (ctrl+F5), the cookies isn't created anymore... if I try many time, maybe 2-3 min later, the cookie is created ...
Without cookie, I have the error about the view.
Sometime, without any change, in Firefox, it work but using URL variable for session... and after few login-logout-login, it use JSESSIONID cookie !
Any idea ? This kind of random problem is hard to solve.
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee   http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>URL</param-name>
<param-value>ldap://localhost:10389</param-value>
</context-param>
<context-param>
<param-name>managerDN</param-name>
<param-value>uid=admin,ou=system</param-value>
</context-param>
<context-param>
<param-name>managerPassword</param-name>
<param-value>****</param-value>
</context-param>
<context-param>
<param-name>facelets.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<description>valide le fichier faces-config</description>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<description>vérifie si tous les objets configurés sont créé correctement</description>
<param-name>com.sun.faces.verifyObjects</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml</param-value>
</context-param>
<filter>
<filter-name>MyFacesExtensionsFilter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
<init-param>
   <param-name>uploadMaxFileSize</param-name>
   <param-value>20m</param-value>
</init-param>
</filter>

<filter-mapping>
<filter-name>MyFacesExtensionsFilter</filter-name>

<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>

<filter-mapping>
<filter-name>MyFacesExtensionsFilter</filter-name>
<url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
</filter-mapping>
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
<listener>
<listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class>
</listener>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>2</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<login-config>
<auth-method>BASIC</auth-method>
</login-config>
</web-app>
index.html
<html>
     <head>
          <meta http-equiv="Pragma" content="no-cache" />
          <meta http-equiv="expires" content="0" />
          <meta http-equiv="Cache-Control" content="no-cache" />
          <meta http-equiv="Cache-Control" content="must-revalidate" />
          <meta http-equiv="Refresh" content="0; URL=login.faces" />
          <title>Start Web Application</title>
     </head>
     <body>
          <p>
               Please wait for the web application to start.
          </p>
     </body>
</html>Edited by: laurentw on Feb 10, 2009 4:12 PM
Edited by: laurentw on Feb 10, 2009 4:13 PM

APEX 4.1 - Problem with session and cookie

Hi,
I have 2 applications with both public pages and pages needs authentication. The 2 apllication have same authentication model and are using subscription to have like an SSO. So they share the same cookie.
My problem is when i'm loged on the first application and open a new navigator tab to go into a public page of the second without passing the session id, My session on the first application is not valid any more and i must login again.
I'm migrating all my applications from apex 3.1 to apex 4.1. Before this upgrade all my applications worked fine.
Thanks.

Hi,
have you implemented your own custom authentication scheme or are you using a built-in one? If you have a custom authentication scheme, can you setup an example on apex.oracle.com and provide the workspace name and application id so that we can have a look.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

How to use session and cookies in struts

I have login page. If user enters his username and password go to other page. then i copy this url and put the address bar automatically go to this page without enter username and password. So this time i want to send one message "Your session is expired". How can i tell this message page in struts. Please tell me.

I don't want to sound like a jerk (but I often do), but wouldn't it be easier to look for a good struts manual to look this stuff up in?
If each time you don't know something you ask people in this forum to explain it to you then you'll be developing for a LONG time. If you do find a good manual (hint: a book might help a lot), then your lack of struts knowledge isn't really a problem anymore.

I need java application to read session and cookie requests

Similar Messages

Maybe you are looking for