Hi,
I have a question about XWiki's version control functionality.
Q1)document deletion is recorded in the history?
Q2)Is it possible to rollback document deletion?
Thanks,
ebi
anyone can help me?
before post i search and try every solution :s.
laurentj wrote:
>
> I have this error since yesterday
> " javax.servlet.ServletException: Error number 3 in 0: Could not
> initialize main XWiki context
> Wrapped Exception: Error number 3001 in 3: Cannot load class
> com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
> from param xwiki.store.migration.manager.class
> Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
> Wrapped Exception: invalid configuration
>
> org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
>
> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
>
> org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
> org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
> org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
> com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:119)
>
> com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
>
> com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
>
> com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
> "
>
> i don't change the hibernate configuration since last try.
>
> hibernate.configuration
>
> <?xml version='1.0' encoding='utf-8'?>
> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
> Configuration DTD//EN"
> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
> <hibernate-configuration>
> <session-factory>
>
> <!-- Please refer to the installation guide on
> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation
> for configuring your
> database. You'll need to do 2 things:
> 1) Copy your database driver JAR in WEB-INF/lib or in some shared
> lib directory
> 2) Uncomment the properties below for your specific DB (and
> comment the default
> database configuration if it doesn't match your DB)
> -->
>
> <!-- Generic parameters common to all Databases -->
>
> <property name="show_sql">false</property>
> <property name="use_outer_join">true</property>
>
> <property name="dbcp.defaultAutoCommit">false</property>
> <property name="dbcp.maxActive">50</property>
> <property name="dbcp.maxIdle">5</property>
> <property name="dbcp.maxWait">30000</property>
> <property name="dbcp.whenExhaustedAction">1</property>
> <property name="dbcp.ps.whenExhaustedAction">1</property>
> <property name="dbcp.ps.maxActive">20</property>
> <property name="dbcp.ps.maxWait">120000</property>
> <property name="dbcp.ps.maxIdle">20</property>
> <!-- Without it, some queries fail in MS SQL. XWiki doesn't need
> scrollable result sets, anyway. -->
> <property name="jdbc.use_scrollable_resultset">false</property>
>
> <!-- Configuration for the default database.
> Comment out this section and uncomment other sections below if
> you want to use another database.
> Note that the database tables will be created automatically if
> they don't already exist.
> -->
> <property
> name="connection.url">jdbc:hsqldb:file:database/xwiki_db;shutdown=true</property>
> <property name="connection.username">sa</property>
> <property name="connection.password"></property>
> <property
> name="connection.driver_class">org.hsqldb.jdbcDriver</property>
> <property name="dialect">org.hibernate.dialect.HSQLDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <mapping resource="xwiki.hbm.xml"/>
> <mapping resource="feeds.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
>
> <!-- MySQL configuration.
> Uncomment if you want to use MySQL and comment out other database
> configurations.
> We need to set the sql_mode to a less strict value, see
> XWIKI-1945
> <property
> name="connection.url">jdbc:mysql://localhost/xwiki?useServerPrepStmts=false&useUnicode=true&characterEncoding=UTF-8&sessionVariables=sql_mode=''</property>
> <property name="connection.username">xwiki</property>
> <property name="connection.password">xwiki</property>
> <property
> name="connection.driver_class">com.mysql.jdbc.Driver</property>
> <property name="dialect">org.hibernate.dialect.MySQLDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <mapping resource="xwiki.hbm.xml"/>
> <mapping resource="feeds.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
> -->
>
> <!-- HSQLDB configuration.
> Uncomment if you want to use HSQLDB and comment out other
> database configurations.
> <property
> name="connection.url">jdbc:hsqldb:file:/some/path/xwikidb;shutdown=true</property>
> <property name="connection.username">sa</property>
> <property name="connection.password"></property>
> <property
> name="connection.driver_class">org.hsqldb.jdbcDriver</property>
> <property name="dialect">org.hibernate.dialect.HSQLDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <mapping resource="xwiki.hbm.xml"/>
> <mapping resource="feeds.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
> -->
>
> <!-- PostgreSQL configuration.
> Uncomment if you want to use PostgreSQL and comment out other
> database configurations.
> <property name="connection.url">jdbc:postgresql:xwiki</property>
> <property name="connection.username">xwiki</property>
> <property name="connection.password">xwiki</property>
> <property
> name="connection.driver_class">org.postgresql.Driver</property>
> <property
> name="dialect">org.hibernate.dialect.PostgreSQLDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <mapping resource="xwiki.hbm.xml"/>
> <mapping resource="feeds.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
> -->
>
> <!-- Oracle configuration.
> Uncomment if you want to use Oracle and comment out other
> database configurations.
> Note: the 2 properties named
> "hibernate.connection.SetBigStringTryClob" and
> "hibernate.jdbc.batch_size". They are required to tell Oracle to
> allow CLOBs larger than
> 32K.-->
> <property
> name="connection.url">jdbc:oracle:thin:@localhost:1521:XE</property>
> <property name="connection.username">xwiki</property>
> <property name="connection.password">xwiki</property>
> <property
> name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
> <property
> name="dialect">org.hibernate.dialect.Oracle10gDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <property
> name="hibernate.connection.SetBigStringTryClob">true</property>
> <property name="hibernate.jdbc.batch_size">0</property>
> <mapping resource="xwiki.oracle.hbm.xml"/>
> <mapping resource="feeds.oracle.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
>
>
> <!-- Derby configuration.
> Uncomment if you want to use Derby and comment out other database
> configurations.
> <property
> name="connection.url">jdbc:derby:/some/path/xwikidb;create=true</property>
> <property
> name="connection.driver_class">org.apache.derby.jdbc.EmbeddedDriver</property>
> <property name="dialect">org.hibernate.dialect.DerbyDialect</property>
> <property
> name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
> <property name="connection.pool_size">2</property>
> <property name="statement_cache.size">2</property>
> <mapping resource="xwiki.derby.hbm.xml"/>
> <mapping resource="feeds.hbm.xml"/>
> <mapping resource="activitystream.hbm.xml"/>
> -->
>
> </session-factory>
> </hibernate-configuration>
>
>
> I don't see where the error is!
>
--
View this message in context: http://n2.nabble.com/error-500-javax-servlet-ServletException-Error-number-…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi xwiki-users,
I'm trying to bootstrap a component from the wiki itself (via Groovy). I
have an interface defined as follows:
// This is the text inside the User.UserDAO document
{{groovy}}
interface UserDAO
{
def ROLE = UserDAO.class.name
/**
* Returns the current user name.
*/
def getUserName()
/**
* Returns the current user's password
*/
def getPassword()
}
{{/groovy}}
I also have a dummy implementation defined as follows:
// This is the text inside the User.UserXWQLDAO document
{{include document="User.UserDAO" /}}
{{groovy}}
import org.xwiki.component.annotation.Component
import org.xwiki.component.annotation.Requirement
import org.xwiki.component.descriptor.DefaultComponentDescriptor
import org.xwiki.query.Query
import org.xwiki.query.QueryManager
import com.xpn.xwiki.web.Utils
@Component(roles = [ UserDAO.class ])
class UserXWQLDAO implements UserDAO
{
@Requirement
def QueryManager queryManager
/**
* Returns the current user name.
*/
def getUserName() {
return "bleh"
}
/**
* Returns the current user's password
*/
def getPassword() {
return "bleh"
}
}
if(!Utils.componentManager.hasComponent(UserDAO.class))
{
def componentDescriptor = new DefaultComponentDescriptor()
componentDescriptor.setImplementation(UserDAO.class)
Utils.componentManager.registerComponent(componentDescriptor, new
UserXWQLDAO())
}
{{/groovy}}
The first problem I ran into was that Groovy 1.6.5 ran into
IncompatibleClassChangeErrors (http://jira.codehaus.org/browse/GROOVY-3830).
Upgrading to 1.6.6 fixed this issue. But, then I ran into a NPE:
*exception*
javax.servlet.ServletException: Failed to initialize Request/Response or Session
com.xpn.xwiki.web.XWikiAction.initializeContainerComponent(XWikiAction.java:391)
com.xpn.xwiki.web.XWikiAction.initializeXWikiContext(XWikiAction.java:372)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:112)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
javax.servlet.http.HttpServlet.service(Unknown Source)
javax.servlet.http.HttpServlet.service(Unknown Source)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:119)
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
*root cause*
org.xwiki.container.servlet.ServletContainerException: Failed to
initialize request
org.xwiki.container.servlet.internal.DefaultServletContainerInitializer.initializeRequest(DefaultServletContainerInitializer.java:98)
com.xpn.xwiki.web.XWikiAction.initializeContainerComponent(XWikiAction.java:387)
com.xpn.xwiki.web.XWikiAction.initializeXWikiContext(XWikiAction.java:372)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:112)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
javax.servlet.http.HttpServlet.service(Unknown Source)
javax.servlet.http.HttpServlet.service(Unknown Source)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:119)
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
*root cause*
java.lang.NullPointerException
Haven't investigated any further than this, but has anyone successfully
created components completely within a wiki document? That would just be so
cool! Great work!
-- Lewis
dear admins and xwiki enthusiasts, I say thank you in advance for setting up
the linfocus.myxwiki.org account. we will use this account for first
impression of the system in a collaborative environment. Best, Peter
(pthalmann)
hi folks,
can anyone point me to a step-by-step example of upgrading a standalone
xwiki?
replacing the contents of ${XWIKI_HOME}/webapps/xwiki/ with
xwiki-enterprise-web-2.1-rc-1.war & copying back the hibernate.cfg.xml
and xwiki.cfg has resulted in:
Problem accessing /xwiki/bin/view/Main/. Reason:
Error number 3 in 0: Could not initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Could not parse mapping document from resource
xwiki.hbm.xml
i'm upgrading 2.0.3 to 2.1RC1
sorry if this is covered in a FAQ - the upgrade Xwiki Core from
<http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgrading…>
isn't very explicit
any suggestions?
regards
p
--
Peter Lees
I just got my Google
Wave<http://mashable.com/2009/05/28/google-wave-guide/>invite and have
been trying to understand how I can use it with my
Xwiki <http://xwiki.org>-based application (soon launching on
http://trainspodder.com see
example-screen<http://nielsmayer.com/prototype-11-17-2009.jpg>: my
interest in Wave is because my site, in google-parlance, is basically
a
"wave for deep-linking/commenting/annotating/transcluding&mashing streaming
audio&video media").
One of the areas that I think Wave would help Xwiki-based applications (and
wikis/sites) is with "Viral commenting" so that Wave becomes a central place
for comments and conversations on web pages. As it "socially networks"
comments, this enables FOAFs to more easily find out about internet
conversations that might otherwise be hidden away on a website that nobody
knows about.. Thus, Wave provides a viral commenting mechanism for Xwiki
pages that is potentially superior to the other alternatives previously
available, e.g.
http://massol.myxwiki.org/xwiki/bin/view/Blog/AnonymousComments :
> XWiki Enterprise allows users to leave comments on pages. However in order
> to prevent spam on your public wiki instance you usually only want to allow
> registered users the right to add comments. Thus we need a solution that
> still allows guest users to leave comments while preventing spam.
>
> I'm proposing 2 solutions that I've both tried on this blog and that have
> worked well: Solution 1: create a special guest account that can be used
> transparently to leave comments. This can be achieved by creating a custom
> skin and tweaking the comments form Solution 2: integrate with an external
> comment web service such as IntenseDebate <http://www.intensedebate.com/>.
> This also requires a custom skin in order to override some templates.
>
It also solves the "commenting" issues in Xwiki that include (1) controlling
comment spam by forcing commenters to login with real Xwiki accounts to post
comments; (2) the lack of well-integrated and "working right out of the box"
captcha support in Xwiki to prevent comment spam w/o authentication/login;
(3) lack of "out of the box" OpenID support which would allow easy
authentication of public users wanting to leave comments; (4) users wanting
to leave comments constantly forgetting the accounts and passwords under
which they left comments, as well as not having a centralized place to
follow-up on comments they've left, or conversations they've been involved
in.
Wave seems to solve some of the problems, and might help side-step a lot of
others in Xwiki.... for example, why spend a huge amount of effort tightly
integrating OpenID or some other certificate/2FA/SSO-based auth system for
the class of wikis that comprise a small number of editors and site
maintainers, and a large number of commenters and public that you want to
authenticate, identify, and spam-control -- perhaps Xwiki's login/auth
system is perfectly adequate for this class of sites, but becomes
"overwhelmed" by logins and accounts that have been created automatically,
or just for the purpose of posting a single comment (if people even bother
to create an account to leave a comment...). Integrating Wave or
IntenseDebate <http://www.intensedebate.com/> into Xwiki might give the user
experience desired, without the complexity....
Yesterday, I posted the following to an "Xwiki wave" I started:
https://wave.google.com/wave/#restored:wave:googlewave.com!w%252Bedlc50w0G<https://wave.google.com/wave/#restored:wave:googlewave.com%21w%252Bedlc50w0G>(please
join and lets try this thing out!!)
...................................
FYI, here are some ways Wave has been integrated into other platforms (note
MediaWiki integration, can it be leveraged for Xwiki?)
Taken from http://wave.google.com/help/wave/extensions.html
(1) MediaWiki integration:
My Wave wet dream<http://mediawikiwave.blogspot.com/2009/10/my-wave-wet-dream.html>
I have been asked several times where I see Wave
<https://wave.google.com/>go. The last time I was asked where I see
Wave in 5 years time.. not
Internet years. What I did was look hard at Wave for what it does, and look
at Google <http://google.com/> for the kind of things it has been doing.
For me, Wave is an environment where the functionality of e-mail, chat, wiki
comes together. What we have done in the
MediaWikiWave<http://mediawikiwave.org/>project is provide Wave with a
publishing back end. This is something that
MediaWiki <http://mediawiki.org/> does really well. I expect that Wave will
continue to integrate parts of the puzzle that is computer software and
data.
Google is getting into operating systems with its Chrome
OS<http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html>.
Add to this Moore's law <http://en.wikipedia.org/wiki/Moore%27s_law> and in
five years time a computer with Chrome OS, with over a terabyte of storage
is not a wild idea at all.
When something like a terabyte is used for caching, I can imagine that this
cache is maintained by Wave. In this cache you find e-mail, Wavelets, Wiki
pages and other information that is of interest to a user. Wave being Wave,
will cache this information and updates it in the background. This
information will be available on request.
Wave in its architecture allows for multiple servers. It is not necessary to
know on what server a particular Wavelet is available. I think that a user
is not that interested in any particular server, he is interested in the
data being available. Only when the data is manipulated is there a need for
immediate feed back to servers or other computers.
I think this is doable. Part of the cache is already there in Google
Gears<http://gears.google.com/>and this makes this vision evolutionary
progress.
Thanks,
GerardM
(2) SAP integration:
Gravity – Collaborative Business Process Modelling within Google
Wave<http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15618>
Gravity is a prototype developed by SAP Research in Brisbane, Australia and
SAP NetWeaver Development providing real-time, cloud-based collaborative
business process modelling within Google Wave <http://wave.google.com/>.
Google Wave is Google's new real-time collaboration platform that combines
features of e-mail, social networking, wikis and instant messaging in one
integrated browser-based client. Google Wave offers rich developer APIs to
extend the core functionality with custom components. We have embedded
Gravity as a Google Wave "gadget" that can be added within the Google Wave
client. Leveraging the collaborative features of Google Wave, all business
process modelling activities get propagated in near real-time to all other
participants of the Wave. In addition, participants of the Wave can use all
other features provided by Google and its developer community to enrich the
collaborative modelling experience.
In the demo we see how Gravity can be used to facilitate the development of
high level process descriptions for two merging companies, BCD South Bank
and FH Insurance. These two companies are merging in a tough economic
climate and management need to quickly re-engineer their business processes
in order to capitalise from cross-selling opportunities between banking and
insurance products. In addition to the near real-time propagation of model
content to all participants of a Wave, various features of true real-time
collaboration are shown, such as different colour-coding for each individual
modeller, history of a model, asynchronous and synchronous editing, and
more. The demo also shows how robots (automated components that act as Wave
participants) can be leveraged in order to syntactically correct the model
on the fly. In the end, we will see how models are exported using BPMN 2.0
XML. They will then be imported into SAP Netweaver BPM for further
refinement and execution.
The demo shows how new technology can be systematically leveraged in order
to facilitate what Business Process Management is really about: business
user collaboration within and across departments of one or more
organisations.
Please check out the high resolution
screencam<https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/e03471b6-db79-2c10…>by
clicking on the Gravity screenshot above. If you experience problems with
the Podcast, please click here for more versions including a low resolution
of the screencam<https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/705d166b-dd79-2c10…>or
view the embedded screencam below.
(3) Salesforce.com <http://salesforce.com/> integration:
Getting in Front of the
Wave<http://blog.sforce.com/sforce/2009/09/getting-in-front-of-the-wave.html>
On Wednesday, September 30th, Google will open up their
Wave<http://wave.google.com/>preview to about 100,000 people. Details
are at Google
Wave Developer Blog<http://googlewavedev.blogspot.com/2009/09/what-happened-in-wave-sandbox.html>and
The
Official Google
Blog<http://googleblog.blogspot.com/2009/09/surfs-up-wednesday-google-wave-updat…>I
am excited to announce that we have put together a new
demo <http://www.youtube.com/watch?v=TQ0b1CVRZHs> on how you might leverage
the Wave platform on salesforce.com and how you might leverage
salesforce.com from Wave.
Wave is a truly exciting and seminal Cloud technology. Google Wave was
invented by two brothers Jens
Rasmussen<http://www.crunchbase.com/person/jens-rasmussen>andLars
Rasmussen <http://www.crunchbase.com/person/lars-rasmussen> at Google that
builds on the concepts of AJAX combined with fresh look at Operation
Transformation <http://en.wikipedia.org/wiki/Operational_transformation>.
It's difficult at this point in time to fully understand the ways in which
this technology may transform web based communication. It will be up to the
community of developers working within and without the enterprise to realize
the evident potential of Wave.
>From a technical perspective, Wave has the ability to interact with other
cloud platforms, like the Force.com <http://developer.force.com/> platform.
It is this interaction that we have demonstrated in relatively short time
frame in the demonstration announced in this post.
The use case for the demo is a fictitious Mobile Services Company named
Booyah. This company asks customers to register the products that they
purchase and one piece of information that is returned upon registration is
an email address for support. The email address is actually to a Wave robot
created by the company's service and support organization. When a customer
encounters a problem with their product, they can begin the process of
resolution by contacting the robot from Google Wave.
This initial contact begins an interaction to provide results from the
company's knowledge base, which of course is implemented using
salesforce.com's Service
Cloud<http://www.salesforce.com/crm/customer-service-support/>.
Through a short series of questions and responses a list of possible
solutions to the customers problem can be presented.
Behind the scenes, the robot identifies the customer by her Wave id and can
tailor the interaction based on the customers purchase and support history
providing a personalized yet automated path to resolution. The robot also
creates a case on the salesforce.com side so that this support interaction
can be managed by Booyah.
To take the experience beyond a simple knowledge base search, the customer
also has the option of requesting a live chat with an available support
representative. This is where Google Wave really starts to shine. If none of
the suggested solutions work for the customer, she can simply click a link
to request a chat. Wave sends this request to the robot which in turn makes
a request to salesforce.com to find an available representative. That
representative is then added to the wave as a participant and the
personalized service begins.
Behind the scenes the robot request is evaluated by a salesforce.com web
service built in Force.com <http://force.com/> Code. When the representative
is found the web service creates a task and a reminder for the task and
assigns it to the representative. The representative is, of course, working
in the salesforce.com UI and sees an alert window as the reminder is
triggered. The representative can simply click on the link to the case shown
in the alert window to access the case.
The cool part about this is that when the case was created, enough
information about the wave was included so that the active wave could be
embedded directly into the layout of the Case detail page. This embedded
Wave has full interactive capability so that the support representative can
carry on the conversation with the customer from the Case detail page. And,
the wave, which was the original channel for the support case can be
accessed at any point in time later, including all the interaction with the
customer.
I'm confident that with the creative minds in the
Force.com<http://force.com/>community, as evidenced by the fantastic
Sites created during our Sites
contest, that many more and truly valuable use cases can be implemented by
combining these two amazing platforms.
If you want to learn more about creating Force.com <http://force.com/> and
Wave solutions be sure to attend the Riding the (Google)
Wave<http://www.salesforce.com/dreamforce/DF09/site/learn/tracks/a1y300000004CGe…>session
at
Dreamforce <http://www.salesforce.com/dreamforce/DF09/site/> this year.
Niels
http://nielsmayer.com
Hi,
Is it possible to create a listener, like those for java GUI, to listen for new updates or pages? The goal is to perform an operation everytime a save operation in xwiki occurs.
Thanks in advance!
J. Allen
Hello,
I have a page that was modified 47 times. When i go to see the history, the tab displayed "Results 1 - 20 of 47" but i can see all versions. If i go on the second or the third page, the result is also the complete history list.
Is it a known bug ? I tried to look at the JIRA issues but i did not find any.
Thank you
Christophe Périnaud
Windows Server 2003 SP2 in a VMWare instance
Oracle 10g
Java 1.6.0_12
Xwiki 2.0.3 from the pack Jetty/HSQL
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
